> ## 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 a quote by ID ## OpenAPI ````yaml get /v1/quotes/{id} 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/quotes/{id}: get: tags: - Quotes summary: Get a quote by ID operationId: QuotesController_findOne_v1 parameters: - name: id required: true in: path description: Quote ID schema: type: string - name: X-API-Key in: header description: API key required: false schema: type: string responses: '200': description: Quote retrieved successfully content: application/json: schema: $ref: '#/components/schemas/QuoteResponseDto' '401': description: Unauthorized - Invalid or missing authentication credentials security: - bearer: [] x-codeSamples: - lang: bash label: CLI source: >- # Requires: npm i -g @infinite_dev/cli && export INFINITE_API_KEY=sk_sandbox_... infinite quotes get quote_abc123 - lang: text label: MCP source: Get a quote (quote_abc123). components: schemas: QuoteResponseDto: type: object properties: id: type: string description: Quote ID (only present for held quotes) example: quote_abc123 sourceAmount: description: Source amount with currency details allOf: - $ref: '#/components/schemas/MoneyOutputDto' destinationAmount: description: Destination amount with currency details allOf: - $ref: '#/components/schemas/MoneyOutputDto' exchangeRate: type: string description: Exchange rate (inclusive of all fees) example: '1.00500' infiniteFee: description: Infinite fee breakdown allOf: - $ref: '#/components/schemas/FeeBreakdownDto' developerFee: description: Developer fee breakdown allOf: - $ref: '#/components/schemas/DeveloperFeeDto' sourceRail: type: string description: Source payment rail example: ACH destinationRail: type: string description: Destination payment rail example: SWIFT expiresAt: type: string description: Quote expiration timestamp (only present for held quotes) format: date-time example: '2026-09-15T10:35:00Z' createdAt: type: string description: Quote creation timestamp format: date-time example: '2026-09-15T10:30:00Z' lockable: type: boolean description: Whether the exchange rate can be locked for 24 hours example: true route: description: Route information including timing and fee estimates allOf: - $ref: '#/components/schemas/RouteInfoDto' required: - sourceAmount - destinationAmount - exchangeRate - infiniteFee - createdAt - lockable MoneyOutputDto: type: object properties: currency: type: string description: Currency code example: USD exponent: type: number description: >- Number of decimal places for this currency (e.g., 2 for USD, 6 for USDC) example: 2 value: type: string description: Amount in smallest unit as a string example: '12345' displayValue: type: string description: Human-readable decimal value example: '123.45' required: - currency - exponent - value - displayValue FeeBreakdownDto: type: object properties: fixed: type: number description: Fixed fee amount example: null nullable: true variable: type: number description: Variable fee rate example: null nullable: true required: - fixed - variable DeveloperFeeDto: type: object properties: fixed: type: number description: Fixed fee amount example: null nullable: true variable: type: number description: Variable fee rate example: null nullable: true required: - fixed - variable RouteInfoDto: type: object properties: supported: type: boolean description: Whether this route is supported example: true flow: type: string description: Transfer flow type example: CRYPTO_TO_SWIFT summary: type: string description: Human-readable route summary example: USDC → USD totalFeeBps: type: number description: Total fee in basis points example: 2 estimate: description: Route timing estimate allOf: - $ref: '#/components/schemas/RouteEstimateDto' minimumAmount: description: >- Minimum amount for this route. Requests below this floor are rejected at transfer creation. allOf: - $ref: '#/components/schemas/MoneyOutputDto' legs: description: Individual legs of the transfer type: array items: $ref: '#/components/schemas/RouteLegDto' required: - supported RouteEstimateDto: type: object properties: estimatedReceiveAt: type: string description: Estimated time when funds will be received format: date-time example: '2026-09-17T10:30:00Z' estimatedMinutes: type: number description: Estimated duration in minutes example: 2880 nextCutoff: type: string description: Next wire cutoff time (if applicable) format: date-time example: '2026-09-15T15:00:00Z' cutoffTimezone: type: string description: Timezone for the cutoff time example: Asia/Singapore required: - estimatedReceiveAt - estimatedMinutes RouteLegDto: type: object properties: type: type: string description: Type of leg example: payout_fiat inputCurrency: type: string description: Input currency for this leg example: USDC outputCurrency: type: string description: Output currency for this leg example: USD inputRail: type: string description: Input rail for this leg example: ETHEREUM outputRail: type: string description: Output rail for this leg example: SWIFT feeBps: type: number description: Fee in basis points for this leg example: 2 settlementType: type: string description: Settlement type for this leg example: T+2 required: - type - inputCurrency - outputCurrency - inputRail - outputRail - feeBps - settlementType securitySchemes: bearer: scheme: bearer bearerFormat: API Key type: http description: API Key in Bearer format (e.g., Bearer sk_test_...) ```` ## Related topics - [Quotes and Transfers](/guides/quotes-and-transfers.md) - [MCP Server](/guides/mcp.md) - [Get transfer by ID](/api-reference/transfers/get-transfer-by-id.md) - [Get document by ID](/api-reference/documents/get-document-by-id.md) - [Get counterparty by ID](/api-reference/counterparties/get-counterparty-by-id.md)