# TruthBear Stablecoin Depeg & Lifecycle Gauge > TruthBear Stablecoin Depeg & Lifecycle Gauge is a paid API for AI agents from api.truthbear.co, paid per call via x402, $0.25/call, status unknown (last checked 2026-09-13). Returns a three-leg sequential chain assessment of a single stablecoin's peg health, covering leading depeg pressure, current peg deviation and market cap, and realized redemption or lifecycle outcome. ## Facts - Endpoint: GET https://api.truthbear.co/gauge/stablecoin-region - Price: $0.25/call - Payment: x402 - Status: unknown - Last checked: 2026-09-13 - Activations on Zero: 0 - Tags: x402 - Canonical page: https://www.zero.xyz/c/truthbear-stablecoin-depeg-lifecycle-gauge-f3094327 - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Csf0JNB7_CRelO0coon2A 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-stablecoin-depeg-lifecycle-gauge-f3094327 ``` Example prompt: Can you check the TruthBear stablecoin gauge for TerraUSD (terrausd-ust) and tell me how many signal legs are lit — specifically the current peg deviation, reserve status, any regulatory notices, and whether there's been a realized redemption or lifecycle outcome? ## When to prefer this Use this endpoint when you need a structured, multi-signal assessment of a single stablecoin's peg health, depeg pressure, and lifecycle status — especially when you want a confidence-weighted three-leg chain rather than a single data point. It is the right choice when monitoring algorithmic or collateralized stablecoins for depeg events, regulatory notices, or post-collapse lifecycle outcomes. Prefer it over raw exchange data when you need a synthesized, sequential signal chain from TruthBear's curated exchange and registry feeds. ## Known failure modes - 422 no_charge returned when no data exists for the requested entity — not billed - Invalid or unrecognized entity ID returns an error; valid entity IDs can be fetched from GET /gauge/catalog?signal_id= - Partial confidence if only one or two legs have data available — lower confidence score returned - Exchange or registry feed outages may result in incomplete leg data ## How this service works [3-LEG] Stablecoin chain, one stablecoin (?entity=terrausd-ust): leading depeg pressure - peg deviation, reserves, regulatory notices -> current current peg and market cap -> realized redemption and lifecycle outcome (confirmation gate). A chain, not one reading: confidence = how many legs are lit, in order. Sources: exchange and registry feeds. Descriptive only, never a forecast or advice. No data -> 422 no_charge, not billed. $0.25 per call. ## Output A structured JSON response containing up to three sequentially unlocked legs: (1) leading depeg pressure signals including peg deviation and reserve status and any regulatory notices, (2) current peg level and market cap from exchange and registry feeds, and (3) realized redemption and lifecycle outcome with a confirmation gate. A confidence score reflects how many legs are lit in order. Returns HTTP 422 with no_charge if no data is available for the requested entity. ## Request schema (JSON Schema) ```json { "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "input": { "type": "object", "properties": { "type": { "const": "http" }, "method": { "type": "string", "enum": [ "GET" ] }, "queryParams": { "type": "object", "additionalProperties": false, "properties": { "entity": { "type": "string", "description": "required - monitored object id, paired with signal_id; free list at GET /gauge/catalog?signal_id= -> signals[0].entities[]", "examples": [ "terrausd-ust", "iron-titan", "basis-cash-bac", "empty-set-dollar-esd", "dynamic-set-dollar-dsd", "dei-deus" ], "x-accepted-values": { "shown": 6, "total": 22, "all": "https://api.truthbear.co/schemas/gauge-stablecoin-region.input.json" } } }, "required": [ "entity" ] } }, "required": [ "type", "method", "queryParams" ] }, "output": { "type": "object", "properties": { "type": { "const": "json" }, "example": {} }, "required": [ "type" ] } } } ``` ## Response schema (JSON Schema) ```json { "type": "json", "example": { "legs": { "lifecycle": { "band": "dead", "source_ref": "https://www.reuters.com/technology/how-terra-collapse-triggered-crypto-panic-2022-05-13/", "record_hash": "sha256:a009c4f22c72a04c50f598b09aa35663f16a1eaa106754de1298c568ec834cef" }, "peg_distress": { "band": "depegged", "source_ref": "https://www.reuters.com/technology/how-terra-collapse-triggered-crypto-panic-2022-05-13/", "record_hash": "sha256:d69b4a36144a8d104557bf38fd8350011003738a0d26cd3d6e10f75d06416880" }, "redemption_flight": { "band": "collapsed", "source_ref": "https://www.reuters.com/technology/how-terra-collapse-triggered-crypto-panic-2022-05-13/", "record_hash": "sha256:8051f4bbe6bdc4d250e88078fc3120763ed93a11f92e72aa8802da012da6cfd9" } }, "name": "TerraUSD (UST)", "grade": "screening-level, not decision-grade", "scope": { "full": "https://api.truthbear.co/scope/v1", "verifiability": "unknown", "monitoring_not_forecast": true, "intelligence_not_command": true }, "entity": "terrausd-ust", "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.", "provenance": { "freshness": "recent", "age_hours_now": 154, "freshness_basis": "cadence=default; fresh<=24h; recent<=192h; dead_source>1440h; age_basis=request-time(now minus observed_at)" } } } ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/truthbear-stablecoin-depeg-lifecycle-gauge-f3094327/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)