> For the complete documentation index, see [llms.txt](https://docs.seda.xyz/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seda.xyz/home/for-agents/agent-modules/execute-on-seda-fast.md).

# Execute On SEDA Fast

Execute Oracle Programs through SEDA Fast (API-first). Includes canonical curl examples and links to Fast OpenAPI docs.

## Execute via SEDA Fast (API)

**Canonical URL:** [**https://docs.seda.xyz/home/for-agents/agent-modules/execute-on-seda-fast**](https://docs.seda.xyz/home/for-agents/agent-modules/execute-on-seda-fast)

> **Important: SEDA Fast does not deploy Oracle Programs.**
>
> * **Deploy** (upload) Oracle Programs to the SEDA Network using a wallet + tokens (testnet or mainnet).
> * **Execute** Oracle Programs via SEDA Fast using an API key and the existing **Oracle Program ID**.
>
> If you do not have an Oracle Program ID yet, go to: `modules/50-execute-core.md` (Deploy section) + `modules/30-wallet-and-tokens.md`.

Authoritative references:

* Quick Start Guide: <https://docs.seda.xyz/home/for-developers/quick-start-guide>
* SEDA Fast overview: <https://docs.seda.xyz/home/for-developers/define-your-delivery-method/seda-fast>
* Fast API reference (OpenAPI):
  * Testnet: <https://fast-api.testnet.seda.xyz/docs>
  * Mainnet: <https://fast-api.mainnet.seda.xyz/docs>

This runbook executes Oracle Programs through the SEDA Fast API.

**Rule:** Do not guess payload shapes or fields. If anything changes, treat the OpenAPI docs as the source of truth.

***

### Critical distinction (Fast execution vs Program deployment)

#### Case 1: Execute an existing Oracle Program on Fast

* Needs: Fast API key
* Does **not** need: wallet/tokens

#### Case 2: Deploy your own Oracle Program, then execute on Fast

* Needs: wallet + tokens to deploy the Oracle Program
  * [`https://docs.seda.xyz/home/for-agents/agent-modules/wallets-and-tokens`](https://docs.seda.xyz/home/for-agents/agent-modules/wallets-and-tokens)
  * deploy step in <https://docs.seda.xyz/home/for-agents/agent-modules/deploy-oracle-program-upload-to-seda-network>
* Needs: Fast API key to execute on Fast: <https://docs.seda.xyz/home/for-agents/agent-modules/execute-on-seda-fast>

***

### Canonical execute endpoint (testnet)

Docs use: `https://fast-api.testnet.seda.xyz/execute?includeDebugInfo=true&encoding=json`

***

### Example: ETH/USD (JSON output)

Copy/paste (replace the bearer token only):

```bash
curl -L -X POST 'https://fast-api.testnet.seda.xyz/execute?includeDebugInfo=true&encoding=json' \
  -H 'Authorization: Bearer {{BEARER_TOKEN}}' \
  -H 'Content-Type: application/json' \
  --data-raw '{
    "execProgramId": "1b7754932d711916abe9b986c4ac9c2195e7a9efbe7445d774739966370f880a",
    "execInputs": {
      "id": "0xff61491a931112ddf1bd8147cd1b641375f79f5825126d665480874634fd0ace",
      "output_format": "json"
    }
  }'
```

Checkpoint:

* response JSON includes a `result` object and a top-level `signature`
* response indicates successful execution (e.g., consensus info / debug info)

***

### Using your own Oracle Program on Fast

Prerequisite:

* you must already have an `oracleProgramId` from deployment (Core deploy step)

Action:

* set:
  * `execProgramId = <your oracleProgramId>`
  * `execInputs = <your program’s input schema>`

Checkpoint:

* you can specify `execInputs` exactly (no guessing)
* the response includes `result` + `signature`

***

### Execute on SEDA Fast (mainnet)

Use this when you are ready to execute against Fast mainnet.

**Source of truth (OpenAPI):**

* <https://fast-api.mainnet.seda.xyz/docs>

#### Canonical execute endpoint (mainnet)

Use the same path/query params as testnet, but with the mainnet host:

`https://fast-api.mainnet.seda.xyz/execute?includeDebugInfo=true&encoding=json`

#### Example: ETH/USD (JSON output) — mainnet

Copy/paste (replace the bearer token only):

```bash
curl -L -X POST 'https://fast-api.mainnet.seda.xyz/execute?includeDebugInfo=true&encoding=json' \
  -H 'Authorization: Bearer {{BEARER_TOKEN}}' \
  -H 'Content-Type: application/json' \
  --data-raw '{
    "execProgramId": "1b7754932d711916abe9b986c4ac9c2195e7a9efbe7445d774739966370f880a",
    "execInputs": {
      "id": "0xff61491a931112ddf1bd8147cd1b641375f79f5825126d665480874634fd0ace",
      "output_format": "json"
    }
  }'
```

Checkpoint:

* response includes `result` + `signature`
* if you receive auth errors, confirm you are using a **mainnet Fast 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.seda.xyz/home/for-agents/agent-modules/execute-on-seda-fast.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.