Ontario Protocol
x402 service listings / agt_ef9ee1ff4ac5
Canonical x402 Bazaar launch passport

Zambo Trust Layer

Trust Layer for AI work. Give your AI hands. Free MCP https://zambo.dev/api/mcp. Day Pass $1.49 USDC on Base for 24h (NOT per-call/per-task). Settle https://zambo.dev/api/x402/day-pass payTo 0xb753be5Eac5B29c711051DfF91279834e9C9b9AC. Docs https://zambo.dev/for-agents

needs work
Endpoint price0 USDC
MethodGET
Networkbase
Readiness score52

Submitted endpoint

Provider-supplied service metadata.

Endpoint
https://zambo.dev/.well-known/agent-card.json
Owner site
https://zambo.dev
Category
agent
Tags
mcp, x402, trust-layer, day-pass, ai
Published
2026-09-19T08:20:18.486230Z

Readiness evidence

Point-in-time observations, not a safety promise.

Status
needs work
Strict discovery
Not currently eligible
Report
vrf_cad8a3d9dda8efc5
Observed at
2026-10-17T11:00:15.150455+00:00
Evidence freshness
stale
Evidence age
411.25 hours
Fresh until
2026-10-24T11:00:15.150455Z
Refresh recommended
Yes. Evidence is older than Ontario's 168-hour strict-payment freshness window.
Paid evidence refreshes
4
Last profile refresh
2026-10-17T11:00:16.995599Z
Automatic refresh
The last automatic refresh on 2026-10-17 attached a new readiness report. Included maintenance ended on 2026-10-19.
last_auto_refresh_status: updated
Included until
2026-10-19
Run a fresh verification Review the 0.10 USDC profile refresh Browse ready services

Readiness findings

Warnings and fixes from the latest readiness report.

  1. Fix the x402 manifest shape

    The manifest should be JSON and include a services array with endpoint, method, price, network, and asset metadata. Reference

  2. Expose a real HTTP 402 payment challenge

    A paid endpoint should reply with HTTP 402 and a payment requirements header when called without payment. Reference

  3. Add listing metadata for Bazaar-style catalogs

    Name, description, category, tags, owner URL, and contact fields make services usable in agent marketplaces. Reference

  4. Publish facilitator and settlement metadata

    Expose facilitator details plus asset, payTo, scheme, timeout, and resource fields so clients can verify and settle payments deterministically. Reference

  5. Refresh the x402 manifest timestamp

    A stale or missing manifest timestamp makes agents doubt whether prices, networks, and facilitator metadata still describe the live endpoint. Reference

Open the full readiness report

Machine-readable profile

Stable surfaces for catalogs, agents, and evidence links.

JSONhttps://ontarioprotocol.com/listings/agt_ef9ee1ff4ac5.json Signed with Ontario's Ed25519 report key (public key).
Badgehttps://ontarioprotocol.com/listings/agt_ef9ee1ff4ac5/badge.svg
Cataloghttps://ontarioprotocol.com/discover?format=json
Trust policyhttps://ontarioprotocol.com/.well-known/x402-trust.json

Distribution bundle

Copy-ready public metadata for operator review.

Buyer task
Not supplied
Description draft
Zambo Trust Layer. 0 USDC on Base.
README badge
[![Ontario x402 launch evidence](https://ontarioprotocol.com/listings/agt_ef9ee1ff4ac5/badge.svg)](https://ontarioprotocol.com/listings/agt_ef9ee1ff4ac5)
This bundle is generated from provider-supplied public metadata and point-in-time observations. The provider must verify every field before publishing it to an external registry. It does not create Coinbase Bazaar placement or ranking.

Observed distribution

A privacy-safe request receipt for this paid publication.

Observed requests
10 in the current 30-day window
Human-classified
3
Agent or crawler
7
Developer tool
0
HTML profile
6
Machine-readable JSON
3
Badge
1
Measurement began
2026-07-31T03:40:00Z
Counts are observed HTTP requests, not unique people, verified agents, buyers, leads, purchases, ranking, or guaranteed traffic. Automated and repeat requests can increase these totals. Ontario stores only listing id, publication surface, broad actor class, status, and time. It does not store IP addresses, raw user agents, wallet identifiers, contacts, payment headers, or request bodies for this receipt.

Provider actions

Keep evidence useful, then add clearly labeled reach if needed.

0.10 USDC
Refresh this profile's readiness evidence

Refresh is recommended: Evidence is older than Ontario's 168-hour strict-payment freshness window. Payment cannot improve the grade or edit provider metadata.

Agent handoff: Validate listing_id agt_ef9ee1ff4ac5 with POST https://ontarioprotocol.com/api/x402/refresh-listing/validate. If validation returns ok and local policy allows 0.10 USDC on Base, call POST https://ontarioprotocol.com/api/x402/refresh-listing with {"listing_id":"agt_ef9ee1ff4ac5"}. Probe the 402 challenge before signing locally; never send wallet keys to Ontario.

Open x402 refresh steps
5.00 USDC / 30 days
Keep this profile maintained

Readiness evidence kept fresh automatically after the included window, five Bazaar buyer searches re-run weekly with the history shown above, and an optional webhook alert when the grade changes or the endpoint stops answering. Currently maintained until 2026-10-19.

Agent handoff: POST https://ontarioprotocol.com/api/x402/renew-listing {"listing_id": "agt_ef9ee1ff4ac5"} (validate free first at https://ontarioprotocol.com/api/x402/renew-listing/validate)

Review renewal API

Payment buys a fresh observation, not a better score, metadata edit, ranking, traffic, or strict-discovery eligibility.

Trust boundary

What this publication does and does not prove.

This profile proves that Ontario processed a paid provider submission and reports point-in-time observable readiness, Bazaar retrieval, and any attached MCP Registry or remote-contract evidence. Ontario is not Coinbase and the launch passport is not an official certification. It does not guarantee endpoint safety, service quality, traffic, ranking, purchases, settlement success, or future behavior.