PayPerByte · Feeds Address Reputation

import { wrapFetchWithPayment } from "@x402/fetch";
import { privateKeyToAccount } from "viem/accounts";

const account = privateKeyToAccount(process.env.PRIVATE_KEY);
const fetchWithPay = wrapFetchWithPayment(fetch, account);

const res = await fetchWithPay("https://x402.payperbyte.io/feeds/address-reputation", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "address": "0x1111111111111111111111111111111111111111",
    "amount": 50000,
    "chain": "base",
    "domain": "example.com"
  }),
});
const data = await res.json();

curl -X POST \
  "https://x402.payperbyte.io/feeds/address-reputation" \
  -H "Content-Type: application/json" \
  -d '{"address":"0x1111111111111111111111111111111111111111","amount":50000,"chain":"base","domain":"example.com"}' \
  -H "X-PAYMENT: <signed x402 payment>"

{
  "_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": {
    "methodology": "ar-v1",
    "query": {
      "address": "0x1111111111111111111111111111111111111111",
      "amount": 50000,
      "chain": "base",
      "domain": "example.com"
    },
    "reasons": [
      "illustrative — real answers cite the ar-v1 domain (RDAP/TLS/DNS/Wayback), on-chain, and blocklist signals judged"
    ],
    "score": 55,
    "v": "address-reputation/v1",
    "verdict": "WARN"
  },
  "attestation": {
    "domain": {
      "chainId": 421614,
      "name": "BYTE Library",
      "version": "1"
    },
    "payloadHash": "0x…",
    "signature": "0x…",
    "signer": "0x…"
  }
}