> ## 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 payment outcome intent ## OpenAPI ````yaml get /v1/payment-outcome-intents/{intentId} 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/payment-outcome-intents/{intentId}: get: tags: - Payment outcome intents summary: Get a payment outcome intent operationId: PaymentOutcomeIntentsController_get_v1 parameters: - name: X-API-Key in: header description: API key required: false schema: type: string - name: intentId required: true in: path description: Intent id (`oint_…`). schema: type: string responses: '200': description: '' content: application/json: schema: $ref: '#/components/schemas/PaymentOutcomeIntentResponseDto' '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 GET /v1/payment-outcome-intents/ - lang: text label: MCP source: Get a payment outcome intent (). components: schemas: PaymentOutcomeIntentResponseDto: type: object properties: id: type: string example: oint_abc123 organizationId: type: string customerId: type: string outcomeText: type: string requesterId: type: string status: type: string enum: - OPEN - APPROVED - REJECTED draftLinks: type: array items: $ref: '#/components/schemas/PaymentOutcomeIntentDraftLinkResponseDto' sealedPlan: nullable: true description: >- Omitted when sealed legs would expose internal account ids; sealedPlanHash remains authoritative. type: object allOf: - $ref: '#/components/schemas/SealedPaymentPlanDto' sealedPlanHash: type: string nullable: true sealedPlanSignature: type: string nullable: true description: >- HMAC-SHA256 hex over sealedPlanHash. Set when Infinite approves (ENG-2002). sealedAt: type: string format: date-time nullable: true sealedBy: type: string nullable: true createdAt: format: date-time type: string updatedAt: format: date-time type: string required: - id - organizationId - customerId - outcomeText - requesterId - status - draftLinks - sealedPlan - sealedPlanHash - sealedPlanSignature - sealedAt - sealedBy - createdAt - updatedAt PaymentOutcomeIntentDraftLinkResponseDto: type: object properties: id: type: string draftKind: type: string enum: - PAYEE_DRAFT - TRANSFER_DRAFT draftId: type: string linkedAt: format: date-time type: string required: - id - draftKind - draftId - linkedAt SealedPaymentPlanDto: type: object properties: v: type: number example: 1 legs: type: array items: $ref: '#/components/schemas/SealedPaymentPlanLegDto' required: - v - legs SealedPaymentPlanLegDto: type: object properties: legIndex: type: number sourceAmountMinor: type: string description: Source spend in minor units. sourceCurrency: type: string sourceAccountId: type: string sourceRail: type: string destinationAmountMinor: type: string description: Destination payout in minor units. destinationCurrency: type: string payeeAccountId: type: string destinationRail: type: string required: - legIndex - sourceAmountMinor - sourceCurrency - sourceAccountId - sourceRail - destinationAmountMinor - destinationCurrency - payeeAccountId - destinationRail securitySchemes: bearer: scheme: bearer bearerFormat: API Key type: http description: API Key in Bearer format (e.g., Bearer sk_test_...) ```` ## Related topics - [Create a payment outcome intent](/api-reference/payment-outcome-intents/create-a-payment-outcome-intent.md) - [Link a Lane A draft to an intent](/api-reference/payment-outcome-intents/link-a-lane-a-draft-to-an-intent.md) - [Evaluate a mandate against a sealed plan or draft proposal](/api-reference/mandates/evaluate-a-mandate-against-a-sealed-plan-or-draft-proposal.md) - [Quote a transfer intent](/api-reference/transfers/quote-a-transfer-intent.md) - [Confirm an unlocked transfer intent](/api-reference/transfers/confirm-an-unlocked-transfer-intent.md)