Market / Ontario Protocol
External service · publisher supplied metadata

Ontario Protocol

Source and listing identity

Source: x402 Bazaar

Listing ID: x402:535f9e26c1839666b59493f1d376329be0af8ae7228ee6ee9cf6d4a97403a1a9

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.

Which x402 API should my agent call? Live API finder for any task. Required: task. Returns up to 5 paid APIs that answered a fresh unpaid probe with a valid Base USDC 402, ranked by task fit, price and Bazaar-reported repeat buyers, each with live price, network and a ready-to-call request. Provider calls are paid separately. No live match, no charge. $0.005 USDC on Base. No account, no API key. Recommendations, not a safety guarantee. By Ontario Protocol.

APIx402Indexed

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-10-30 · 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://ontarioprotocol.com/api/x402/find-api

Read the current payment requirements with a compatible client before authorizing a call.

Documentation ↗Open provider website ↗

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 →