Roundhouse

PayPerByte

A curated library of live data feeds and oracles for AI agents — pay per call in USDC over x402, settled on Base mainnet. First-party, verifiable, no token. Every paid response carries an EIP-712 X-BYTE-Attestation receipt the agent verifies before acting.

SearchLiveeip155:8453Exactvia cdp
https://x402.payperbyte.io/feeds/sanctions-screen
PayperbyteSanctions-screenOfacComplianceSigned-verdict
Calls · 30d
1↓ 59%
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 32 snapshots so far.
$9.01
Verified settled volume
283 settlements proven x402 by their on-chain EIP-3009 marker.
$0.100
Listed price
As published in the catalog. Always read the live 402 before paying.
1
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-08-21 03:55Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0xffFf4B8Da8C165B556326453446F6940C8AFE0DB

The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.

Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Provider

The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.

Accepts

The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.

0.1USDC≈ $0.1 USD
on Base · exact scheme

Pay 0.1 USDC on Base to 0xffFf…FE0DB. The signed payment is good for 5 minutes.

Paid to
0xffFf…FE0DB
USD Coin contract
0x8335…02913
Payment window
5 minutes
As published
100000 smallest units
The catalog’s raw entry
[
  {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": {
      "name": "USD Coin",
      "version": "2"
    },
    "payTo": "0xffFf4B8Da8C165B556326453446F6940C8AFE0DB",
    "amount": "100000",
    "scheme": "exact",
    "network": "eip155:8453",
    "maxTimeoutSeconds": 300
  }
]

Extensions

{
  "bazaar": {
    "info": {
      "input": {
        "body": {
          "name": "Lazarus Group"
        },
        "type": "http",
        "method": "POST",
        "bodyType": "json"
      },
      "output": {
        "type": "json",
        "example": {
          "_note": "Excerpt of a real answer (live service, 2026-07-01); hash/signature elided, signals/consolidated trimmed. Every answer pins the exact OFAC list version (published date + sha256 + entry count) it was judged against. Screening signal, not legal advice. The EIP-712 receipt — domain chainId 421614 = Arbitrum Sepolia, a frozen signing namespace, not a settlement rail — proves who signed these exact bytes (authenticity + tamper-evidence), not that the screening result is correct. Recompute keccak256(canonical answer bytes) and recover the signer before acting.",
          "answer": {
            "v": "sanctions-screen/v1",
            "query": {
              "name": "Lazarus Group",
              "chain": null,
              "address": null
            },
            "score": 0,
            "reasons": [
              "name exactly matches OFAC SDN primary name \"LAZARUS GROUP\": entry #27307 \"LAZARUS GROUP\" [DPRK3] — list published 2026-06-30"
            ],
            "verdict": "BLOCK",
            "list_state": {
              "sdn": {
                "stale": false,
                "source": "OFAC SDN (Specially Designated Nationals and Blocked Persons)",
                "entry_count": 19129,
                "content_sha256": "a04efa5d60104ebd35fc08b6891811120d151bf37801fbd3c01e64380198f099",
                "published_date": "2026-06-30"
              }
            },
            "methodology": "ss-v1"
          },
          "attestation": {
            "domain": {
              "name": "BYTE Library",
              "chainId": 421614,
              "version": "1",
              "verifyingContract": "0x44729bB148F46d8Db509E47b0453edc271e06e95"
            },
            "signer": "0x344ECaCDe6566294c31397445c98b62a3EEEA456",
            "signature": "0x…",
            "payloadHash": "0x…"
          }
        }
      }
    },
    "schema": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "input"
      ],
      "properties": {
        "input": {
          "type": "object",
          "required": [
            "type",
            "method",
            "bodyType",
            "body"
          ],
          "properties": {
            "body": {
              "type": "object",
              "anyOf": [
                {
                  "required": [
                    "address"
                  ]
                },
                {
                  "required": [
                    "name"
                  ]
                }
              ],
              "properties": {
                "name": {
                  "type": "string",
                  "maxLength": 256,
                  "minLength": 2,
                  "description": "Counterparty name (individual or entity). Screened exact + conservative fuzzy against primary and a.k.a. names in the SDN + Consolidated lists."
                },
                "chain": {
                  "type": "string",
                  "description": "Optional, informational only — the SDN annex pins addresses to currency symbols; chain never gates a hit."
                },
                "address": {
                  "type": "string",
                  "description": "Counterparty address: 0x+40-hex (EVM) or a digital-currency address. Checked against the OFAC SDN digital-currency annex."
                }
              },
              "description": "At least one of `address` or `name` is required."
            },
            "type": {
              "type": "string",
              "const": "http"
            },
            "method": {
              "enum": [
                "POST"
              ],
              "type": "string"
            },
            "bodyType": {
              "enum": [
                "json",
                "form-data",
                "text"
              ],
              "type": "string"
            }
          },
          "additionalProperties": false
        },
        "output": {
          "type": "object",
          "required": [
            "type"
          ],
          "properties": {
            "type": {
              "type": "string"
            },
            "example": {
              "type": "object"
            }
          }
        }
      }
    }
  },
  "payperbyte-service-metadata": {
    "tags": [
      "payperbyte",
      "sanctions-screen",
      "ofac",
      "compliance",
      "signed-verdict"
    ],
    "serviceName": "PayPerByte"
  }
}

Provenance

Seen in the source catalog
2026-08-21 03:55Z
Last indexed by Roundhouse
2026-09-20 03:50Z
Last enriched (probe, favicon, geo)
2026-09-14 04:15Z
x402 version
2
Max timeout
300s
Liveness probe
HTTP 405
Report

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/endpoints

This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 32 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.

Open skill.md
Show the prompt
Using Roundhouse, look up the x402 service PayPerByte and tell me whether it is
worth paying: what a call costs, whether the endpoint answered when last probed, and what
its payment record actually shows.

curl -s 'https://api.roundhouseai.io/v0/endpoints?q=PayPerByte'
curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>'

Then call it: read the price from the live 402 at https://x402.payperbyte.io/feeds/sanctions-screen, never from
a cached figure, and pay with an x402 client.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.