> For the complete documentation index, see [llms.txt](https://docs.fixes.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fixes.world/developer/open-api-service.md).

# Open API Service

{% hint style="info" %} <mark style="color:green;">Please read</mark> [FIXeS Open API Service Legal Disclaimer](/developer/open-api-service/legal-disclaimer.md) <mark style="color:green;">before using FIXeS Open API Service.</mark>
{% endhint %}

## Overview

FIXeS Open API Service is open to community developers, allowing you to explore the world of FIXeS executable inscription. You can deploy your own inscribing services, bulid wallet applications, develop browsers, and much more using this API.

## Getting an API Key

To use the FIXeS Open API Service, please request an `API_KEY` from us by sending an email to <fixesonflow@gmail.com> with the name and description of your project and the reason for using it. After we review it, we will send you the `API_KEY`.

When you obtain the API key, please add it to the request header with the `Authorization` format as follows:

```bash
curl --location 'http://open-api.fixes.world/v1/utils/flow-price' \
--header 'Authorization: Bearer YOUR_API_KEY'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fixes.world/developer/open-api-service.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.