# Orders of Magnitude Namespace Index Query

> Orders of Magnitude Namespace Index Query is a paid API for AI agents from x402-api-production-5133.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-13).

Queries the namespace index to search or retrieve data and AI service results via x402 micropayment protocol

## Facts

- Endpoint: GET https://x402-api-production-5133.up.railway.app/ns/index/query?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/orders-of-magnitude-namespace-index-query-56172873
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_E_I5p50a-uaGbEwvNIb-e

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 orders-of-magnitude-namespace-index-query-56172873
```

Example prompt: Search the Orders of Magnitude namespace index for 'climate change economic impact' and return whatever data records come back.

## When to prefer this

Use this endpoint when you need to query a micropayment-gated namespace index for data or AI service results and are already integrated with the x402 payment protocol. Prefer this over general-purpose search APIs when accessing specifically the Orders of Magnitude indexed dataset, where a $0.01 USDC per-call cost is acceptable and you need structured index lookups rather than open-web search.

## Known failure modes

- Missing required 'input' parameter returns a 400 or validation error
- Payment not fulfilled via x402 protocol returns a 402 Payment Required response
- Input string yields no matching records in the namespace index, returning empty results
- Service unavailability on Railway deployment causes 503 errors
- Malformed or excessively long input strings may cause unexpected errors

## How this service works

Data and AI services via x402 payment protocol

## Output

Returns a JSON object containing index query results matching the input string, which may include data records, AI-generated content, or structured information from the namespace index. The response schema is open-ended ({}) so the shape of returned data depends on what is stored in the index.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/orders-of-magnitude-namespace-index-query-56172873/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-api-production-5133.up.railway.app](https://www.zero.xyz/host/x402-api-production-5133.up.railway.app/llms.txt)