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

> ## Agent Instructions
> Agentcard is for companies whose agent buys for their users. Pick one path: the opencommerce SDK (@agent-cards/commerce-sdk) gives your agent one buy tool that finds the product, builds the cart, gets the user's approval and places the order at real stores; the Agentcard SDK (@agent-cards/sdk) pays with the user's own card when your agent already shops in a browser (Browser Use, Kernel, Browserbase, Anchor or Notte); the Purchase API (POST /buy) does the same purchase flow over plain HTTP in any language; Issuing gives the agent its own card.
> Start with `npx agent-cards init` in the app's folder (Node 22 or later). No invite is needed: it creates your Agentcard account if you don't have one, installs the opencommerce SDK and puts the credentials in the env file, kept out of git. From a coding agent, run `npx agent-cards init --print --categories all --implementation tool --wallet vault --skip-install` to get the setup steps to apply yourself.
> Vault is by invitation: request it at https://agentcard.com/get-started?utm_source=docs&utm_medium=llms&utm_campaign=agent-instructions. opencommerce needs no invite.
> Never ask a user for a card number, expiry date or CVV in chat. Send them the Vault link; they add their card on Agentcard's page, and the agent never sees the number.
> Every purchase is approved by the user, with a passkey or Face ID, or by an auto-approval they granted. An approval covers one merchant and one exact total. If the total changes, ask again. When a result says the user already said yes, don't ask again.
> `init` writes PRODUCTION credentials, which place real orders, so test in sandbox first. For opencommerce, run `npx agent-cards credentials --mode sandbox` and put the two lines it prints in place of the production ones in the env file `init` wrote, because that command only prints them; sandbox then runs the whole flow against real stores and stops before payment, so no order is placed and nobody is charged. For Vault and Issuing, sandbox credentials issue test cards that no real merchant accepts; try the checkout against shop.agentcard.sh, a test store on Stripe test mode.
> Tell the user an order is placed only after Agentcard reports it placed.
> Vault is free up to 5,000 users (https://agentcard.com/pricing). opencommerce takes 1% of each completed order. Full docs in one file: https://docs.agentcard.com/llms-full.txt

# Disconnect a user

> End your app's connection to a user. Your app can no longer read their cards or ask them to pay.

Call it when the user asks your app to forget them. Every token your app holds for the user stops working, links you sent them stop opening, and the user's cards stay in their Vault.

```bash cURL theme={null}
curl -X DELETE https://api.agentcard.sh/api/v2/vault_users/usr_8f3k2m/connection \
  -H "Authorization: Bearer $ORG_TOKEN"
```

```json 200 theme={null}
{
  "object": "vault_user_connection",
  "user_id": "usr_8f3k2m",
  "connected": false,
  "revoked_tokens": 2,
  "revoked_wallet_links": 0,
  "revoked_sessions": 1,
  "test_mode": false
}
```

After the call, [List a user's vaulted cards](https://docs.agentcard.com/api-reference/vault/cards-list.md) answers `404 connection_not_found` for the user, and a checkout authorization for them is refused. To work with the user again, send them a new [vault session](https://docs.agentcard.com/api-reference/vault/sessions-create.md).

Call it as often as you like. A second call answers `200` with every count at `0`.

## Errors

A user your app never connected is refused, so the call tells you nothing about anyone else's users:

```text theme={null}
HTTP 404
{
  "error": {
    "code": "connection_not_found",
    "message": "No production connection exists for that user under this client.",
    "docs": "https://docs.agentcard.sh"
  }
}
```

The tokens stop working before the user's auto-approval for your app does. While the second half is still in flight, the call answers:

```text theme={null}
HTTP 503
{
  "error": {
    "code": "partner_disconnect_pending",
    "message": "The connection is off. The payment authority has not confirmed yet: call again to check.",
    "docs": "https://docs.agentcard.sh"
  }
}
```

| Code | Meaning | What to do |
| - | - | - |
| `404 connection_not_found` | Your app holds no connection to that user in this mode. | Check the `user_id`, and that you called with the token of the mode the user connected in. |
| `503 partner_disconnect_pending` | The tokens are off. The user's auto-approval for your app is not yet. | Call again until it answers `200`. The tokens stay off either way. |

Deleting one vault session with `DELETE /api/v2/vault_sessions/{id}` ends only that link and the token it gave you. The user stays connected to your app.


## OpenAPI

````yaml openapi.json DELETE /api/v2/vault_users/{user_id}/connection
openapi: 3.1.0
info:
  title: Agentcard API
  version: 2.0.0
  description: >-
    The Agentcard v2 API — connect your users and verify their identity from
    your own backend. Every call is authenticated with a platform access token
    minted from your `client_id` + `client_secret`.
servers:
  - url: https://api.agentcard.sh
    description: >-
      There is one base URL. Sandbox vs production is decided by the client
      credential you use, never by the host.
security:
  - platformToken: []
tags:
  - name: Authentication
    description: >-
      Exchange your client credentials for a platform access token, and
      introspect what a token acts as.
  - name: Connect
    description: >-
      Connect a user to your platform: send a one-time code, verify it, record
      consent, and keep the connection alive.
  - name: Identity verification
    description: >-
      Verify a connected user's identity: upload their ID, submit any extra
      fields we ask for, then show a short face scan.
paths:
  /api/v2/vault_users/{user_id}/connection:
    delete:
      tags:
        - Connect
      summary: Disconnect a user
      description: >-
        Ends your app's connection to a user. Every token your app holds for the
        user stops working, Vault session links they have not opened stop
        opening, and their cards stay in their Vault. Idempotent: a second call
        answers `200` with every count at `0`.
      operationId: vaultUserConnectionDelete
      parameters:
        - name: user_id
          in: path
          required: true
          description: The user's id, as your app stored it when they connected.
          schema:
            type: string
            maxLength: 64
      responses:
        '200':
          description: The user is disconnected from your app.
          content:
            application/json:
              schema:
                type: object
                properties:
                  object:
                    type: string
                    enum:
                      - vault_user_connection
                  user_id:
                    type: string
                  connected:
                    type: boolean
                    enum:
                      - false
                  revoked_tokens:
                    type: integer
                    description: >-
                      Tokens your app held for the user that stopped working on
                      this call.
                  revoked_wallet_links:
                    type: integer
                    description: >-
                      Wallet links your app sent the user that stopped working
                      on this call.
                  revoked_sessions:
                    type: integer
                    description: >-
                      Vault session links the user had not opened yet. A
                      disconnected user who taps one gets nothing.
                  test_mode:
                    type: boolean
              example:
                object: vault_user_connection
                user_id: usr_8f3k2m
                connected: false
                revoked_tokens: 2
                revoked_wallet_links: 0
                revoked_sessions: 1
                test_mode: false
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          description: >-
            `connection_not_found`: your app holds no connection to that user in
            this mode.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '503':
          description: >-
            `partner_disconnect_pending`: the tokens are off, and the user's
            auto-approval for your app is not yet. Call again until it answers
            `200`.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  responses:
    Unauthorized:
      description: >-
        `unauthorized` — the platform access token is missing or expired.
        Exchange your client credentials for a fresh one.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    Error:
      type: object
      description: Every v2 error uses the same envelope.
      properties:
        error:
          type: object
          properties:
            code:
              type: string
              description: A stable, machine-readable string (snake_case). Branch on this.
            message:
              type: string
              description: A human-readable explanation, safe to log.
            docs:
              type: string
              description: A link back to the reference.
            field_errors:
              type: object
              additionalProperties:
                type: string
              description: Only on `invalid_fields` — names each field to fix.
            warnings:
              type: array
              items:
                type: string
              description: >-
                Only on document upload errors — actionable feedback safe to
                show the user.
            status:
              type: string
              description: >-
                Only on `verification_terminally_rejected` — the user's current
                verification status, which this call did not change.
            reason:
              type: string
              description: >-
                The detail behind the failure, on the errors that carry one: on
                `verification_terminally_rejected` an end-user-safe explanation
                of the rejection, when the review left one; on `invalid_code`
                and `invalid_return_url` which part of the input was refused.
            reason_code:
              type: string
              description: >-
                Only on `verification_terminally_rejected`, and only when the
                rejection maps to a known class — most final rejections carry no
                code.
  securitySchemes:
    platformToken:
      type: http
      scheme: bearer
      description: >-
        A platform access token. Get one on the **Create an access token**
        endpoint by exchanging your `client_id` + `client_secret`, then send it
        as `Authorization: Bearer <token>`. Tokens live one hour.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.