# TruthBear Gauge – Single Signal Current Reading

> TruthBear Gauge – Single Signal Current Reading is a paid API for AI agents from api.truthbear.co, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns the current reading for a specific signal/entity pair, benchmarked against official thresholds (band, distance-to-action) and a 5-year same-season percentile, across 180+ signals spanning macro, weather, hazard, shipping, filings, crypto, and lifecycle domains.

## Facts

- Endpoint: GET https://api.truthbear.co/gauge
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/truthbear-gauge-single-signal-current-reading-d6008efc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lJA6jPZrqyYR8ft-HO_6c

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 truthbear-gauge-single-signal-current-reading-d6008efc
```

Example prompt: What is the current river level reading for gauge station 07010000 on the hydrology.river-level signal — is it in the normal band or approaching an action threshold, and how does it compare to the same time of year historically?

## When to prefer this

Use this endpoint when you need a single authoritative current-state snapshot for a specific signal and entity, with threshold-relative context (band, distance-to-action) and seasonal historical framing (5-year percentile). Prefer it over the history-series endpoint when you want the present reading rather than a time series, and over the calibrated add-on when raw (not normalized) readings are sufficient. Always check /gauge/coverage or /gauge/catalog first to confirm the signal_id/entity pair is valid and avoid unbillable 422 errors.

## Known failure modes

- 422 no_charge: No data available for the requested signal_id/entity pair — not billed
- Invalid signal_id format (must be genus.species ASCII form) causes rejection
- Invalid or unrecognized entity identifier for the given signal_id
- Mismatched signal_id/entity pair not in the catalog causes failure — use /gauge/catalog to validate pairs first
- Network or provider timeout resulting in no response

## How this service works

[SIGNAL+PROOF] One official signal record for any signal_id and entity: current reading against the OFFICIAL threshold ladder (band, distance-to-action) plus a 5-year same-season percentile so you can tell routine from unusual. 180+ signals across macro, weather, hazard, shipping, filings, crypto and lifecycle lines. Free coverage check first at /gauge/coverage. Descriptive only, never a forecast or advice. No data -> 422 no_charge, not billed. $0.01 per call.

## Output

A JSON object containing the current scalar reading for the requested signal/entity pair, its placement within the official threshold ladder (band label and distance-to-action), and a 5-year same-season percentile indicating whether the reading is routine or anomalous. Returns a 422 no_charge error if no data is available for the requested pair, so you are not billed for missing data.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "queryParams"
   ],
   "properties": {
    "type": {
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "signal_id",
      "entity"
     ],
     "properties": {
      "entity": {
       "type": "string",
       "examples": [
        "07010000"
       ],
       "description": "required - monitored object id, PAIRED WITH signal_id (e.g. 07010000 for hydrology.river-level, japan for earthquake.current_activity). Valid pairs: free GET /gauge/catalog?signal_id=<signal_id> -> signals[0].entities[]"
      },
      "signal_id": {
       "type": "string",
       "examples": [
        "hydrology.river-level"
       ],
       "description": "required - signal id in genus.species ASCII form (e.g. hydrology.river-level, crypto.spot, macro.unemployment, earthquake.current_activity). Full list: free GET /gauge/catalog"
      }
     },
     "additionalProperties": false
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "const": "json"
    },
    "example": {}
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "grade": "screening-level, not decision-grade",
  "scope": {
   "full": "https://api.truthbear.co/scope/v1",
   "verifiability": "via-endpoint",
   "monitoring_not_forecast": true,
   "intelligence_not_command": true
  },
  "entity": "03255000",
  "nature": "This API supplies data organisation and trend description only. It is not a recommendation to act; the decision is yours. Purely descriptive - no judgement, no prediction.Official source plus record_hash; verify with the free /gauge/verify.",
  "current": {
   "gauge_height_ft": 30.69
  },
  "signal_id": "hydrology.river-level",
  "provenance": {
   "freshness": "fresh",
   "age_hours_now": 23,
   "freshness_basis": "cadence=daily; fresh<=24h; recent<=192h; dead_source>1440h; age_basis=request-time(now minus observed_at)"
  },
  "source_ref": "https://waterdata.usgs.gov/monitoring-location/03255000/",
  "summary_en": "Ohio River at Cincinnati, OH: 30.69 ft gauge height - no flooding, 9.31 ft below the first official alert (action stage 40 ft). seasonal percentile 0.922 (rare). falling vs 24h ago.",
  "entity_name": "Ohio River at Cincinnati, OH",
  "observed_at": "2026-08-25T04:00:00.000Z",
  "record_hash": "sha256:5969b8a147f438254edadf246ed1d7801a77c29babb5d725e17870320d620dd7",
  "record_hash_verifiable": {
   "mode": "via-endpoint",
   "note": "This response is a projected delivery (some core fields are omitted to control size). Cross-check record_hash with the free /gauge/verify, or buy /gauge to get the complete core for offline recomputation."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/truthbear-gauge-single-signal-current-reading-d6008efc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.truthbear.co](https://www.zero.xyz/host/api.truthbear.co/llms.txt)
