> ## 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. # Simulate the deposit for an FX trade (sandbox only) > Sandbox only — always returns 403 in production. Simulates the deposit arriving for a trade in `AWAITING_DEPOSIT`, standing in for the on-chain transfer (crypto-source) or the bank wire (fiat-source, which cannot be sent in sandbox). The trade then advances through its normal lifecycle asynchronously: poll `GET /v1/fx/trades/{tradeId}` or subscribe to FX trade webhooks to observe the transition. ## OpenAPI ````yaml post /v1/fx/trades/{tradeId}/simulate-deposit 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/trades/{tradeId}/simulate-deposit: post: tags: - FX summary: Simulate the deposit for an FX trade (sandbox only) description: >- Sandbox only — always returns 403 in production. Simulates the deposit arriving for a trade in `AWAITING_DEPOSIT`, standing in for the on-chain transfer (crypto-source) or the bank wire (fiat-source, which cannot be sent in sandbox). The trade then advances through its normal lifecycle asynchronously: poll `GET /v1/fx/trades/{tradeId}` or subscribe to FX trade webhooks to observe the transition. operationId: FxTradeController_simulateDeposit_v1 parameters: - name: X-API-Key in: header description: API key required: false schema: type: string - name: tradeId required: true in: path description: Trade ID (tfr_…) schema: type: string responses: '202': description: >- Simulation accepted. The trade advances asynchronously as the simulated funds settle. content: application/json: schema: $ref: '#/components/schemas/FxTradeSimulationResponseDto' '401': description: Unauthorized - Invalid or missing authentication credentials '403': description: Simulation is sandbox-only and not available in production. '404': description: Trade does not exist for the calling organization. '409': description: Trade is not in `AWAITING_DEPOSIT`. 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 POST /v1/fx/trades/fx_abc123/simulate-deposit - lang: text label: MCP source: >- Simulate the deposit for an FX trade (sandbox only) (fx_abc123). # Infinite MCP is read-only for this endpoint — use a dedicated MCP tool when one exists, otherwise run the CLI tab. components: schemas: FxTradeSimulationResponseDto: type: object properties: simulated: type: boolean description: Always `true` — the simulation request was accepted. example: true note: type: string description: >- Human-readable note about what happens next. The trade advances asynchronously; poll `GET /v1/fx/trades/{tradeId}` or subscribe to FX trade webhooks to observe the transition. example: >- Deposit simulation accepted. The trade will advance automatically as the simulated funds settle. required: - simulated - note securitySchemes: bearer: scheme: bearer bearerFormat: API Key type: http description: API Key in Bearer format (e.g., Bearer sk_test_...) ```` ## Related topics - [Simulate the payout for an FX trade (sandbox only)](/api-reference/fx/simulate-the-payout-for-an-fx-trade-sandbox-only.md) - [Read an FX trade](/api-reference/fx/read-an-fx-trade.md) - [Simulate a fixed-route source deposit](/api-reference/sandbox/simulate-a-fixed-route-source-deposit.md) - [Simulate customer capabilities](/api-reference/sandbox/simulate-customer-capabilities.md) - [Simulate transfer lifecycle](/api-reference/sandbox/simulate-transfer-lifecycle.md)