# Bitcoin Ordinals & OP_RETURN Flow Analytics

> Bitcoin Ordinals & OP_RETURN Flow Analytics is a paid API for AI agents from api.carbon-cashmere.de, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Returns hourly bucketed counts of Bitcoin Ordinals inscriptions (detected via witness-envelope magic bytes) and OP_RETURN byte volume over a configurable window up to 7 days.

## Facts

- Endpoint: GET https://api.carbon-cashmere.de/v1/btc-derivatives/ordinals-flow
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-carbon-cashmere-de-5ab7430a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KAeiCLEswZBklr4M9YKF7

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 api-carbon-cashmere-de-5ab7430a
```

Example prompt: Show me the hourly Bitcoin Ordinals inscription counts and OP_RETURN byte volume for the last 24 hours so I can see how active on-chain inscription activity has been today.

## When to prefer this

Use this endpoint when you need time-series (hourly) granularity on Bitcoin Ordinals inscription activity and OP_RETURN usage, especially for trend analysis, monitoring inscription spikes, or correlating on-chain data payload volume with market events. Prefer this over generic block explorers when you need programmatic, structured hourly aggregates with both inscription counts and OP_RETURN byte metrics in a single call.

## Known failure modes

- Window parameter exceeds 7-day limit — API returns an error or truncates data
- No blocks mined in a given hour — bucket may show zero values
- Payment not included or insufficient USDC — x402 payment required error
- Service unavailable or node sync lag — stale or missing recent hours
- Invalid query parameter format — 400 bad request

## How this service works

Hourly Bitcoin Ordinals inscriptions + OP_RETURN byte volume. Inscriptions detected via witness-envelope magic bytes (cord). Window up to 7d.

## Output

An array of hourly buckets, each containing: the ISO timestamp of the hour, number of Bitcoin blocks in that hour, number of Ordinals inscriptions detected via witness-envelope magic bytes, total OP_RETURN bytes, and total OP_RETURN transaction count. The response also reports the detection method (witness_envelope_scan + scriptpubkey_opreturn_count) and the query window.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {}
 }
}
```

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "window": "24h",
  "buckets": [
   {
    "hour": "2026-05-17T14:00+00:00",
    "inscriptions": 1247,
    "op_return_bytes": 142880,
    "op_return_count": 8821
   }
  ],
  "summary": {
   "total_inscriptions": 31840,
   "avg_inscriptions_per_block": 221
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-carbon-cashmere-de-5ab7430a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.carbon-cashmere.de](https://www.zero.xyz/host/api.carbon-cashmere.de/llms.txt)