Let your agent buy. If it goes wrong, we fight to get it back.

How it works

1. Step 1

   Set your limits

   Pick a hold period (10 minutes to 24 hours - 30 minutes by default), a per-transaction cap (default $100.00) and standing rules that name the exact merchants, categories, amounts and quantities your agent may buy without asking. Nothing outside those rules pays without your explicit approval.

2. Step 2

   Connect your agent

   Create a bearer key and register Buygent's MCP server, or install the CLI. Your agent gets exactly six tools: declare a cart, check its status, pay now, cancel, list activity, report an issue.

3. Step 3

   Approve, then your agent pays

   A declaration that matches one of your standing rules is ready immediately; anything else waits for your explicit approval - a timer never approves for you. When a purchase is ready, your agent pays at the merchant with the test card you stored in it. Buygent's locked authorizer approves the network authorization only if it exactly matches the declared merchant and total, and records the evidence either way.

{
  "mcpServers": {
    "buygent": {
      "type": "http",
      "url": "https://buygent.io/api/mcp",
      "headers": { "Authorization": "Bearer bg_test_<your-key>" }
    }
  }
}

What you control

• Spending limits

  A per-transaction cap you set, with a $100.00 hard ceiling, plus standing rules with their own maximums and quantity limits. Purchases above a rule wait for your approval; purchases above the transaction cap are rejected outright.

• Standing rules and explicit approval

  You decide which merchants, categories and amounts your agent may pay immediately. Every other purchase waits for your explicit approval - a hold, a timer or the agent itself never grants it.

• Exact merchant and amount matching

  A network authorization that differs from the declaration is flagged with the mismatch evidence, and Buygent starts the Fix flow to seek cancellation or refund. Processor data cannot prove cart contents at arbitrary merchants, so Buygent never claims item-level verification it cannot do.

• Evidence for every purchase

  Every intent, approval, authorization and outcome is logged with expected versus actual. Issues are reported with that evidence attached.

• One card, handed over by you

  You reveal the persistent test card through Stripe's hosted display and store it in your own agent. Buygent's servers never receive the number - they keep only brand and last four digits. The card is open by default within your prepaid balance and cap; Strict mode makes declarations an authorization gate.

• Email you can act on

  Hold, ready and declined notices carry safe links, and blocked or completed payments get their own notice with what happened. Opening a link never approves or cancels anything by itself.

Frequently asked questions