> ## Documentation Index > Fetch the complete documentation index at: https://docs.infinite.dev/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > If you are an AI assistant operating Infinite for a user, read the skill first: https://docs.infinite.dev/agent-skill.md (setup per host, tool reference, rules for moving money, journeys). > When operating Infinite for a user, use the MCP server. Sign in at https://bot.api.infinite.dev/mcp (production, acts as the user) or send `Authorization: Bearer ` to https://bot.api.infinite.dev/mcp/sse. Prefer its tools over raw HTTP; use REST only for steps no tool covers, and check `get_endpoint_schema` before guessing a request shape. > Net-new Infinite Connect (org_connect) is operator-assisted: do not grant end users shared org_connect Auth Kit membership or the shared platform org API key — those credentials are org-wide on /v1. BYO org keys onboard under that customer's org id. Operator sessions should show org_connect in get_organization_info. > The key decides the tools. Every organization key (`sk_sandbox_…` / `sk_live_…`) gets docs, onboarding, `get_account_balance`, and request logs for your own organization. BYO organizations add payees an agent will pay with `create_payee` (payable once ACTIVE). Platform Connect sessions instead get bound-customer payment lookups (`get_quote`, `get_transfer`, `list_transfers`, `list_account_balances`), payee drafts (`create_payee_draft` / `get_payee_draft`; screening only, never payable), and transfer drafts that wait for Infinite approval (`create_transfer_draft` / `get_transfer_draft`; never POST /v1/transfers). Where offered, platform `create_transfer` files a real transfer that Infinite holds in review before funding; it cannot be submitted from DRAFT. > An agent key (`sk_sandbox_agent_…` / `sk_live_agent_…`) moves money within that agent's limits: `create_transfer` → `submit_transfer` → `wait_for_transfer`. > On sandbox organization-key sessions, `sandbox_approve_customer` (makes the capabilities you pass READY, and related ones may turn READY too; `request_capabilities` is not needed), `sandbox_fund_account`, and `sandbox_complete_transfer` stand in for verification, funding, and settlement, so a whole flow runs from MCP. BYO keys can pass `customerId` on each call without binding; platform sessions must bind a customer first (`create_business_customer` auto-binds, or send `X-Infinite-On-Behalf-Of`). > When searching documentation without a key, use the docs MCP at https://docs.infinite.dev/mcp. > Start in sandbox (https://sandbox.api.infinite.dev). Do not use production unless the user explicitly asks. > Confirm amount, currency, and payee with the user before any payment is submitted. Pass the invoice number as `reference` on `create_transfer`; the summary says what the payee will see. > REST amounts are integer minor units (`"4000"` = 40.00 USD). MCP payment tools take exact decimal strings (`"40.00"`). Never mix them. > Agent denials return `403 { denial: { code, message, window, limit, used, remaining, attemptedAmount, currency }, hint }` with decimal amounts; per-transfer denials omit `used` and `remaining`. Report them to the user; do not work around them. # Get an indicative FX rate for a pair > Returns an indicative (cached, ~30s-fresh) mid-market reference rate with the calling organization’s spread applied. Use this for browse/UX surfaces. This endpoint takes no amount — per-corridor amount limits apply only when committing to a firm price via `POST /v1/fx/quotes`. ## OpenAPI ````yaml get /v1/fx/rates openapi: 3.0.0 info: title: Infinite API description: API for Infinite version: '1.0' contact: {} servers: - url: https://sandbox.api.infinite.dev description: Sandbox - url: https://api.infinite.dev description: Production security: [] tags: - name: Accounts description: Virtual and external account management - name: Customers description: Customer identity management - name: Documents description: Document upload and management - name: Fixed Routes description: Fixed route management - name: External Bank Accounts description: External bank account management - name: External Wallets description: External wallet management - name: Infinite Wallets description: Infinite Wallet management - name: Organizations description: Organization management - name: Quotes description: Quote creation and management - name: Transfers description: Money movement and transaction tracking - name: Verification description: Identity verification workflows - name: Terms of Service description: Terms of Service acceptance - name: Health description: System health and monitoring - name: Sandbox description: Sandbox utilities paths: /v1/fx/rates: get: tags: - FX summary: Get an indicative FX rate for a pair description: >- Returns an indicative (cached, ~30s-fresh) mid-market reference rate with the calling organization’s spread applied. Use this for browse/UX surfaces. This endpoint takes no amount — per-corridor amount limits apply only when committing to a firm price via `POST /v1/fx/quotes`. operationId: FxRateController_getRate_v1 parameters: - name: X-API-Key in: header description: API key required: false schema: type: string - name: sourceCurrency required: true in: query schema: type: string example: USDT - name: sourceNetwork required: false in: query description: >- Network for crypto source (e.g. BASE, ETHEREUM). Required when source is a crypto asset; must be omitted when source is fiat. schema: type: string example: BASE - name: sourceRail required: false in: query description: >- Rail for fiat source (SEPA, SEPA_INSTANT, FASTER_PAYMENTS). Required when source is fiat; must be omitted when source is crypto. For EUR onramp prefer `SEPA`; `SEPA_INSTANT` remains accepted. Slow EUR rails are not available today. schema: example: SEPA type: string - name: destinationCurrency required: true in: query schema: type: string example: USDC - name: destinationNetwork required: false in: query description: >- Network for crypto destination. Required when destination is a crypto asset; must be omitted when destination is fiat. schema: type: string example: BASE - name: destinationRail required: false in: query description: >- Rail for fiat destination (SEPA, SWIFT, ACH). Required when destination is fiat; must be omitted when destination is crypto. schema: example: SEPA type: string - name: onBehalfOf required: false in: query description: >- Customer the rate is browsed for. **Required** when either leg is fiat (GBP/EUR) — fiat pairs quote against per-customer Codex credentials. Optional on stablecoin pairs: pass the customer that will later request the firm quote when they have customer-specific pricing (e.g. market-rate pin) so the indicative rate matches it. schema: type: string example: cus_abc123 responses: '200': description: Indicative rate. content: application/json: schema: $ref: '#/components/schemas/FxRateResponseDto' '400': description: >- Invalid pair shape (mismatched network/rail slots), the fiat source rail is not yet supported (`fx_source_rail_not_supported` — send `SEPA` or `SEPA_INSTANT` for EUR onramp or `FASTER_PAYMENTS` for GBP; slow rails such as SWIFT are not available today), or a fiat pair was requested without `onBehalfOf` (`fx_rates_on_behalf_of_required`). '401': description: Unauthorized - Invalid or missing authentication credentials '403': description: >- The indicative-rates endpoint is not enabled for this organization (`fx_rates_not_enabled`), or fiat pairs are not enabled (`fx_fiat_pairs_not_enabled`). '404': description: >- The requested pair is not supported by any vendor (`fx_pair_unsupported`). '409': description: >- FX is not enabled for this organization on the given pair (`fx_not_enabled_for_pair`). '422': description: >- No rate is available for the pair right now (`fx_quote_capacity_exhausted` / `fx_quote_temporarily_unavailable`). The body includes a `hint` with a human-readable explanation; `limits`/`requested` are never present on this endpoint (it takes no amount). content: application/json: schema: $ref: '#/components/schemas/FxNotExecutableResponseDto' security: - bearer: [] - bearer: [] x-codeSamples: - lang: bash label: CLI source: >- # Requires: npm i -g @infinite_dev/cli && export INFINITE_API_KEY=sk_sandbox_... # Escape hatch for any endpoint: infinite api infinite api GET /v1/fx/rates \ --query sourceCurrency=USDT destinationCurrency=USDC - lang: text label: MCP source: >- Get an indicative FX rate for a pair (sourceCurrency USDT, destinationCurrency USDC, sourceNetwork BASE). components: schemas: FxRateResponseDto: type: object properties: rate: type: string description: >- Indicative all-in customer rate for `destinationCurrency / sourceCurrency`, post-spread. Not a firm quote — request `POST /v1/fx/quotes` to commit a price. example: '0.99975' asOf: type: string description: >- When the underlying reference rate was sourced (ISO 8601). Rates are cached briefly to stay inside vendor budgets; this is the cache anchor, not a per-request timestamp. example: '2026-05-26T19:42:00.000Z' pairKey: type: string description: Canonical SOURCE:DEST pair key (uppercase). example: USDT:USDC source: type: string description: >- Always `reference` for this endpoint. Discriminator left open for future indicative-rate sources without changing the response shape. enum: - reference example: reference required: - rate - asOf - pairKey - source FxNotExecutableResponseDto: type: object properties: message: type: string description: Stable error code. enum: - fx_quote_capacity_exhausted - fx_quote_amount_too_small - fx_quote_amount_too_large - fx_quote_temporarily_unavailable example: fx_quote_amount_too_large hint: type: string description: Human-readable explanation. example: Amount is above the maximum for this corridor. limits: description: >- Per-corridor source-amount bounds. Present only for the `fx_quote_amount_too_small` / `fx_quote_amount_too_large` codes on `POST /v1/fx/quotes`, and only when available. allOf: - $ref: '#/components/schemas/FxNotExecutableLimitsDto' requested: type: string description: >- The originally requested source amount in minor units. Present only alongside `limits`. example: '100000000' required: - message - hint FxNotExecutableLimitsDto: type: object properties: sourceCurrency: type: string example: USDC min: type: string description: Minimum source amount in minor units. example: '0' max: type: string description: Maximum source amount in minor units. example: '10000000' required: - sourceCurrency - min - max securitySchemes: bearer: scheme: bearer bearerFormat: API Key type: http description: API Key in Bearer format (e.g., Bearer sk_test_...) ```` ## Related topics - [List FX pairs enabled for the organization](/api-reference/fx/list-fx-pairs-enabled-for-the-organization.md) - [Create a firm FX quote](/api-reference/fx/create-a-firm-fx-quote.md) - [Read an FX trade](/api-reference/fx/read-an-fx-trade.md) - [Infinite skill for AI assistants](/agent-skill.md) - [Accept a firm FX quote and create a trade](/api-reference/fx/accept-a-firm-fx-quote-and-create-a-trade.md)