# Ontario Protocol x402 Demand Authenticity Report

> Ontario Protocol x402 Demand Authenticity Report is a paid API for AI agents from ontarioprotocol.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Analyzes blockchain transaction hashes and addresses to verify the authenticity and independence of x402 payment demand events before an agent pays

## Facts

- Endpoint: POST https://ontarioprotocol.com/api/x402/demand-authenticity-report
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ontario-protocol-x402-demand-authenticity-report-93c8615a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vZzfo2NwRFWed3fTkCEGW

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability ontario-protocol-x402-demand-authenticity-report-93c8615a -d '<json body>'
```

Example prompt: Before my agent pays this x402 endpoint, run a demand authenticity report on these transaction hashes — 0x3a1f...b2c4 and 0x9e7d...0a11 — to confirm they represent real independent customer payments to recipient 0xAbCd...1234, and tell me how many proven independent customers show up.

## When to prefer this

Use this endpoint when an AI agent needs to verify the authenticity of x402 payment demand events before authorizing payments to an endpoint provider — especially when assessing whether a provider's claimed customer base is real and independent. Prefer this over general blockchain explorers or manual tx lookups when you need a structured, machine-readable authenticity verdict specifically designed for the x402 HTTP 402 payment protocol context.

## Known failure modes

- Invalid tx hash format (must be 0x-prefixed 64-hex-char string) returns validation error
- Invalid address format (must be 0x-prefixed 40-hex-char string) returns validation error
- Empty or missing tx_hashes array returns schema error
- More than 20 tx_hashes or 50 related_addresses exceeds limits and returns error
- Transaction not found on-chain may result in zero proven customers with no error
- Network or RPC timeout may cause delayed or failed analysis

## How this service works

Find the first reason agents are not buying your x402 API. Test HTTP 402 readiness, Coinbase Bazaar retrieval, buyer-task fit, and agent payment policy free.

## Output

Returns a structured authenticity report (schema: ontario.x402_demand_authenticity.v1) containing the number of transactions analyzed and the count of proven independent customers, giving agents a verifiable signal of whether x402 payment demand events are genuine before committing funds.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tx_hashes": {
   "type": "array",
   "items": {
    "type": "string",
    "pattern": "^0x[0-9a-fA-F]{64}$"
   },
   "maxItems": 20,
   "minItems": 1
  },
  "related_addresses": {
   "type": "array",
   "items": {
    "type": "string",
    "pattern": "^0x[0-9a-fA-F]{40}$"
   },
   "maxItems": 50
  },
  "expected_recipient": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "example": {
  "schema": "ontario.x402_demand_authenticity.v1",
  "summary": {
   "transactions_analyzed": 1,
   "proven_independent_customers": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ontario-protocol-x402-demand-authenticity-report-93c8615a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ontarioprotocol.com](https://www.zero.xyz/host/ontarioprotocol.com/llms.txt)