Built for AI Agent purchases

SpendPermit

One human approval. One safe maximum. No reusable company card.

The Agent prepares the purchase; the human approves it through hosted payment. SpendPermit verifies payment before issuing a precisely limited card for up to 24 hours.

Set a maximum Download Skill Download CLI

Why it exists

AI Agents can research and prepare a purchase, but a reusable payment card grants far more authority than one task needs. Exact totals are also hard to predict when tax, shipping, conversion, or final capture can change. SpendPermit turns the requested amount into a hard maximum, not an exact-price guess.

Set maximumReview policyHuman paysSpendPermit verifiesClaimUse by policy

A $100 maximum does not have to become a $100 spend

Suppose an authorized business purchase is expected to cost about $70, but final tax is unknown. The user chooses a $100 maximum and reviews a $100 card budget, $5 processing charge, and $105 total due before approving payment. The merchant settles $70.

Card budget
$100
Net settled spend
$70
Unused principal
$30
Reviewed refund estimate
$28

At the original 24-hour review point, SpendPermit verifies that the card is closed, no authorization is pending, and evidence is complete. An approved refund normally deducts the $2 issuance cost. The original $5 processing charge is not refunded. Eligibility and amount are reviewed, not immediate or unconditional.

Choose a product payment channel

Alipay

Hosted Alipay checkout

Choose --channel alipay. The human opens SpendPermit's returned hosted action and pays personally.

International card

Hosted international-card checkout

Choose --channel card. The human completes SpendPermit's returned hosted card checkout.

In both cases, the CLI and Skill call SpendPermit only. They contain no payment, card-platform, banking, webhook, cloud, or internal credentials.

Know the boundary before paying

Card budget
$25 to $100, subject to the customer's Access Key.
Total due
Review the exact server quote. The current example processing charge is 5%.
Purchase window
Single-use by default; an enabled session shares one budget. Both end within 24 hours.
Not a wallet
No general stored balance or post-issue reload.
Single-use declines count
A declined first authorization still closes a single-use card.
Unused principal review
After the original 24-hour point; processing charge is not refunded and a standard $2 issuance cost normally applies.

Controlled business use only. Do not use this for personal spending, subscriptions, hotels, rentals, deposits, split shipments, merchant retries, or multiple purchases.

The Agent's job is intentionally small

  1. Configure the customer's private, revocable SpendPermit Access Key.
  2. Confirm authorized business use, quote first, and explain the policy.
  3. Return the hosted payment link, order ID, and status URL.
  4. Let the user pay. Check only SpendPermit order status.
  5. At CARD_READY, explicitly claim only after user consent.

The Access Key identifies the customer; verified human payment authorizes the purchase. The Agent never receives payment credentials and should return full card JSON only after explicit consent in a trusted environment.

Start with the right document

Use the Skill for an AI Agent, the CLI for terminal automation, and the complete guide for product rules, recovery, cancellation, states, and refunds.

Real scenarios English guide llms.txt