# TruthBear Signal-Plus: Official Signal + Unverified Chatter Bundle

> TruthBear Signal-Plus: Official Signal + Unverified Chatter Bundle is a paid API for AI agents from api.truthbear.co, paid per call via x402, $0.09/call, status unknown (last checked 2026-09-14).

Returns one verified official signal record with its offline-recomputable cryptographic proof, plus unverified public-channel chatter for a topic from the last 48 hours, delivered as two separate non-merged top-level keys.

## Facts

- Endpoint: GET https://api.truthbear.co/shadow/signal-plus
- Price: $0.09/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/truthbear-signal-plus-official-signal-unverified-chatter-bundle-3ab01d9e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IZ1IVvGnnRYMewi45KU1A

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-signal-plus-official-signal-unverified-chatter-bundle-3ab01d9e
```

Example prompt: Pull the official signal record and proof for hydrology.river-level on entity 07010000, plus any public chatter about 'tariff' from the last 48 hours — I want both halves kept separate so I can compare the verified reading against what people are saying.

## When to prefer this

Use this endpoint when you need both the tamper-evident official signal record AND the unverified public discourse for the same topic in a single call, and you require them to remain cryptographically separated. Prefer it over calling gauge and chatter endpoints separately to save round-trips and cost. Check GET /shadow/catalog first (free) to confirm the topic exists and avoid a 422 no-charge response. If you only need the official signal without chatter, use a gauge endpoint instead.

## Known failure modes

- 422 no_charge: no chatter posted for the topic in the 48-hour window — call is not billed
- 400 bad request: missing required parameters (signal_id, entity, or topic)
- 404 not found: signal_id or entity not in catalog — check GET /gauge/catalog first
- 404 not found: topic not in catalog — check GET /shadow/catalog first
- 402 payment required: x402 payment not provided or insufficient
- 503 service unavailable: signal database temporarily unreachable

## How this service works

[SIGNAL+PROOF+CHATTER] One official signal record with its offline-recomputable proof, PLUS the unverified public-channel chatter for a topic from the last 48h - delivered as two separate top-level keys that are never merged. The unverified half lives in its own database with an engine-level trigger forbidding updates, and contributes nothing to the official hash. Nothing posted in the window -> 422 no_charge, not billed (check GET /shadow/catalog first, free). $0.09 per call.

## Output

A JSON response with two top-level keys: one containing the official signal record and its offline-recomputable cryptographic proof (with signal hash), and a second containing unverified public-channel chatter for the specified topic from the last 48 hours. The two halves are never merged. If no chatter was posted in the 48-hour window, returns HTTP 422 with a no_charge code and the call is not billed.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/truthbear-signal-plus-official-signal-unverified-chatter-bundle-3ab01d9e/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)