# TruthBear Gauge Lifecycle

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

Returns the official lifecycle state (status band, birth/end dates, death type, lifespan) for a named entity across up to 19 tracked industry lines including stablecoins, AI tools, neoclouds, DePIN, RWA, and more.

## Facts

- Endpoint: GET https://api.truthbear.co/gauge/lifecycle
- Price: $0.005/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-lifecycle-95646d7d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_N9EcyCAEESXSLsu30Ro1Z

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-lifecycle-95646d7d
```

Example prompt: What's the official lifecycle status of TerraUSD-UST — is it active, dead, or something else, and when did it end? Also pull any death type and source reference TruthBear has on it.

## When to prefer this

Use this endpoint when you need the official, sourced lifecycle state of a specific named entity (stablecoin, AI tool, neocloud, DePIN project, carbon project, ESG fund, RWA, or tariff measure) and want a single authoritative lookup rather than time-series history or calibrated normalized signals. Prefer this over sibling endpoints like gauge/history-series (which gives full time-series exports) or gauge/calibrated (which adds normalized indices) when you simply need the current status band, dates, and death classification in one cheap call. The no_charge 422 for unknown IDs makes exploratory lookups safe and cost-free.

## Known failure modes

- Unknown entity id returns HTTP 422 with a no_charge signal — the call is not billed
- Ambiguous entity tracked by multiple lines returns all matches unless narrowed with the optional industry parameter
- Stale or incomplete upstream source data may result in missing birth/end dates for some records
- If the entity id casing or slug does not match the catalog exactly, a 422 is returned

## How this service works

One id in, its official lifecycle state out - no need to know which line tracks it first. Covers 19 lifecycle lines (stablecoins, AI tools and datasets, neoclouds, DePIN, RWA, carbon projects, ESG funds, tariff measures and more): status band, birth/end dates, death type, lifespan, official source_ref. If two lines track the same id you get BOTH - nothing is picked for you. Unknown id -> 422 no_charge, not billed. Every record carries an offline-recomputable record_hash. $0.0050 per call.

## Output

A JSON object containing one or more lifecycle records for the queried entity. Each record includes: status band (e.g. active, dead, deprecated), birth date, end date, death type, lifespan duration, official source reference (source_ref), and an offline-recomputable record_hash for integrity verification. If multiple industry lines track the same entity, all matching records are returned. Unknown entity IDs return a 422 no_charge error without billing.

## 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": [
      "entity"
     ],
     "properties": {
      "entity": {
       "type": "string",
       "examples": [
        "coreweave"
       ],
       "description": "required - the id to look up (e.g. coreweave, terrausd-ust, jasper-ai, helium). Full list: free GET /gauge/catalog?all=1 -> signals[] where signal_id ends in .lifecycle, then ?signal_id=<id> for its entities[]"
      },
      "industry": {
       "type": "string",
       "description": "optional - narrow to one line when an id is tracked by more than one (e.g. ai-compute, stablecoin). Omit and you get every matching line"
      }
     },
     "additionalProperties": false
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "const": "json"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/truthbear-gauge-lifecycle-95646d7d/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)