toll402

name	toll402
description	Find, compare, and safely integrate curated x402 resources through the TOLL·402 MCP server. Use when a developer needs an x402 API or MCP service, wants to compare price or verification evidence, needs quote-only integration code, or asks an AI coding agent to add an x402 service without making a payment.

TOLL·402 Integration

Workflow

1. Inspect the repository and identify the required capability, runtime, network constraints, and acceptable unit cost.
2. Call search_services. Prefer curation: curated and verification: direct-quote; relax one constraint at a time when needed.
3. Call get_resource for the strongest candidates. Inspect the exact method, URL, input, payment options, source provenance, and check dates.
4. Use compare_resources when two or more credible candidates remain. Compare cost per completed task, not only the displayed per-call number.
5. Call check_current_quote for the selected record. Treat it as the latest stored dated check, not a new probe.
6. Call get_connection_recipe for the repository language or active coding agent.
7. Implement the quote-only path with the repository's existing patterns and tests. Explain the separate step required to enable a wallet-backed paid request.

Trust Boundaries

• Never request, print, store, or transmit a private key or seed phrase.
• Never make a paid request unless the user explicitly authorizes that exact payment and the repository already has an approved signing path.
• Do not describe a live 402 quote as paid-call verification.
• Prefer exact resource records over provider-level claims.
• Keep the resource ID and last check date in the handoff.
• For state-changing routes, inspect provider-approved test input before any request.

Handoff

State the selected resource, why it won, its published price and network, the date and scope of its latest check, files changed, validation performed, and the remaining step before a paid production call.