# BYTE Library x402 Gateway – USC Statute Feed

> BYTE Library x402 Gateway – USC Statute Feed is a paid API for AI agents from x402.payperbyte.io, paid per call via x402, $0.012208/call, status down (last checked 2026-09-15).

Returns a cryptographically signed, EIP-712 provenance-stamped feed of U.S. Code (USC) statute data, paid per call in USDC via x402 on Base with no API key required.

## Facts

- Endpoint: GET https://x402.payperbyte.io/feeds/usc-statute
- Price: $0.012208/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/byte-library-x402-gateway-usc-statute-feed-240c82ef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uG0T2_Jy4G2RhMPHbJHSI

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 byte-library-x402-gateway-usc-statute-feed-240c82ef
```

Example prompt: Fetch me the latest cryptographically signed USC statute feed from BYTE Library — I need the provenance-attested US Code data and I'll pay per call in USDC, no API key needed.

## When to prefer this

Choose this endpoint when you need verifiable, cryptographically signed U.S. federal statute (USC) data for an AI agent and require provenance attestation (EIP-712) rather than trusting unsigned third-party feeds. Ideal for legal-tech agents, compliance workflows, or any system where tamper-evidence and auditability of law data matters. Prefer over traditional API key-based legal data providers when operating in a wallet-native, pay-per-call architecture on Base.

## Known failure modes

- Payment not included or insufficient USDC — 402 Payment Required response
- Malformed x402 payment header — payment rejected
- Network or Base settlement failure — transaction not confirmed
- Feed temporarily unavailable — service-side error
- Invalid GET parameters — 400 Bad Request

## How this service works

Verified, provenance-first data feeds for AI agents. Every payload is cryptographically signed and EIP-712 PayloadAttestation provenance-stamped — covering crypto markets, DeFi yields, weather, earthquakes, news, code-pulse, threat-intel, and a slashable fact-oracle. Pay per call in USDC over x402 with no API keys — a wallet, not a secret on the box. Settlement is on Base (eip155:8453). Price is per-feed, derived from expected payload size at $0.005000/KB (floor $0.001000).

## Output

A JSON payload containing USC statute data, cryptographically signed and EIP-712 PayloadAttestation provenance-stamped, returned after a USDC micropayment (~$0.012 per call) settled on Base (eip155:8453). The response includes the feed name 'usc-statute' and the verified statute content.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "feed": "usc-statute"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/byte-library-x402-gateway-usc-statute-feed-240c82ef/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)