# OBOL Loop Trading Regime Monitor

> OBOL Loop Trading Regime Monitor is a paid API for AI agents from obol-x402.fly.dev, paid per call via x402, $0.2/call, status down (last checked 2026-09-15).

Returns the current trading loop regime and action policy (e.g. calm/ok_to_act) with a recommended recheck interval for AI agents executing on-chain trades

## Facts

- Endpoint: GET https://obol-x402.fly.dev/v1/loop/trading
- Price: $0.2/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/obol-loop-trading-regime-monitor-2ac37fc1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MtNd5D2kDvU0lutR9x0O4

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 obol-loop-trading-regime-monitor-2ac37fc1
```

Example prompt: Before my agent executes the next swap on Base, check OBOL's trading loop to see if the current regime is calm and the action policy is ok_to_act, and tell me how many seconds until I should recheck.

## When to prefer this

Choose this endpoint when an autonomous trading agent needs a lightweight, real-time signal about current market conditions before deciding whether to act. It is ideal for polling loops that need a binary proceed/pause directive with a built-in recheck cadence, without requiring complex token-level analysis. Prefer this over full pre-trade token analysis endpoints when you already know the token is safe and just need macro regime context.

## Known failure modes

- Payment not received — 402 response requiring USDC payment on Base before data is returned
- Invalid or missing properties parameter — may return schema validation error
- Service unavailable — Fly.dev hosting downtime returns 5xx
- Regime data stale — recheck_in_seconds may be elevated during data feed interruptions

## How this service works

OBOL trading tick — the agent LOOP endpoint: one settle returns Bitcoin market REGIME + broadcast-timing pulse + multi-asset spots with integrity + a machine action policy (ok_to_act / hold / wait / recheck). Poll each cycle. Not raw RPC. Free teaser: GET /v1/loop/trading/preview. Cryptographically signed (Ed25519) — every response is independently verifiable via /.well-known/obol-pubkey.

## Output

A JSON object containing: the loop identifier (e.g. 'trading_tick'), the current market regime label (e.g. 'calm'), the action policy directive for the agent (e.g. 'ok_to_act'), and a recheck_in_seconds value indicating how long to wait before polling again. Each response is Ed25519-signed for independent verification.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/obol-loop-trading-regime-monitor-2ac37fc1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from obol-x402.fly.dev](https://www.zero.xyz/host/obol-x402.fly.dev/llms.txt)