> ## Documentation Index
> Fetch the complete documentation index at: https://docs.infinite.net/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 today at https://mcp.infinite.dev/mcp (Streamable HTTP, production) or legacy https://bot.api.infinite.dev/mcp — customer/BYO org members and returning Infinite Connect users; not https://connect.infinite.dev/mcp until Infinite announces Connect MCP is live. First-time Infinite Connect net-new onboarding is operator-assisted until then. After Infinite announces Connect MCP is live, customer/BYO org members keep the org URL; Infinite Connect users (net-new and returning Connect-only) sign in at https://connect.infinite.dev/mcp. Wrong URL may return API 403 codes (mcp_connect_url_required, mcp_org_url_required) or bot 401 when the token audience does not match the host; see https://docs.infinite.dev/guides/mcp.md. Send `Authorization: Bearer <key>` to https://mcp.infinite.dev/mcp/sse or legacy https://bot.api.infinite.dev/mcp/sse. Prefer MCP 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): today use operator-assisted onboarding only (not self-serve Auth Kit net-new on the org MCP URL; not the shared platform org API key in personal MCP config). After Infinite announces Connect MCP is live, net-new users self-serve via Auth Kit at https://connect.infinite.dev/mcp with restricted Connect membership. BYO org keys onboard under that customer's org id. Connect 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), transfer drafts that wait for Infinite approval (`create_transfer_draft` / `get_transfer_draft`; never POST /v1/transfers), and with a bound customer, `create_transfer` (real POST /v1/transfers, forced IN_REVIEW until Infinite ops approve; not on BYO org keys). An agent key (`sk_sandbox_agent_…` / `sk_live_agent_…`) on a **PAYMENT**-role agent moves money within that agent's limits: `create_transfer` (draft) → `submit_transfer` → `wait_for_transfer`, without per-payment Infinite approval. **PAYMENT_OPERATIONS** agent keys are read-only (no `get_quote`, `create_transfer`, or `submit_transfer`; use `get_quote_by_id` and `list_transfers` on the pinned customer).
> 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 org API keys may pass `customerId` on each call without binding. Platform Connect AuthKit: `create_business_customer` / `create_individual_customer` attempt to bind the session on success; if the response includes `bindError`, call `bind_session_customer` with the returned `continuationToken` before any other customer-scoped tool. OAuth rejects `X-Infinite-On-Behalf-Of` — use bind + `continuationToken` after create or reconnect. Platform org API keys may use `X-Infinite-On-Behalf-Of` to pin a customer.
> 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.

# List customers linked by shared fraud signals

> Returns customers in the same organization linked to the subject by shared signals (email, wallet, bank identifier). EVM addresses compare lowercased. Subject is excluded.



## OpenAPI

````yaml get /v1/customers/{id}/linked
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/customers/{id}/linked:
    get:
      tags:
        - Customers
      summary: List customers linked by shared fraud signals
      description: >-
        Returns customers in the same organization linked to the subject by
        shared signals (email, wallet, bank identifier). EVM addresses compare
        lowercased. Subject is excluded.
      operationId: FraudLinksController_listLinked_v1
      parameters:
        - name: X-API-Key
          in: header
          description: API key
          required: false
          schema:
            type: string
        - name: id
          required: true
          in: path
          description: Subject customer ID
          schema:
            type: string
        - name: limit
          required: false
          in: query
          description: Max groups to return per signal kind
          schema:
            example: 10
            type: string
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FraudLinksResponseDto'
        '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 <METHOD> <path>

            infinite api GET /v1/customers/cus_abc123/linked \
              --query limit=10
        - lang: text
          label: MCP
          source: List customers linked by shared fraud signals (cus_abc123).
components:
  schemas:
    FraudLinksResponseDto:
      type: object
      properties:
        customerId:
          type: string
          description: Subject customer ID
        groups:
          description: >-
            Clusters of related customers grouped by the shared signal (ring
            members only, not a transitive closure).
          type: array
          items:
            $ref: '#/components/schemas/FraudLinkGroupDto'
      required:
        - customerId
        - groups
    FraudLinkGroupDto:
      type: object
      properties:
        kind:
          type: string
          description: Link signal kind
          enum:
            - EMAIL
            - WALLET
            - BANK
        signal:
          type: string
          description: >-
            Signal value. Wallets show full address; bank identifiers are masked
            to last4 only.
          example: user@example.com
        customers:
          description: Linked customers sharing this signal (subject excluded, org-scoped).
          type: array
          items:
            $ref: '#/components/schemas/FraudLinkedCustomerDto'
      required:
        - kind
        - customers
    FraudLinkedCustomerDto:
      type: object
      properties:
        id:
          type: string
          description: Customer ID
          example: cus_123
        customerName:
          type: string
          description: Display name (when available)
          example: Acme Corp
      required:
        - id
  securitySchemes:
    bearer:
      scheme: bearer
      bearerFormat: API Key
      type: http
      description: API Key in Bearer format (e.g., Bearer sk_test_...)

````

## Related topics

- [List fixed routes for a customer](https://docs.infinite.net/api-reference/customers/list-fixed-routes-for-a-customer.md)
- [List mandates for a customer](https://docs.infinite.net/api-reference/mandates/list-mandates-for-a-customer.md)
- [List customer RFIs](https://docs.infinite.net/api-reference/rfis/list-customer-rfis.md)
- [Get all counterparties](https://docs.infinite.net/api-reference/counterparties/get-all-counterparties.md)
- [List documents](https://docs.infinite.net/api-reference/documents/list-documents.md)
