Skip to main content
Set how much each agent can spend, where it can pay, and which purchases it must ask you about. In the sidebar, under Workspace, click Agent cards. Creating one takes about 3 minutes.
The Agent cards page showing three agent card tiles: Default agent card and Shopping agent are Active, Travel agent is Paused. Each shows this week's spend against its weekly cap and when it was last used.The Agent cards page showing three agent card tiles: Default agent card and Shopping agent are Active, Travel agent is Paused. Each shows this week's spend against its weekly cap and when it was last used.

The Agent cards page with two active agent cards and one paused.

An agent card is a set of rules on one of your cards, its funding card (Underlying card). The rules are checked every time an agent tries to fill it.

​
Create an agent card

1

Click New agent card

On an empty page it reads Create agent card.
2

Enter a Name

Name it after the agent that will use it, for example “Grocery agent”.
3

Choose the Funding card

Pick the card this agent pays with, or click Add a new card.
4

Check the spending limits

They start at the defaults. Clear a field for no limit.
5

Click Create

The agent card’s page opens. Changes there save as you make them.
Your agent can now spend with this card, within the limits you set.

Creating an agent card and tuning its settings.

Give each agent its own agent card and API key, so you can stop one agent and leave the rest running.
Free allows 1 agent card, Plus 5, and Enterprise unlimited. Only agent cards linked to a funding card you still have count. See Billing.

​
The Default agent card

Your first card gets one named Default agent card, so that card is never usable without limits. It uses the defaults below. Rename it after its agent.
Every card you add after the first starts with No limits: an agent can fill it for any amount at any authorized site. On the Cards page, click Add limits on it straight away.

​
The agent card page

The Shopping agent card page, marked Active, with Pause and Manage API keys buttons, the Spending this period meters, the Configuration panel, and the Spending limits section.The Shopping agent card page, marked Active, with Pause and Manage API keys buttons, the Spending this period meters, the Configuration panel, and the Spending limits section.

An agent card's page.

Spending this period shows spend This week and This month against your caps. Configuration holds the Name and Underlying card. Spend is counted per funding card, so agent cards that share one show the same figure. Fills made while it had No limits are never counted, even after you attach an agent card. They appear only on Activity.

​
Spending limits

Spending limits section with the per-transaction cap and the daily, weekly and monthly limit fields.Spending limits section with the per-transaction cap and the daily, weekly and monthly limit fields.

The four spending limits on an agent card.

Windows roll: a weekly limit frees up as old spend passes 7 days, not on Monday. To stop spending, pause rather than setting 0.Alimitmustbemorethan0. A limit must be more than 0: a $0 or negative value is refused (agent_card_cap_not_enforceable), shown on the page as Unable to update agent card. There is no upper bound.
The daily, weekly and monthly limits apply on production deployments only. Other deployments enforce only the Per-transaction cap. See Limits.
Spending limits are in beta. A total Agent Vault cannot read is declined, but a total read wrongly could slip past, so keep an eye on Activity.

​
Spend counts when the card is filled

A purchase counts the moment the card number is typed, before any order exists.
If the order is never placed, the amount still counts until it ages out, so a few abandoned attempts can reach a limit with nothing bought. Agent Vault never reverses it. Check your card statement for real charges.

​
Merchant restrictions

The Merchant restrictions section with Mode set to Blocklist, a domain field with an Add button, and two blocked domains shown as removable chips.The Merchant restrictions section with Mode set to Blocklist, a domain field with an Add button, and two blocked domains shown as removable chips.

Merchant restrictions in Blocklist mode.

Mode sets where this agent card may pay. The default is Allow all. Pick the narrowest mode that still lets the agent do its job.
1

Choose a Mode

Pick Blocklist or Allowlist only.
2

Add a site

Type a domain such as example.com and click Add.
Click the cross on a chip to remove it. amazon.com covers smile.amazon.com, but not amazon.co.uk. Sites on an active allowlist skip the new-site approval for all your saved details. If you leave Enterprise, an agent card already in Allowlist only mode keeps that mode and keeps paying only at its listed sites. The list is shown but read-only. To change it, switch Mode to Allow all or Blocklist, or return to Enterprise. See Billing.

​
Require approval above an amount

Require confirmation above, under Behavior, makes any purchase at or above that amount wait for your Approve or Deny. Set it to the order size you would want to check yourself.
  • Blank (the default): never asks.
  • 0: asks for every purchase.
  • A negative value: saved but ignored, so it never asks.
Behavior section with the Auto-pause on limit exceeded switch on and Require confirmation above set to 50.Behavior section with the Auto-pause on limit exceeded switch on and Require confirmation above set to 50.

Require confirmation above, under Behavior.

Once set, you are also asked when the total cannot be read or confirmed. You have about 5 minutes to answer. See Purchase approvals. If the total is often unknown, add a page hint rather than raising the amount.

​
Auto-pause on limit exceeded

Auto-pause on limit exceeded stops the agent card when a purchase would break any limit. It is on by default. Keep it on, so you can look before the agent tries again. With it off, a smaller cart or a new window goes straight through.
Agent card page showing the Limit status, a Resume button and spend bars near the weekly cap.Agent card page showing the Limit status, a Resume button and spend bars near the weekly cap.

An agent card paused after a purchase broke a limit.

​
Pause and resume

If another active agent card shares the funding card, pausing this one does not stop the card: it stays usable under the other’s limits only. To stop it, pause every agent card on it.
Click Pause at the top of the agent card’s page to stop its card fills, and Resume to restart them. To stop every agent at once, see Overview.

​
What happens when…

A site is allowed if any active agent card on that card allows it. The limits that apply come from every agent card that allows the site and is Active or stopped at Limit. A Limit card’s caps keep applying, so a looser sibling cannot raise the limit after one denial.An agent card you paused yourself contributes no limits and no merchant permission. To keep a tight cap in force, lower the sibling’s limits too. If the only agent card allowing a site is paused, that site is blocked until you resume it.

​
Card tokens

Underlying card tokens shows the funding card’s mock tokens: Card number, CVV and the real Expiry. The security code (CVV) is never stored, so it is marked Entered live by you: you type the real code when an agent fills it. The tokens work only through Agent Vault, for an API key allowed to use the card.
The Underlying card tokens section showing the Card number and CVV mock tokens with copy buttons, the expiry, and a three-line fill snippet.The Underlying card tokens section showing the Card number and CVV mock tokens with copy buttons, the expiry, and a three-line fill snippet.

The Underlying card tokens section.

​
Notification webhook

On Plus and Enterprise, an agent card can send its events to your own system. None is set by default.
1

Enter the Endpoint URL

Type a public https:// address and click Save.
2

Copy the Signing secret

Use it to check each delivery is genuine.
3

Click Send test

The test appears under Recent deliveries, which lists the newest 10.
Deliveries include the merchant host and ids that tie a fill to its funding card and session, plus the amount and threshold on purchase approvals. They never include a card number, security code, password, 2FA secret, identity value or approval link. Payloads and verification are on Webhooks.

​
Delete an agent card

Deleting an agent card is permanent. It does not stop an agent: an open session keeps running. If it is the funding card’s only agent card, that card is left with No limits, even for a checkout already running. To stop the card, pause instead, revoke the agent’s key or delete the card.
1

Click Delete agent card

It is under Danger zone.
2

Click Delete

The agent card and its rules are removed.
If you delete the card instead, the agent card shows No funding card until you pick another Underlying card. Until then it controls nothing and does not use any of your plan’s agent card allowance.

​
Stop an agent using a card

None of these takes back a value already typed into a page.

​
For developers

Counters count card fills, not settled charges. Webhook events and the X-AgentPay-Signature header are on Webhooks. Next: Approvals to make sure approval requests reach you in time.