# Orders of Magnitude API – NS Cache Lookup

> Orders of Magnitude API – NS Cache Lookup 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-09-14).

Performs a cached namespace lookup or retrieval using a string input key, returning cached data and AI service results via the x402 micropayment protocol.

## Facts

- Endpoint: GET https://x402-api-production-5133.up.railway.app/ns/cache
- 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/orders-of-magnitude-api-ns-cache-lookup-64ed8c5b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Txu9-41tdHuqWlRTO2406

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-api-ns-cache-lookup-64ed8c5b
```

Example prompt: Look up the cached result for the key 'latest_market_summary' in the Orders of Magnitude namespace cache and return whatever is stored there.

## When to prefer this

Use this endpoint when you need to retrieve previously computed or stored results from the Orders of Magnitude namespace cache and want to avoid recomputing expensive AI or data operations. It is best suited for scenarios where the same query has likely been run before and a cached result is acceptable. Prefer this over fresh computation endpoints when latency and cost savings are the priority.

## Known failure modes

- Cache miss: the requested key does not exist in the namespace cache, returning an empty or error response
- Invalid or missing input string: returns a 400-level error due to the required 'input' field being absent
- Payment failure: x402 payment protocol authorization fails, blocking the request
- Service unavailable: Railway-hosted backend is down or unreachable, returning a 5xx error
- Expired cache entry: the key exists but the underlying data may be stale or cleared

## How this service works

Data and AI services via x402 payment protocol

## Output

Returns a JSON object containing the cached data associated with the provided input key from the namespace cache. The response schema is open-ended, so the shape of the returned data depends on what was previously stored under that key.

## 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-api-ns-cache-lookup-64ed8c5b/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)