# Oracles Service Status Incident Detail Lookup

> Oracles Service Status Incident Detail 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-15).

Retrieves stored detail for a single tracked service-status incident by its entityId (e.g. 'status:GitHub:abc123').

## Facts

- Endpoint: GET https://oracles-production.up.railway.app/v1/service-status/status
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/oracles-service-status-incident-detail-lookup-da57f7ed
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0zq7Bw0KmxNxqKvuHMC7A

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 oracles-service-status-incident-detail-lookup-da57f7ed
```

Example prompt: Can you fetch the full incident details for the service status entity 'status:GitHub:abc123' from the oracles status tracker?

## When to prefer this

Use this endpoint when you already have a specific service status entityId (e.g. from a prior list call or alert) and need the full detail record for that single incident. Prefer this over listing endpoints when you want deep detail on one known incident rather than browsing all tracked entities.

## Known failure modes

- Missing or invalid entityId returns empty or error response
- EntityId not found in stored incidents returns null or 404-equivalent
- Malformed entityId format causes lookup failure
- Payment not processed results in 402 error
- Omitting the id query parameter returns a list of tracked entities instead of a single record

## How this service works

Stored detail for a single incident (entityId like 'status:GitHub:abc123').

## Output

Returns a stored entity object containing the full detail record for the requested service status incident, including incident metadata and status fields associated with the given entityId.

## 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/oracles-service-status-incident-detail-lookup-da57f7ed/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)