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

# remove_address

> Remove the address saved under a name.

Connect to `https://mcp.opencommerce.sh/mcp` with your Commerce SDK credentials as `Authorization: Bearer <YOUR_CLIENT_ID>:<YOUR_CLIENT_SECRET>`. See [Connect your agent](https://docs.agentcard.com/commerce-mcp/implement.md#connect-a-client).

> [!NOTE]
>
> `remove_address` isn't available on the server yet. Until it is, a call answers `saved_addresses_unavailable`.

Behavior: Changes state. After a timeout, read `list_addresses` before you try again.

## What it does

Removes the address saved under a name, only after the shopper asked to.

## Inputs

| Field | Type | Description |
| - | - | - |
| `shopper_id` *(required)* | string | Your own stable id for the shopper. The same value on every call for the same person. |
| `label` *(required)* | string | The name the shopper gave the address, such as `Dad` or `Office`. Any spelling of a saved name matches it. 1 to 100 characters. |

## Returns

| Field | Type | Description |
| - | - | - |
| `removed` | boolean | `true`. |
| `label` | string | The name that was removed. |

## Example call

```json theme={null}
{
  "tool": "remove_address",
  "arguments": {
    "shopper_id": "user_8f3a21",
    "label": "Dad"
  }
}
```

## Notes

* `shopper_address_not_found` means nothing is saved under that name. [`list_addresses`](https://docs.agentcard.com/commerce-mcp/tools/list_addresses) shows what is.
* `saved_addresses_unavailable` means saved addresses aren't available yet.


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