Try it as the agent and the person
Send a request the way an AI agent would, then approve or deny it, switch rules on and off, or pause every agent, and watch what the agent reads back. No sign-up: it all runs in this page.
1You are the agent
Pick a request or write your own. The code below is what your agent would run to ask for real.
curl -X POST https://api.variantgate.com/v1/requests \
-H 'authorization: Bearer gl_YOUR_KEY' \
-H 'content-type: application/json' \
-d '{
"action": "payment.refund",
"agent": "support-bot",
"summary": "Refund โฌ49.00 to ana@example.com for order 1182",
"amount": "49.00",
"currency": "EUR",
"wait_seconds": 30
}'import { ApprovalClient } from "@variantgate/agent";
const approvals = new ApprovalClient({
agent: "support-bot",
apiUrl: "https://api.variantgate.com",
key: process.env.VARIANTGATE_KEY ?? "",
});
// Runs the function only on allowed: true. Anything else throws.
await approvals.guard(
{
action: "payment.refund",
summary: "Refund โฌ49.00 to ana@example.com for order 1182",
amount: "49.00",
currency: "EUR",
},
() => doTheThing()
);from variantgate import require_approval
# VARIANTGATE_KEY comes from the environment, and VARIANTGATE_API_URL
# when you do not use the hosted service.
# The block runs only on allowed: true. Anything else raises NotApprovedError.
with require_approval(
"payment.refund",
"Refund โฌ49.00 to ana@example.com for order 1182",
agent="support-bot",
amount="49.00",
currency="EUR",
):
do_the_thing()What the agent reads back
Nothing sent yet. Send the request to see the answer.
2You are the person
Inbox
Requests your agent sends land here.
Show someone else this request, with the rules and pause as you set them:
What the playground shows
The agent asks, then waits
Before a risky step the agent makes one HTTP call, or calls the TypeScript or Python client or the MCP tool. It does nothing until the answer comes back.
Only allowed: true means go
Waiting, denied, expired and withdrawn all mean stop, and so does an approval while agents are paused. The clients fail closed: an error or a timeout means the action does not run.
Rules answer the routine ones
Small refunds and staging deploys go through on their own, in the name of the owner who wrote the rule. Anything above a limit, or without an amount to compare, goes to a person. How rules work.
What the real service adds
The playground keeps everything in this page and sends nothing. The service does the same job with real requests, and adds:
- A message where you already are: email, Slack, Microsoft Teams, Discord or a phone notification, with Approve and Deny in it (notifications).
- A time limit on every request, 15 minutes unless the agent asks for another. A request nobody answers expires and can no longer be approved.
- A sealed record of every decision and every change to keys, rules and people.
- Budgets per day, week or month, two-person approval, and approving a smaller amount than the agent asked for.
- The full answer, with fields the playground leaves out, as listed in requests.
Ask for real
Free for one person and 100 requests a month, with no card. Make an agent key and the code above asks for real. Standing rules come with Pro.