Integrate payments and related Stripe operations.
US cards:2.9% + USD 0.30/transactionUsage-based
Market / json-repair-api-9ybv.onrender.com · /trust/x402/clearance
External service · publisher supplied metadata
json-repair-api-9ybv.onrender.com · /trust/x402/clearance
Source and listing identity
Source: x402 Bazaar
Listing ID: x402:734e01de282807a38f52e6db08c66a412372103a961199608a9dcbb7a20cb9e1
Topic categories are inferred from listing text. Prices are source declarations; provider terms take precedence.
A registry entry or matching company name does not establish product authorship. Compare record IDs before treating similar titles as one product.
Decide whether an autonomous agent both can and should execute an exact x402 payment. Verifies predelegated spending authority, challenge/request integrity, and public merchant transaction-risk signals, then returns an evidence-based APPROVED, REVIEW or DENIED clearance plus a signed clearance token. APPROVED means the agent may proceed autonomously; REVIEW means do not auto-pay until higher-level review; DENIED means do not pay.
Listing completeness · 80/100
Presence of published information only. Not a security, reliability or performance score. Same rules for Datoka and external listings.
- Name and traceable source
- 10/10 · Present
- Meaningful description
- 10/10 · Present
- Connection or installation reference
- 20/20 · Present
- Dedicated documentation or source repository
- 0/15 · Missing or insufficient
- Explicit free access or numeric tariff
- 20/20 · Present
- Declared integration protocol
- 10/10 · Present
- Source updated within 90 days
- 10/10 · Present
- Declared capability names
- 0/5 · Missing or insufficient
Evaluated 2026-11-05 · Method listing-completeness-1. Scoring rules
Connect & use
Connect through the publisher’s supported interface. Any credentials or payments are handled by the provider.
x402 resource
https://json-repair-api-9ybv.onrender.com/trust/x402/clearanceRead the current payment requirements with a compatible client before authorizing a call.
Categories and declared capabilities
Topic categories are derived from publisher text for discovery, not independently verified capabilities.
The registry does not provide a verified tools list. See the observations, when available, for any tools/list check; a published tools list does not establish that execution succeeds.
Evidence, with its limits.
This listing is indexed. Any domain claim or endpoint observation appears separately with its date and limited scope. No payment execution, factual accuracy or safety certification is inferred.
The listing completeness score measures published information only. No safety or performance score has been assigned. A signature, source listing or successful HTTP response does not certify factual accuracy or safety.
How verification states work →Related tools
Similar tasks and categories; compatibility has not been tested.