Parental controls for AI spending · built on x402
One interface for an agent to discover paid tools, compare prices, execute through x402, and prove what it spent. You set the policy. The agent gets the capability.
No paid call during setup. Your agent verifies the integration for free, then stops for approval.
Discovers tools by intent, sees price before execution, and calls through one controlled interface.
Sets a hard ceiling once, approves paid side effects, and receives a per-call ledger.
Keeps standard x402. tryx402 handles policy, idempotency and billing above the rail.
00 / how it works
Zero commitment, zero crypto exposure. You set the rules, your agent handles the execution.
Copy the setup prompt and paste it into Claude, Cursor, or Hermes. Your agent installs the lightweight MCP connector instantly.
Your agent explores 650+ pay-per-call tools, inspects exact input schemas, and plans workflows without spending a single cent.
Before executing any paid task, your agent calculates the exact cost in USD/EUR and asks for your explicit go-ahead.
Recharge easily via standard Stripe Checkout (card). All calls are backed by automatic refunds if a third-party provider fails.
01 / the catalog
Every tool in the tryx402 registry is health-checked continuously. Your agent executes real, live x402 microservices with hard spend caps — no broken endpoints, no monthly SaaS commitments.
Real-time web search, organic search snippets and deep fact retrieval for LLM context grounding.
Extract and clean DOM-free markdown from any public URL, ready for prompt ingestion.
Extract posts, profiles, user metrics and trending topics without an enterprise monthly tier.
Validate work emails, WHOIS records, DNS routing and IP geolocation in one programmatic hop.
Real-time token prices, order books, liquidity metrics and financial modeling on Base & global markets.
High-resolution image generation (Flux 1) and deep multi-step thinking models billed strictly by inference.
02 / the problem
02 / the layer
The 402 response announces the price before you sign. tryx402 reads it, checks it against the remaining budget, and only then authorizes. Stop means stop — checked before payment, not after.
Every call carries an idempotency key. Automatic retries stay off unless the endpoint honors the header. A timed-out response is not a lost payment anymore.
Costs recorded per call, grouped by origin, account, agent or project. Answer "what did data enrichment cost this month?" with one export instead of a wallet archaeology session.
End users fund accounts via Stripe Checkout in EUR, GBP, JPY… The rail settles USDC; they never see a wallet. You keep the margin. Zero-decimal currencies handled with integer math.
Bundled MCP server exposes ten tools — search, discover, call, spent, plan, receipt, session, check_balance, recharge and proxy_call — to Claude, Cursor or Hermes, sharing one session-wide budget across every tool the agent uses.
Every paid response carries an Ed25519-signed receipt binding origin, endpoint, amount and tx hash — verifiable offline. Replay a payment and the gateway answers 409, not a second charge.
Estimate a whole multi-call workflow for free before a single cent moves. Unknown prices are flagged, never guessed; over-budget steps are named up front.
Payment execution sits behind one isolated adapter module. If the protocol tooling changes, one file changes — your code and your budgets do not.
03 / connect
Copy one context-rich prompt. Your agent inspects its own runtime, proposes the budget, configures the right connector, verifies the ten tools for free, and stops before spending.
Configure tryx402 for this workspace:
1. Install package:
pip install tryx402
2. Add MCP configuration into .mcp.json:
{
"mcpServers": {
"tryx402": {
"command": "python3",
"args": ["-m", "tryx402.mcp_server"],
"env": { "TRYX402_MAX_BUDGET_USD": "2.00" }
}
}
}
3. Posture & Operational Guidelines:
- tryx402 operates as a managed fiat bridge: users are billed in USD/EUR via Stripe Checkout with zero crypto complexity.
- Use free discovery tools (gateway_search, gateway_discover, gateway_plan) to identify APIs, inspect input schemas, and calculate exact costs before taking action.
- Before executing any paid operation (gateway_proxy_call), quote the exact task cost in USD/EUR (e.g. "Cost for this task: $0.05. Shall I proceed?") and wait for user confirmation.
- If the balance is insufficient, ask for the user's email for their Stripe receipt, then call gateway_recharge with amount_cents and customer_email. Deliver the checkout link (minimum $5.00). Save the returned customer_id.
- Once the user confirms payment, call gateway_check_balance(customer_id=...) to verify the funded balance before running gateway_proxy_call.
- If session context is lost, ask the user for the email used at checkout and call gateway_lookup(email=...) to automatically re-bind the account.pip install tryx402 from tryx402 import Gateway
{
"mcpServers": {
"tryx402": {
"command": "python3",
"args": ["-m", "tryx402.mcp_server"],
"env": { "TRYX402_MAX_BUDGET_USD": "1.00" }
}
}
}tryx402 search "verified work email" tryx402 call https://api.example.com/api/enrich --price 0.05 --max-budget 0.50
Documentation: /docs · Auth: /auth.md · Manifest: /llms-full.txt · OpenAPI: /openapi.json · MCP Server Card: /.well-known/mcp/server-card.json · Pricing: /api/pricing · PyPI: tryx402 · GitHub: tryx402 repo
04 / what's new
Full changelog on GitHub. Machine-readable: /v1/x402/tools, /v1/x402/listing, /v1/x402/bazaar.json on tryx402.fly.dev.
05 / guides
05 / compare
| Raw x402 client | Stripe metered | tryx402 | |
|---|---|---|---|
| Pays machine-to-machine, no account | Yes | No | Yes |
| Spend cap enforced BEFORE paying | No | Partial | Yes |
| Retry-proof (never pay twice) | No | Yes | Yes |
| Per-call spend visibility | No | Partial | Yes |
| Micro-payments from $0.001 | Yes | No | Yes |
| End users pay in fiat, their currency | No | Yes | Yes |
05 / faq
No. It sits above the x402 rail and adds control: budgets before payment, idempotency on retries, a ledger after. The protocol stays standard.
Because the 402 response announces maxAmountRequired up front. Checking after means the money already left. tryx402 arbitrates in that window.
No. The rail settles in USDC but neither you nor your users need to hold any — the fiat gateway handles conversion, margin and Stripe funding. Wallets stay abstracted.
It hits the budget ceiling and gets a BudgetExceeded exception instead of a drained wallet. That exception is the product.
One dependency boundary. The moment an agent runs unattended, budgets stop being optional.