> ## 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

# Clear a user's spend limits

> Remove your limits on what can leave a user's balance.

Removes your limits on one user. Limits another company set on the same user
stay in place.

Your limits stop at once. The wallet provider can take a little longer to let
go of the per-transaction limit: until it has, `wallet_provider_policy.status`
reads `pending` or `failed`, and no single transfer is larger than the wallet
provider still allows. Agentcard retries on its own every few minutes, and
sending the same request again retries right away.

When the user disconnects from your company, your limits on them are removed
the same way.

You can still clear a limit you left on a user who disconnected. The answer then
carries `spent` as `null`, since what that user spends is no longer yours to
read, and a read of their limits answers `404`.


## OpenAPI

````yaml openapi.json DELETE /api/v2/wallet/limits
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/wallet/limits:
    delete:
      tags:
        - User balance
      summary: Clear a user's spend limits
      description: >-
        Removes your limits on one user. They stop at once;
        `wallet_provider_policy.status` reads `pending` or `failed` until the
        wallet provider has let go of the per-transaction limit, and sending the
        same request again retries it. Another company's limits on the same user
        stay. Your limits are also removed when the user disconnects from your
        company.
      operationId: walletLimitsClear
      parameters:
        - name: user_id
          in: query
          required: true
          description: The connected user.
          schema:
            type: string
      responses:
        '200':
          description: The user's spend limits, with yours removed.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WalletSpendLimit'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          description: >-
            `not_found`: you set no limits on this user. `connection_not_found`:
            no connection for that user in this mode.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - platformToken: []
components:
  schemas:
    WalletSpendLimit:
      type: object
      required:
        - object
        - user_id
        - stricter_limit_applies
        - spent
        - wallet_provider_policy
      properties:
        object:
          type: string
          description: Always `wallet_spend_limit`.
          enum:
            - wallet_spend_limit
        user_id:
          type: string
          description: The connected user.
        per_transaction_cents:
          type:
            - integer
            - 'null'
          description: Your most for one movement, in cents. `null` is no limit.
        daily_cents:
          type:
            - integer
            - 'null'
          description: Your most for any 24 hours, in cents.
        monthly_cents:
          type:
            - integer
            - 'null'
          description: Your most for any 30 days, in cents.
        stricter_limit_applies:
          type: boolean
          description: >-
            `true` when another company set a smaller figure for one of the
            three limits, or a limit you left unset. The user's balance obeys
            the smaller figure of each limit across every company; that
            company's figures are not shown.
        spent:
          type:
            - object
            - 'null'
          description: >-
            What left the user's balance onto their cards, in cents, across
            every company. A refunded purchase stops counting. `null` when you
            clear a limit on a user who disconnected from your company.
          properties:
            last_24_hours_cents:
              type: integer
            last_30_days_cents:
              type: integer
        wallet_provider_policy:
          type: object
          description: >-
            Whether the wallet provider that holds the user's balance refuses a
            transfer above the per-transaction limit that holds for the user.
          properties:
            status:
              type: string
              enum:
                - synced
                - pending
                - failed
                - not_needed
              description: >-
                `synced`: the wallet provider refuses a transfer above the
                per-transaction limit. `pending` or `failed`: a change has not
                reached the wallet provider yet. Agentcard holds your limits
                meanwhile, never moves more in one transfer than the wallet
                provider still allows, and retries every few minutes.
                `not_needed`: no per-transaction limit is set.
        updated_at:
          type:
            - string
            - 'null'
          format: date-time
          description: When you last set your limits.
    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.
  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'
  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.