# x402 Demand Provenance Check

> x402 Demand Provenance Check is a paid API for AI agents from hermesplant.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Analyzes payment demand signals for x402-gated endpoints to assess credibility, detect owner-funded or artificial usage patterns, and return a confidence-scored provenance report.

## Facts

- Endpoint: GET https://hermesplant.com/api/agent-services/x402-provenance/check
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-demand-provenance-check-69ac1502
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ANdsIvJNlF8zxaQQvBYQR

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 x402-demand-provenance-check-69ac1502
```

Example prompt: Before my agent starts paying for calls to that x402 endpoint, run a demand provenance check on it — I want to know if the payment history looks credible or if it's mostly owner-funded, and give me the confidence score and top payer share.

## When to prefer this

Use this endpoint when an AI agent needs to gate consequential spend decisions on x402-priced APIs by first validating whether observed payment demand is organic and credible, rather than artificially inflated by the service owner. Prefer this over generic reputation checks when the specific concern is x402 micropayment provenance and wash-funding detection.

## Known failure modes

- Caller-supplied payment records cannot be independently verified onchain, reducing confidence
- Insufficient payment history may yield low confidence or inconclusive signal
- Missing or malformed scope metadata may cause analysis to fail
- Payment records with fewer than a minimum threshold of payers may return limited metrics
- Service unavailable errors if the hermesplant.com endpoint is down

## How this service works

Deterministic provenance analysis for caller-supplied x402 payment records. Excludes duplicate transaction hashes, separates declared owner wallets from candidate external payers, measures concentration and evidence coverage, and states limitations explicitly. It does not fetch the chain or claim wallet independence.

## Output

Returns a JSON object with: a provenance signal label (e.g. 'credible_candidate_pattern'), overall status ('analyzed'), confidence level ('moderate', 'high', etc.), metrics including topPayerShare, analyzedPayments, ownerFundedCalls, and uniqueCandidateExternalPayers, the service name, and a limitations array noting whether records were independently verified onchain or caller-supplied.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "payTo": {
   "type": "string",
   "description": "Optional expected Base/EVM recipient address."
  },
  "payments": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "payer"
    ],
    "properties": {
     "payTo": {
      "type": "string"
     },
     "payer": {
      "type": "string"
     },
     "txHash": {
      "type": "string"
     },
     "occurredAt": {
      "type": "string",
      "format": "date-time"
     },
     "amountUnits": {
      "type": "string"
     }
    }
   },
   "maxItems": 500,
   "minItems": 1
  },
  "resourceUrl": {
   "type": "string",
   "format": "uri"
  },
  "ownerWallets": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "maxItems": 50,
   "description": "Known operator wallets to exclude from external-demand candidates."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "scope": {
   "recordSource": "caller_supplied"
  },
  "signal": "credible_candidate_pattern",
  "status": "analyzed",
  "metrics": {
   "topPayerShare": 0.5,
   "analyzedPayments": 2,
   "ownerFundedCalls": 0,
   "uniqueCandidateExternalPayers": 2
  },
  "service": "x402-demand-provenance",
  "confidence": "moderate",
  "limitations": [
   "Caller-supplied records are not independently verified onchain."
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-demand-provenance-check-69ac1502/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from hermesplant.com](https://www.zero.xyz/host/hermesplant.com/llms.txt)