> ## 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. # Update an external wallet ## OpenAPI ````yaml patch /v1/external-wallets/{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/external-wallets/{id}: patch: tags: - External Wallets summary: Update an external wallet operationId: ExternalWalletsController_update_v1 parameters: - name: X-API-Key in: header description: API key required: false schema: type: string - name: id required: true in: path description: External wallet ID schema: type: string requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/UpdateExternalWalletDto' responses: '200': description: External wallet updated successfully content: application/json: schema: $ref: '#/components/schemas/ExternalWalletResponseDto' '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 PATCH /v1/external-wallets/acc_abc123 \ --body '' - lang: text label: MCP source: >- Update an external wallet (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: UpdateExternalWalletDto: type: object properties: chains: type: array description: Supported chains example: - ETHEREUM - BASE items: type: string enum: - ETHEREUM - BASE - POLYGON - SOLANA - TRON - BITCOIN - ARBITRUM - ROBINHOOD currencies: description: Supported currencies example: - USDC - USDT type: array items: type: string metadata: description: Optional metadata for the account (e.g., nickname) example: nickname: Primary USDC Wallet allOf: - $ref: '#/components/schemas/AccountMetadataDto' ExternalWalletResponseDto: type: object properties: id: type: string description: Account ID example: ewa_1234567890abcdef customerId: type: string description: Customer ID example: cust_abc123 counterpartyId: type: string description: Counterparty ID when this is a third-party recipient wallet example: cp_abc123 nullable: true type: type: string enum: - EXTERNAL_WALLET description: Account type example: EXTERNAL_WALLET status: type: string enum: - IN_REVIEW - ACTIVE - CLOSED description: Account status example: IN_REVIEW metadata: description: Custom metadata for your application, including account nickname allOf: - $ref: '#/components/schemas/AccountMetadataDto' walletAddress: type: string description: Wallet address example: '0x1234567890abcdef1234567890abcdef12345678' addressType: type: string enum: - EVM - TRON - BITCOIN - SOLANA description: Wallet address type example: EVM chains: type: array description: Supported blockchain chains example: - ETHEREUM - BASE items: type: string enum: - ETHEREUM - BASE - POLYGON - SOLANA - TRON - BITCOIN - ARBITRUM - ROBINHOOD currencies: description: Supported currencies example: - USDC - USDT type: array items: type: array custodyType: type: string description: Wallet custody type used for provider custodian mapping. enum: - SELF_HOSTED - ANCHORAGE - BINANCE - BITGO - CIRCLE - COINBASE - FIREBLOCKS - GEMINI - KRAKEN - ROBINHOOD - OTHER_EXCHANGE example: SELF_HOSTED createdAt: type: string description: Account creation date format: date-time example: '2026-01-15T10:00:00Z' updatedAt: type: string description: Account last update date format: date-time example: '2026-01-15T10:00:00Z' created: type: boolean description: >- Whether this account was newly created in this request or returned from an existing match example: true required: - id - customerId - type - status - walletAddress - addressType - createdAt - updatedAt AccountMetadataDto: type: object properties: nickname: type: string description: Account nickname example: Main Checking Account maxLength: 256 purpose: type: string description: Account purpose example: Business operations maxLength: 512 tags: description: Account tags example: - primary - operations type: array items: type: string securitySchemes: bearer: scheme: bearer bearerFormat: API Key type: http description: API Key in Bearer format (e.g., Bearer sk_test_...) ```` ## Related topics - [Create an external wallet](/api-reference/external-wallets/create-an-external-wallet.md) - [Update an external account](/api-reference/external-bank-accounts/update-an-external-account.md) - [Accounts](/concepts/accounts.md) - [Update a fixed route](/api-reference/fixed-routes/update-a-fixed-route.md) - [Update transfer details](/api-reference/transfers/update-transfer-details.md)