> ## 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 all counterparties > Lists counterparties for the organization. Counterparties are organization-scoped and may be linked to many customers through external accounts (many-to-many): the same counterparty can be paid by more than one customer. Use customerId to return only counterparties linked to that customer via an account. ## OpenAPI ````yaml get /v1/counterparties 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/counterparties: get: tags: - Counterparties summary: Get all counterparties description: >- Lists counterparties for the organization. Counterparties are organization-scoped and may be linked to many customers through external accounts (many-to-many): the same counterparty can be paid by more than one customer. Use customerId to return only counterparties linked to that customer via an account. operationId: CounterpartiesController_list_v1 parameters: - name: X-API-Key in: header description: API key required: false schema: type: string - name: limit required: false in: query description: >- Number of results to return (1-1000). Use with offset for traditional pagination. schema: minimum: 1 maximum: 1000 default: 500 type: number - name: offset required: false in: query description: >- Number of results to skip. Use with limit for traditional pagination. schema: minimum: 0 default: 0 type: number - name: page_size required: false in: query description: >- Number of results per page (1-1000). Use with starting_after for cursor-based pagination. schema: minimum: 1 maximum: 1000 default: 500 type: number - name: starting_after required: false in: query description: >- Cursor for pagination. Use the ID of the last item from the previous page to get the next page. Use with page_size for cursor-based pagination. schema: type: string - name: search required: false in: query description: Search counterparties by name schema: example: Jane type: string - name: customerId required: false in: query description: >- Filter to counterparties linked to this customer through an account. Counterparties are organization-scoped and shared across customers — the same counterparty can appear for multiple customers when each has a linked account. schema: type: string example: cus_abc123 responses: '200': description: Counterparties retrieved successfully content: application/json: schema: type: object properties: data: type: array items: $ref: '#/components/schemas/CounterpartyResponseDto' total: type: number limit: type: number offset: type: number '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/counterparties \ --query limit=10 page_size=10 customerId=cus_abc123 - lang: text label: MCP source: Get all counterparties (search Jane, customerId cus_abc123). components: schemas: CounterpartyResponseDto: type: object properties: id: type: string example: cp_abc123 description: Counterparty ID name: type: string example: Jane Doe description: Counterparty legal name beneficiaryType: type: string enum: - INDIVIDUAL - BUSINESS example: INDIVIDUAL description: Entity type (individual or business) address: nullable: true description: Counterparty address type: object allOf: - $ref: '#/components/schemas/AddressDto' createdAt: type: string description: Creation timestamp format: date-time updatedAt: type: string description: Last update timestamp format: date-time required: - id - name - beneficiaryType - createdAt - updatedAt AddressDto: type: object properties: addressLine1: type: string description: Address line 1 example: 123 Main Street maxLength: 1024 addressLine2: type: string description: Address line 2 (apartment, suite, etc.) example: Apt 4B maxLength: 1024 city: type: string description: City example: San Francisco maxLength: 256 state: type: string description: State / Province example: CA maxLength: 256 postalCode: type: string description: >- Postal code / ZIP code. May be empty for countries without a postal-code system, including the United Arab Emirates. example: '94102' maxLength: 50 country: type: string description: Country code (ISO 3166-2) example: US minLength: 2 maxLength: 2 transliterated: description: >- Transliterated address fields (Latin characters) for non-Latin addresses. Required when address contains non-Latin characters (Chinese, Arabic, Cyrillic, etc.). allOf: - $ref: '#/components/schemas/TransliteratedAddressDto' required: - addressLine1 - city - postalCode - country TransliteratedAddressDto: type: object properties: addressLine1: type: string description: Transliterated address line 1 (Latin characters) example: 123 Main Street maxLength: 1024 addressLine2: type: string description: Transliterated address line 2 (Latin characters) example: Apt 4B maxLength: 1024 city: type: string description: Transliterated city (Latin characters) example: Beijing maxLength: 256 state: type: string description: Transliterated state/province (Latin characters) example: Hebei maxLength: 256 securitySchemes: bearer: scheme: bearer bearerFormat: API Key type: http description: API Key in Bearer format (e.g., Bearer sk_test_...) ```` ## Related topics - [Get counterparty by ID](/api-reference/counterparties/get-counterparty-by-id.md) - [Get all accounts](/api-reference/accounts/get-all-accounts.md) - [Get all customers](/api-reference/customers/get-all-customers.md) - [Get all webhook endpoints](/api-reference/webhooks/get-all-webhook-endpoints.md) - [Delete a counterparty](/api-reference/counterparties/delete-a-counterparty.md)