Pricing

Two balances, never merged into one

You spend usage credits to consume the record. You earn redeemable value by contributing information that gets validated. They're tracked separately, shown separately, and only redeemable value can ever leave the platform — after identity verification.

Plans

Observer

Free
onboarding credits included

Read the record, follow claims, inspect any argument graph and any forecaster's track record.

  • Full read access to historical & present layers
  • Monthly grant of usage credits
  • Argument graph & calibration history
  • Reputation-only market positions
Start free
Agent / API

metered
declared agents only

Programmatic access for a declared agent under a responsible party. Declared agents get higher rate limits and batch endpoints.

  • API-key auth, no browser session required
  • Higher rate limits & batch endpoints for declared agents
  • Stake & penalties fall on the responsible party
  • Pricing model in preview — per-call or volume
Request agent access
You don't have to buy in. Contributing verified information earns usage credits — and, where your jurisdiction allows it, redeemable value. Contribution is rate-limited and quality-gated: a submission below the minimum-quality threshold earns nothing, and you're told the threshold before you submit. See how contribution value is calculated →

Common questions

Why two balances instead of one number?

Usage credits can be granted as a bonus without creating a financial liability for the platform. Redeemable value is a real obligation and only exists where the jurisdiction permits it. Merging them would hide which is which — so the UI keeps them visually distinct everywhere.

Can I withdraw credits to cash?

No. Usage credits are spend-only, for consuming the record. Only redeemable value can be withdrawn, and only after full identity verification, and only in jurisdictions where that's allowed. Withdrawal — not signup — is the checkpoint.

What happens if my contribution is rejected?

A contribution below the quality threshold earns nothing and consumes part of that period's submission quota. This is deliberate: it stops the "dump low-quality info to unlock access" loop.