# IETF RFC Lookup

> IETF RFC Lookup is a paid API for AI agents from intel.rallylive.ca, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Retrieves full metadata for an IETF RFC by number, including title, authors, status, abstract, relations, and links to the specification text.

## Facts

- Endpoint: GET https://intel.rallylive.ca/dev/rfc
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ietf-rfc-lookup-1478bfec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hsy-1bXrvCinjU-YYbVj8

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 ietf-rfc-lookup-1478bfec
```

Example prompt: Can you look up RFC 9110 for me — I need its title, current status, who wrote it, and whether it obsoletes or updates any earlier RFCs?

## When to prefer this

Use this endpoint when an agent or engineer needs to programmatically resolve IETF RFC metadata by number — particularly for protocol research, standards compliance checks, or navigating RFC obsolescence chains. Preferred over manually scraping the IETF website or searching free-text when a specific RFC number is known and structured metadata is required.

## Known failure modes

- RFC number not found or does not exist — returns error or empty result
- Missing or malformed RFC number in query — returns validation error
- IETF data source temporarily unavailable — upstream timeout or fetch failure
- Non-numeric or out-of-range RFC number input — returns error

## How this service works

IETF RFC lookup by number: title, authors, publication date, status (Internet Standard, Proposed Standard, Informational...), page count, obsoletes/obsoleted-by/updates relations, keywords, abstract, and links to the HTML/text versions. Protocol-spec navigation for engineering agents. $0.01 per RFC.

## Output

Returns structured metadata for the requested RFC: title, author list, publication date, status (e.g. Internet Standard, Proposed Standard, Informational, Historic), page count, relationships to other RFCs (obsoletes, obsoleted-by, updates, updated-by), keywords, abstract text, and URLs to the HTML and plain-text versions on the IETF website.

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ietf-rfc-lookup-1478bfec/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from intel.rallylive.ca](https://www.zero.xyz/host/intel.rallylive.ca/llms.txt)