Seedance video
10 seconds · 720p
tryx402$2.40
vsfal.ai standard≈ $3.03
2,250+ APIs, zero subscriptions. Starting at $0.001 per call.
“Find 25 French fintech companies, their sales leaders and verified work emails.”
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.
01 / cost proof
tryx402 cost on the left. Competitor price on the right. Same mission.
10 seconds · 720p
200 professional addresses
1 audit · 10 SERP · 10 keyword-volume checks.
10 generations
Illustrative workloads, excluding tax. Prices vary by provider and parameters. ZeroBounce includes a free monthly quota; the SEO comparison is for a one-off diagnostic.
00 / developer workflow
No web3 wallet or crypto setup. Manage your budget from the web, and let your agents call pay-per-use APIs safely.
Click the orange button above and paste the prompt into Claude, Cursor, or Hermes. Your agent installs the connector and prepares access.
Sign in to the web console via Magic Link to view live balance, top up via Stripe, and inspect real-time debits.
Your agent discovers 2,250+ tools, requests quote approval for paid calls, and all expenditures appear live in your dashboard.
01 / the catalog
Every tool in the tryx402 registry is health-checked continuously. Your agent executes 2,250+ live x402 microservices with hard spend caps — web search, scraping, B2B intel, crypto, AI inference, no monthly 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 (or claude_desktop_config.json):
{
"mcpServers": {
"tryx402": {
"command": "python3",
"args": ["-m", "tryx402.mcp_server"],
"env": { "TRYX402_MAX_BUDGET_USD": "2.00" }
}
}
}
3. Posture & Operational Guidelines:
- tryx402 is a managed fiat bridge: you pay in USD/EUR via Stripe Checkout with zero crypto complexity.
- Use free discovery tools (gateway_search, gateway_discover, gateway_plan) to search tools and check exact costs before acting.
- Before any paid operation (gateway_proxy_call), display the exact task cost in USD/EUR and request user confirmation.
- If balance is insufficient, ask for the user's email or provide the checkout link (https://www.tryx402.app/dashboard).
- If session context is lost, ask for the email used at checkout and call gateway_lookup(email=...) to re-bind.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.
The gateway re-reads the 402 challenge on every call. A price increase either fits inside your remaining budget and goes through, or trips the cap and stops. Nothing is signed on stale pricing.
Yes. Budgets attach to sessions, not wallets. Run one agent at $0.50 for scraping and another at $5.00 for enrichment on the same account, each with its own ledger.
Yes. Operators fund accounts by card through Stripe Checkout in EUR, USD, GBP or JPY. The USDC settlement on Base happens downstream and no wallet handling reaches you or your users.
One dependency boundary. The moment an agent runs unattended, budgets stop being optional.