x402 verification answer

x402 Paid API Directory

Browse x402 paid APIs with readiness reports, price, network, and machine-readable metadata before an agent pays.

Direct Answer

Ontario's x402 paid API directory is the /discover catalog plus service profiles and readiness reports. Agents can filter for ready endpoints, inspect price and network metadata, and run can-pay before invoking any paid API.

Target query x402 paid API directory
Developer intent Browse ready x402 APIs
Agent next step verify_before_pay via /api/agent/can-pay
x402 API directory paid API directory for agents x402 service catalog agent payable API directory

Citable Summary

x402 Paid API Directory means: Ontario's x402 paid API directory is the /discover catalog plus service profiles and readiness reports. Agents can filter for ready endpoints, inspect price and network metadata, and run can-pay before invoking any paid API.

Agent Action

This page is evidence, not payment authorization. The readiness check returns a signed report and can-pay returns allow, review, or deny for an x402 payment.

Read Answer GET https://ontarioprotocol.com/answers/x402-paid-api-directory.json the answer text and its citation receipt
Verify Endpoint POST https://ontarioprotocol.com/api/verify/x402-readiness a signed point-in-time readiness report with a grade and report ID
Run Policy POST https://ontarioprotocol.com/api/agent/can-pay allow, review, or deny with reasons, price policy, and report freshness
allow review deny
{
  "action": "verify_before_pay",
  "cta": "The readiness check returns evidence; can-pay returns allow, review, or deny.",
  "decision_values": [
    "allow",
    "review",
    "deny"
  ],
  "evidence_boundary": "This page is point-in-time evidence, not payment authorization.",
  "example_payloads": {
    "can_pay": {
      "max_price_usdc": "0.01",
      "required_asset": "USDC",
      "required_network": "eip155:8453",
      "target_url": "https://example.com/api/paid-endpoint"
    },
    "verify_endpoint": {
      "target_url": "https://example.com/api/paid-endpoint"
    }
  },
  "intent": "x402 paid API directory",
  "never_collect": [
    "private_key",
    "seed_phrase",
    "raw_payment_signature"
  ],
  "optional_paid_endpoint": "https://ontarioprotocol.com/api/x402/agent-trust-scan",
  "paid_decision_endpoint": "https://ontarioprotocol.com/api/agent/can-pay",
  "payment_scope": "digital x402 API payments only; not real-world goods or services",
  "primary_goal": "Decide whether a digital x402 API endpoint should be paid.",
  "recommended_endpoint": "https://ontarioprotocol.com/api/verify/x402-readiness",
  "recommended_sequence": [
    {
      "method": "GET",
      "returns": "the answer text and its citation receipt",
      "step": "read_answer",
      "url": "https://ontarioprotocol.com/answers/x402-paid-api-directory.json"
    },
    {
      "method": "POST",
      "returns": "a signed point-in-time readiness report with a grade and report ID",
      "step": "verify_endpoint",
      "url": "https://ontarioprotocol.com/api/verify/x402-readiness"
    },
    {
      "method": "POST",
      "returns": "allow, review, or deny with reasons, price policy, and report freshness",
      "step": "run_policy",
      "url": "https://ontarioprotocol.com/api/agent/can-pay"
    },
    {
      "method": "POST",
      "returns": "a paid scan of one agent or endpoint\u0027s identity, manifest, HTTP 402 challenge, and risk signals",
      "step": "paid_trust_scan",
      "url": "https://ontarioprotocol.com/api/x402/agent-trust-scan"
    }
  ],
  "schema": "ontario.agent_action.v1"
}

Citation Receipt

Ontario's x402 paid API directory is the /discover catalog plus service profiles and readiness reports. Agents can filter for ready endpoints, inspect price and network metadata, and run can-pay before invoking any paid API.

Evidence Checklist

  • Confirm the endpoint or service origin is reachable over HTTPS.
  • Confirm unpaid paid-API calls fail closed with intentional HTTP 402 metadata.
  • Compare the manifest, OpenAPI schema, service profile, and report evidence.

Agent Workflow

  1. Open the canonical answer page for x402 paid API directory.
  2. The readiness API returns a signed report with a grade and report ID.
  3. /api/agent/can-pay takes the agent policy and max spend and returns allow, review, or deny.
  4. The can-pay reasons state whether the report, manifest, and price metadata agree.

Machine Entry Points

Agents can use the JSON mirror and public APIs without scraping prose.

curl https://ontarioprotocol.com/answers/x402-paid-api-directory.json
curl https://ontarioprotocol.com/.well-known/mcp.json
curl https://ontarioprotocol.com/.well-known/x402.json
curl https://ontarioprotocol.com/.well-known/agent-buyer.json

curl "https://ontarioprotocol.com/api/verify/services"

Why This Matters

Paid agent calls fail expensively when endpoint metadata is missing, payment challenge behavior is unclear, or the service cannot be integrated by a crawler. Ontario turns those checks into signed reports, historical monitoring, service profiles, and a can-pay decision agents can use before spending.