# BYTE Library x402 Gateway – Runtime EOL Feed

> BYTE Library x402 Gateway – Runtime EOL Feed is a paid API for AI agents from x402.payperbyte.io, paid per call via x402, $0.069336/call, status unknown (last checked 2026-09-13).

Returns a cryptographically signed, EIP-712 provenance-stamped data payload indicating software/runtime end-of-life (EOL) status, paid per call in USDC via x402.

## Facts

- Endpoint: GET https://x402.payperbyte.io/feeds/runtime-eol
- Price: $0.069336/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/byte-library-x402-gateway-runtime-eol-feed-4ca98b07
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZVrwtuS-28V8OSxkWjs0I

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-runtime-eol-feed-4ca98b07
```

Example prompt: Pull the latest signed runtime EOL feed from BYTE Library — I need to know which runtimes are past or approaching end-of-life, and I want the payload to include a cryptographic provenance attestation so I can verify the data source.

## When to prefer this

Choose this endpoint when you need tamper-evident, cryptographically attested runtime EOL data and cannot rely on unsigned third-party sources. Ideal for compliance pipelines, security audits, or automated dependency checks where provenance matters and you want pay-per-call pricing without API key management.

## Known failure modes

- Insufficient USDC payment or wallet balance — 402 Payment Required with required payment details
- Invalid or missing x402 payment header — 402 error with payment channel info
- Feed temporarily unavailable — 503 Service Unavailable
- Malformed request properties — 400 Bad Request
- Network congestion on Base chain delaying settlement — delayed or timeout response

## How this service works

End-of-life dates and status for language runtimes, frameworks, OSes (endoflife.date)

## Output

A JSON payload containing runtime end-of-life data (EOL dates, support status per runtime version), along with a cryptographic EIP-712 PayloadAttestation signature proving data provenance. Settlement occurs on Base (eip155:8453) at ~$0.069 USDC per call.

## 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": "runtime-eol"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/byte-library-x402-gateway-runtime-eol-feed-4ca98b07/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)