> ## 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 account funding > Simulate inbound funding for a sandbox funding-method account (`vba_` for virtual bank accounts, including USD balance accounts; `vwa_` for virtual wallets; `pba_` for stablecoin balance accounts) using a requested rail. ## Account id Pass the funding-method account id returned when the account was created (`vba_…` for a virtual bank account, including a USD balance account; `vwa_…` for a virtual wallet; `pba_…` for a stablecoin balance account). Do not use a top-level `acct_` id. ## Infinite wallets (`inw_`) This endpoint does **not** credit Infinite wallets (`inw_…`). That includes treasury vaults and crypto deposit mailboxes created by `POST /v1/fixed-routes/virtual-wallets` (those are `INFINITE_WALLET`, not `vwa_`). To credit a treasury vault so you can test withdrawals, pick a route whose sweep target is that vault and [simulate-deposit](/api-reference/sandbox/simulate-a-fixed-route-source-deposit) with that route's source account id (`vba_…` or mailbox `inw_…`). Funds land on the destination, not the source mailbox. ## Stablecoin balance funding Fund a `pba_…` stablecoin balance account with `rail: BLOCKCHAIN` plus the `network` and `currency` the account holds (e.g. `USDT` on `ETHEREUM`). The credit posts immediately and emits a `balance.credited` webhook. Reuse `reference` to make retries idempotent. ## Sandbox settlement timing For `ACH` and `WIRE` on provider-simulated bank accounts, sandbox funds do not settle until 5:00 PM ET on weekdays to mirror production timing. Balance-account fund-in credits immediately. ## OpenAPI ````yaml post /v1/sandbox/accounts/{id}/fund-in 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/sandbox/accounts/{id}/fund-in: servers: - url: https://sandbox.api.infinite.dev description: Sandbox post: tags: - Sandbox summary: Simulate account funding description: >- Simulate inbound funding for a sandbox funding-method account (`vba_` for virtual bank accounts, including USD balance accounts; `vwa_` for virtual wallets; `pba_` for stablecoin balance accounts) using a requested rail. operationId: SandboxController_simulateFundIn_v1 parameters: - name: X-API-Key in: header description: API key required: false schema: type: string - name: id required: true in: path description: >- Funding-method account id (`vba_` for virtual bank, `vwa_` for virtual wallet, `pba_` for stablecoin balance) schema: type: string requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/SandboxFundInDto' responses: '200': description: Sandbox fund-in simulated successfully content: application/json: schema: $ref: '#/components/schemas/SandboxFundInResponseDto' '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_... # Escape hatch for any endpoint: infinite api infinite api POST /v1/sandbox/accounts/acc_abc123/fund-in \ --body '' - lang: text label: MCP source: >- Simulate account funding (acc_abc123). # Infinite MCP is read-only for this endpoint — use a dedicated MCP tool when one exists, otherwise run the CLI tab. components: schemas: SandboxFundInDto: type: object properties: rail: type: string description: Funding rail to simulate enum: - WIRE - ACH - BLOCKCHAIN example: WIRE amount: type: string description: >- Funding amount as a decimal string. Fiat rails accept up to 2 decimals; stablecoin balance funding accepts up to 6. example: '1000.00' currency: type: string description: Funding currency code example: USD network: type: string description: Blockchain network when `rail` is `BLOCKCHAIN` enum: - ETHEREUM - BASE - SOLANA - ARBITRUM - POLYGON - TRON example: BASE reference: type: string description: Optional client reference for future providers example: fund_in_123 required: - rail - amount - currency SandboxFundInResponseDto: type: object properties: accountId: type: string description: Internal account ID used for the sandbox simulation example: vba_123 amount: description: Funding amount returned in our API shape allOf: - $ref: '#/components/schemas/SandboxFundingAmountResponseDto' rail: type: string description: Funding rail simulated enum: - WIRE - ACH - BLOCKCHAIN example: WIRE transactionHash: type: string description: Blockchain transaction hash when provided by the sandbox provider example: '0x1234' required: - accountId - amount - rail SandboxFundingAmountResponseDto: type: object properties: value: type: string description: Funding amount returned as a decimal string example: '1000.00' currency: type: string description: Currency code example: USD required: - value - currency securitySchemes: bearer: scheme: bearer bearerFormat: API Key type: http description: API Key in Bearer format (e.g., Bearer sk_test_...) ```` ## Related topics - [Accounts](/concepts/accounts.md) - [Balance Accounts](/guides/balance-accounts.md) - [Simulate transfer lifecycle](/api-reference/sandbox/simulate-transfer-lifecycle.md) - [Simulate customer capabilities](/api-reference/sandbox/simulate-customer-capabilities.md) - [Fixed Routes](/concepts/fixed-routes.md)