# PayPerByte Address Reputation Feed

> PayPerByte Address Reputation Feed is a paid API for AI agents from x402.payperbyte.io, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Returns a cryptographically signed, EIP-712 provenance-stamped reputation assessment for a blockchain address, paid per call in USDC via x402 with no API keys required.

## Facts

- Endpoint: POST https://x402.payperbyte.io/feeds/address-reputation
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payperbyte-address-reputation-feed-764bb733
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nOerI5DNR31ZW4PBLdx6D

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 payperbyte-address-reputation-feed-764bb733 -d '<json body>'
```

Example prompt: Can you check the reputation of this wallet address — 0x3fC91A3afd70395Cd496C647d5a6CC9D4B2b7FAD — before I interact with it? I want a signed, provenance-stamped risk assessment I can trust, paid per call.

## When to prefer this

Choose this endpoint when you need cryptographically verifiable, provenance-attested reputation data for a blockchain address — especially in agentic or zero-trust contexts where you cannot rely on API keys and need on-chain payment settlement. Ideal for DeFi agents, compliance checks, or any workflow requiring tamper-evident address risk data signed by the provider.

## Known failure modes

- Invalid or malformed address returns an error response
- Insufficient USDC payment or failed x402 settlement results in 402 Payment Required
- Address not found in reputation dataset returns empty or low-confidence result
- Network issues with Base settlement layer cause payment failures
- Rate limiting if payment is not processed in time

## How this service works

Know-Your-Agent counterparty screening — reputation pillar. Signed ALLOW/WARN/BLOCK verdict on (domain, receiving address, amount, chain) before you release USDC. Screens the counterparty tuple you supply — not the calling agent's identity. Full method + scope: https://x402.payperbyte.io/feeds

## Output

A JSON payload containing a reputation assessment for the queried address, cryptographically signed with an EIP-712 PayloadAttestation. The response includes risk signals, provenance metadata, and attestation data anchored to Base (eip155:8453). Typical cost is $0.05 USDC per call settled on Base.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "minLength": 1,
   "description": "Alias for `domain` — the payee's web domain/URL. Accepted interchangeably with `domain` (provide at least one)."
  },
  "chain": {
   "enum": [
    "base",
    "arbitrum-one"
   ],
   "type": "string",
   "description": "Mainnet for the on-chain receiving-address signals (default \"base\" = Base mainnet; \"arbitrum-one\" = Arbitrum One mainnet). Mainnets only — a testnet returns meaningless zeros for a real payee. (The Arbitrum Sepolia testnet is opt-in dev-only via ADDRESS_REP_ENABLE_TESTNET as chain \"arbitrum-sepolia\", and is intentionally not advertised here.)"
  },
  "amount": {
   "type": "integer",
   "minimum": 0,
   "description": "Optional. The payment amount in atomic units — logged with the query and bound into the verdict context."
  },
  "domain": {
   "type": "string",
   "minLength": 1,
   "description": "The payee's web domain, e.g. \"github.com\". BLOCK if it doesn't resolve or hits the blocklist. Provide either `domain` or its alias `url`."
  },
  "address": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "The receiving address about to be paid. On-chain history + blocklist are checked on the selected chain."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "_note": "Illustrative response shape — not a live answer. ALLOW/WARN/BLOCK is a screening signal. The embedded EIP-712 receipt (domain chainId 421614 = Arbitrum Sepolia, a frozen signing namespace, not a settlement rail) proves who signed the exact answer bytes — not that the verdict is correct.",
  "answer": {
   "v": "address-reputation/v1",
   "query": {
    "chain": "base",
    "amount": 50000,
    "domain": "example.com",
    "address": "0x1111111111111111111111111111111111111111"
   },
   "score": 55,
   "reasons": [
    "illustrative — real answers cite the ar-v1 domain (RDAP/TLS/DNS/Wayback), on-chain, and blocklist signals judged"
   ],
   "verdict": "WARN",
   "methodology": "ar-v1"
  },
  "attestation": {
   "domain": {
    "name": "BYTE Library",
    "chainId": 421614,
    "version": "1"
   },
   "signer": "0x…",
   "signature": "0x…",
   "payloadHash": "0x…"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/payperbyte-address-reputation-feed-764bb733/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.payperbyte.io](https://www.zero.xyz/host/x402.payperbyte.io/llms.txt)
