# reg-watch-status

> reg-watch-status is a paid API for AI agents from store.cryptotradecalc.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Polls the US Federal Register for a given topic and returns a stable fingerprint (latest document number + 7-day count) so monitoring agents can detect new regulatory activity without LLM cost.

## Facts

- Endpoint: GET https://store.cryptotradecalc.com/api/reg-status
- 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/reg-watch-status-048dfa7e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wrfWWR1JOsvmlfEhWOap3

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 reg-watch-status-048dfa7e
```

Example prompt: Check the US Federal Register for any new activity on the topic 'cryptocurrency' and tell me if anything has changed since last time — I just need a quick status fingerprint, not the full documents.

## When to prefer this

Choose this endpoint when you need a cheap, byte-stable polling signal for US Federal Register activity and want to avoid LLM or heavy parsing costs on every check. It is ideal as the first stage in a two-tier monitoring pipeline: poll here frequently at $0.01/call, and only invoke costlier analysis endpoints when the fingerprint actually changes. Prefer it over full-text retrieval endpoints when the goal is purely change detection, not content analysis.

## Known failure modes

- Missing required 'topic' query parameter — returns error indicating topic is required
- Topic returns zero documents — fingerprint may be null or zero count, not necessarily an error
- Federal Register upstream unavailable — may return timeout or 5xx error
- Overly broad topic keyword — returns high document counts with low specificity, making change detection noisy

## How this service works

reg-watch-status: Cheap change-detector for US Federal Register activity on any topic. Returns a stable latestDocumentNumber fingerprint plus a 7-day document count, so a monitoring agent can poll hourly and compare against its last value: unchanged means nothing was published and no further spend is needed. When it changes, escalate to /api/reg-changes for the delta or a topic brief for LLM analysis. No LLM, fast and byte-stable. Query: topic (required keyword or phrase).

## Output

Returns a stable latestDocumentNumber fingerprint and a 7-day document count for the queried topic. If both values match the previous poll, nothing new was published; a change signals new Federal Register activity and warrants follow-up calls to richer endpoints.

## 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": {
      "topic": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/reg-watch-status-048dfa7e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from store.cryptotradecalc.com](https://www.zero.xyz/host/store.cryptotradecalc.com/llms.txt)