> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paywithlocus.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Poll an agent funding handoff

> Returns ready only after the signed Stripe webhook has been durably consumed and the credit ledger balance is usable.



## OpenAPI

````yaml /api-reference/openapi.json get /credits/agent/funding-sessions/{sessionId}
openapi: 3.1.0
info:
  title: Locus Pro API
  description: >-
    Production is live at https://api.paywithlocus.com/api. Stage remains
    available for evaluation and integration testing at
    https://api.stage.paywithlocus.com/api; credentials, balances, and tenant
    data are isolated by environment. Embedded prepaid credits over the Locus
    pay-per-use catalog. Money and top-up amounts use exact decimal strings (up
    to 6dp). Every burn requires an Idempotency-Key header. Management routes
    accept a tenant secret key or authorized dashboard session as shown per
    operation. Widget routes accept an end-user JWT alone; when a publishable
    key is present it must belong to the JWT's tenant. MCP uses OAuth 2.1
    Authorization Code with PKCE by default and also accepts the explicitly
    documented tenant secret key, end-user JWT, or scoped agent connection
    compatibility credentials. Burns accept the execution credentials shown per
    operation. Publishable keys never authorize management or burns by
    themselves.
  version: 0.6.0
servers:
  - url: https://api.paywithlocus.com/api
    description: Production
  - url: https://api.stage.paywithlocus.com/api
    description: Stage — evaluation and integration testing
security:
  - secretKey: []
tags:
  - name: Authentication
    description: Email-verified self-serve account creation and dashboard identity
  - name: Tenants
    description: Tenant profile, keys, and settings (dashboard session or secret key)
  - name: Workspace members
    description: Invite-only human workspace membership and role administration
  - name: Catalog
    description: Enable/disable APIs and set markups
  - name: Custom APIs
    description: >-
      Available when enabled for the workspace. Enterprise BYOK providers and
      schema-backed custom actions
  - name: End users
    description: End-user accounts, tokens, and allocations
  - name: Top-ups
    description: Locus-hosted checkout top-ups and quotes
  - name: Ledger
    description: Burn/top-up history and earnings
  - name: Webhooks
    description: Signed events, delivery inspection, and replay
  - name: Burn
    description: Metered pay-per-use calls
  - name: Travel routing
    description: >-
      Available when enabled for the workspace. Multi-provider flight search,
      no-dispatch planning, and feedback
  - name: MCP
    description: Stateless Streamable HTTP transport and MCP tool-result contracts
  - name: Okibi Identity
    description: >-
      Available when enabled for the workspace. Okibi identity verification and
      scoped native CLI credential bootstrap
  - name: Widget
    description: End-user JWT surface; a matching publishable key is optional
  - name: Agent-native onboarding
    description: >-
      Self-registration, human Stripe funding handoff, and restricted account
      setup for headless agents
  - name: Agent connections
    description: Scoped, expiring, revocable credentials for agent execution
  - name: Capability routing
    description: Outcome-level web search and research across eligible catalog providers
paths:
  /credits/agent/funding-sessions/{sessionId}:
    get:
      tags:
        - Agent-native onboarding
      summary: Poll an agent funding handoff
      description: >-
        Returns ready only after the signed Stripe webhook has been durably
        consumed and the credit ledger balance is usable.
      parameters:
        - name: sessionId
          in: path
          required: true
          schema:
            type: string
            pattern: ^cs_
      responses:
        '200':
          description: Current authenticated funding state
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AgentFundingStatus'
        '404':
          description: Session does not belong to this agent account
      security:
        - agentConnection: []
components:
  schemas:
    AgentFundingStatus:
      type: object
      additionalProperties: false
      required:
        - success
        - fundingSessionId
        - state
        - paymentStatus
        - balance
        - nextAction
      properties:
        success:
          const: true
        fundingSessionId:
          type: string
          pattern: ^cs_
        state:
          $ref: '#/components/schemas/AgentFundingState'
        paymentStatus:
          type: string
        balance:
          $ref: '#/components/schemas/AgentOwnedBalance'
        nextAction:
          type: object
          additionalProperties: true
    AgentFundingState:
      type: string
      enum:
        - awaiting_payment
        - processing
        - ready
        - expired
        - failed
    AgentOwnedBalance:
      type: object
      additionalProperties: false
      required:
        - usd
        - credits
        - creditsPerDollar
      properties:
        usd:
          $ref: '#/components/schemas/DecimalString'
        credits:
          $ref: '#/components/schemas/DecimalString'
        creditsPerDollar:
          type: string
          pattern: ^\d+$
    DecimalString:
      type: string
      pattern: ^\d+(?:\.\d{1,6})?$
      description: >-
        Non-negative exact decimal string with at most six fractional digits.
        Endpoint-specific positivity and amount limits still apply.
  securitySchemes:
    secretKey:
      type: http
      scheme: bearer
      description: Tenant secret key (lcr_…). Server-side only.
    agentConnection:
      type: http
      scheme: bearer
      description: >-
        Scoped lcac_ credential. Tenant-managed Agent Connections authorize only
        their bound MCP and wrapped execution surfaces. A bootstrap connection
        for a self-registered agent additionally authorizes the explicit
        /credits/agent/* self-service routes for its own account; neither form
        authorizes general tenant management.

````