# Python PEPs Status Lookup

> Python PEPs Status Lookup is a paid API for AI agents from oracles-production.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns stored detail for a single Python Enhancement Proposal (PEP) by its entityId, or lists all tracked PEPs if no ID is provided.

## Facts

- Endpoint: GET https://oracles-production.up.railway.app/v1/python-peps/status
- 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/python-peps-status-lookup-6c73fcc5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DKRNQEDtgtWoHf0gy4FVg

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 python-peps-status-lookup-6c73fcc5
```

Example prompt: Can you pull up the stored details and status for Python PEP 703 — the one with entity ID pep:703?

## When to prefer this

Use this endpoint when you need structured, stored detail for a specific Python Enhancement Proposal by its entityId, especially within a compliance or standards-monitoring workflow on the oracles-production platform. Prefer this over a web search when you need machine-readable PEP status data with a consistent schema.

## Known failure modes

- Invalid or unknown entityId returns empty or error response
- Malformed entityId format (not 'pep:NNN') may return no match
- Network or service unavailability returns 5xx error
- Payment failure (x402) blocks access if USDC not provided

## How this service works

Stored detail for a single PEP (entityId like 'pep:703').

## Output

Returns a JSON object containing stored entity details for the requested PEP, including its status and metadata. If no ID is provided, returns a list of all tracked PEP entities.

## 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": {
      "id": {
       "type": "string",
       "description": "entityId to look up; omit to list tracked entities"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "entity": {
       "type": "object"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/python-peps-status-lookup-6c73fcc5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from oracles-production.up.railway.app](https://www.zero.xyz/host/oracles-production.up.railway.app/llms.txt)