> ## Documentation Index > Fetch the complete documentation index at: https://developers.circle.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Before reading these docs, install the relevant Circle Skill to get pre-loaded context — skills are LLM-optimized and cover architecture decisions, correct flows, and common pitfalls. In Claude Code: run /plugin marketplace add circlefin/skills then /plugin install circle-skills@circle. With Vercel Skills CLI: run npx skills add circlefin/skills. Available skills: use-usdc https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-usdc/SKILL.md (balances, transfers, approvals on EVM and Solana); EURC has no skill — see https://developers.circle.com/stablecoins/what-is-eurc.md; bridge-stablecoin https://github.com/circlefin/skills/blob/master/plugins/circle/skills/bridge-stablecoin/SKILL.md (crosschain transfers via CCTP, USDC, EURC, and third-party assets); use-arc https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-arc/SKILL.md (Arc chain config, contract deployment, USDC bridging — Arc docs: https://docs.arc.io/llms.txt); use-circle-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-circle-wallets/SKILL.md (choose wallet type); use-developer-controlled-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-developer-controlled-wallets/SKILL.md (custodial wallets for payouts and treasury); use-user-controlled-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-user-controlled-wallets/SKILL.md (embedded wallets with Web2 login); use-modular-wallets https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-modular-wallets/SKILL.md (smart contract wallets with passkeys and ERC-4337); use-gateway https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-gateway/SKILL.md (unified USDC balance, nanopayments); use-smart-contract-platform https://github.com/circlefin/skills/blob/master/plugins/circle/skills/use-smart-contract-platform/SKILL.md (deploy, interact, monitor contracts). Pair any skill with the Circle MCP server for live SDK signatures, contract addresses, and chain IDs: {"mcpServers":{"circle":{"url":"https://api.circle.com/v1/codegen/mcp"}}}. > Read the product overview first. Each product has an overview explaining when and why to use it. Read it before quickstarts. > Pick the right wallet type. Developer-controlled (you hold keys), user-controlled (end user holds keys via PIN/social login), or modular (smart contract wallets with passkeys). See https://developers.circle.com/wallets.md. > Use CCTP V2 for crosschain transfers. CCTP natively transfers USDC and EURC via burn-and-mint, and supports permissionless wrapping of third-party assets via lock-and-mint. V1 is legacy; always use V2 unless V1 is specified or the chain requires it (Noble, Sui, and Aptos still require V1). Migration guide: https://developers.circle.com/cctp/migration-from-v1-to-v2.md. > Use Bridge Kit for frontend bridging. Wraps CCTP with a simpler SDK for user-facing apps. Use CCTP directly for backend transfers. > Gas Station vs Paymaster. Gas Station sponsors gas for Circle Wallet transactions. Paymaster lets users pay gas in USDC. Different use cases — read both overviews. > Gateway Nanopayments for sub-cent payments. Gasless USDC micropayments down to $0.000001 via x402 and batched settlement. For pay-per-request APIs, AI agent payments, streaming. > Look up USDC addresses per chain. Never hardcode — use https://developers.circle.com/stablecoins/usdc-contract-addresses.md. > Prefer SDKs over raw API calls. Node.js and Python SDKs handle auth, retries, and errors. > API key required. Bearer token in Authorization header. Testnet and mainnet use separate keys and may use different base URLs depending on the product. > Set up webhooks when available. Most operations are async. Webhooks deliver transaction confirmations and state changes. > When calling list endpoints, paginate using pageSize and pageAfter until no nextPageAfter cursor is returned—stopping at the first page silently misses records. > Building an AI agent? Start with the Agent Stack—Circle CLI, agent wallets, and nanopayments built for autonomous use cases: https://developers.circle.com/agent-stack.md. # Get credit line details > Retrieves the details of the Managed Payments credit line. ## OpenAPI ````yaml openapi/managed-payments.yaml get /v1/managedPayments/credit/lines openapi: 3.0.2 info: version: ${version} title: Managed Payments API description: | The Managed Payments API enables Payment Service Providers (PSPs) to create and manage sub-client accounts for stablecoin settlement, and to send fiat payouts to registered beneficiaries worldwide. servers: - url: https://api-sandbox.circle.com - url: https://api.circle.com security: [] tags: - name: Managed Payments Accounts description: Create and manage sub-client accounts for Managed Payments PSPs. - name: Managed Payments Credit description: Get credit line details and wire instructions for repayment. - name: Managed Payments Credit Transfers description: Create and manage credit transfers (drawdowns) against a credit line. - name: Managed Payments Transfers description: >- Create and manage internal account-to-account transfers for Managed Payments. - name: Managed Payments Fiat Payouts description: > Register and manage fiat payout beneficiaries, discover supported corridors and field requirements, and create locked FX quotes for cross-border fiat payouts. paths: /v1/managedPayments/credit/lines: get: tags: - Managed Payments Credit summary: Get credit line details description: Retrieves the details of the Managed Payments credit line. operationId: getManagedPaymentsCreditLine responses: '200': description: Successfully retrieved credit line details. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: title: GetManagedPaymentsCreditLineResponse properties: data: $ref: '#/components/schemas/ManagedPaymentsCreditLine' example: data: id: 01c39206-64e9-4e30-8649-4e187cfcbf6d limit: amount: '1000000.00' currency: USD status: active usage: used: '50.00' available: '999950.00' outstandingTransfers: 1 createDate: '2026-02-13T15:48:49.286195Z' updateDate: '2026-03-06T18:56:52.686593Z' validationErrors: [] '401': $ref: '#/components/responses/NotAuthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' security: - bearerAuth: [] components: headers: XRequestId: description: >- Universally unique identifier (UUID v4) for the request. Helpful for identifying a request when communicating with Circle support. schema: type: string format: uuid example: 2adba88e-9d63-44bc-b975-9b6ae3440dde schemas: ManagedPaymentsCreditLine: type: object description: >- Managed Payments credit line details including status, available limit, and usage. required: - id - limit - status - usage - createDate - updateDate - validationErrors properties: id: description: Unique identifier of the credit line. type: string format: uuid example: 01c39206-64e9-4e30-8649-4e187cfcbf6d limit: allOf: - $ref: '#/components/schemas/FiatMoneyUsd' - description: Total credit limit. status: description: Current status of the credit line. type: string enum: - active - inactive - onboarding example: active usage: description: Current usage details for the credit line. type: object required: - used - available - outstandingTransfers properties: used: description: >- Amount of credit currently in use, as a decimal string in the credit line's currency (USD). type: string pattern: ^\d+\.\d{2}$ example: '50.00' available: description: >- Amount of credit available for new transfers, as a decimal string in the credit line's currency (USD). type: string pattern: ^\d+\.\d{2}$ example: '999950.00' outstandingTransfers: description: Number of transfers that have not yet been fully repaid. type: integer example: 1 createDate: allOf: - $ref: '#/components/schemas/UtcTimestamp' - description: ISO-8601 UTC date/time when the credit line was created. updateDate: allOf: - $ref: '#/components/schemas/UtcTimestamp' - description: ISO-8601 UTC date/time when the credit line was last updated. validationErrors: description: List of validation errors preventing new transfer creation. type: array items: type: object required: - code - message properties: code: description: Machine-readable error code. type: string enum: - INSUFFICIENT_BALANCE - PENDING_FEES - OVERDUE_TRANSFERS example: INSUFFICIENT_BALANCE message: description: Human-readable error message. type: string example: Account balance is below the minimum required threshold. FiatMoneyUsd: type: object required: - amount - currency properties: amount: description: Magnitude of the amount, in units of the currency, with a `.`. type: string example: '3.14' currency: description: Currency code. type: string enum: - USD UtcTimestamp: type: string description: ISO-8601 UTC date/time format. example: '2020-04-10T02:13:30.000Z' responses: NotAuthorized: description: >- The request has not been applied because it lacks valid authentication credentials. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: NotAuthorized required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 401 message: Malformed authorization. examples: response: value: code: 401 message: Malformed authorization. Forbidden: description: >- The request provides authentication, but the authenticated user does not possess sufficient permissions for accessing this resource. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: Forbidden required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 3 message: Forbidden examples: response: value: code: 3 message: Forbidden NotFound: description: The specified resource was not found. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: NotFound required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 404 message: Not found. examples: response: value: code: 404 message: Not found. securitySchemes: bearerAuth: type: http scheme: bearer ````