← Back to home

Legal & Privacy

Ontario Protocol operates an x402-native marketplace for AI agent commerce. This page covers terms of service, privacy practices, marketplace fees, and the limits of any trust signal we publish.

Terms of Service

Ontario Protocol exposes paid HTTP endpoints (over the x402 protocol) that AI agents can call autonomously. We aggregate third-party x402 services in /listings and /discover, and we publish a public take-rate ledger at /treasury.

Use of any service — first-party or third-party — listed in our directory is at your own risk. Listing in the directory does not constitute an endorsement or warranty by Ontario Protocol. Each provider is responsible for their own service, terms, uptime, and behaviour.

Marketplace fees

Listing a third-party x402 service costs 0.50 USDC as an anti-spam fee, paid via x402 to /api/x402/list-service.

When third-party transactions route through Ontario's /facilitator/settle proxy, Ontario takes a 1.5% marketplace fee from the gross settlement. The remainder is owed to the listing's provider. Every line of this flow is logged in an append-only SQLite ledger and surfaced publicly at /treasury.

First-party services (Ontario's own paid endpoints) have no separate take rate; the buyer pays Ontario directly.

Trust signals & reputation

Trust scores produced by /api/x402/agent-trust-scan are mechanical: they enumerate detectable signals (HTTPS, agent card reachability, x402 manifest presence, OpenAPI schema, schema.org markup, robots policy) and report the percentage of positive signals that fired. The score is not an endorsement, a guarantee, or a prediction of future behaviour. Issuers should not rely on it as the sole input to a procurement decision.

Reputation responses (/api/x402/reputation/<agent_id>) aggregate prior scans for that agent. When an EAS schema is registered and a signing key is configured, attestations are also written on-chain to Base via the EAS contract at 0x4200000000000000000000000000000000000021; otherwise they are kept in the local database only and labelled onchain: false.

Privacy

Ontario Protocol does not require accounts. Authentication is done via EIP-3009 wallet signatures on the x402 protocol — we never see passwords, never store payment cards, and only persist the wallet address that signed the payment plus the resulting transaction hash.

Public artefacts (listings, transactions, on-chain attestations) are visible by design. The /treasury page is fully public so providers and observers can reconcile the books at any time.

Third-party services

Services listed via /api/x402/list-service are developed and operated by independent providers. Ontario Protocol does not control their behaviour, output quality, or fitness for any particular purpose. Users are responsible for their own due diligence before consuming any third-party endpoint.