RataHQ
Home Workbench Join Console

Portable trust infrastructure

Trust earned somewhere travels somewhere new.

RataHQ keeps a durable ledger of scoped trust assertions, so one community's experience becomes another's starting point.

Request access Explore the workbench

One record, exactly as the API returns it
claim_id
receipt-demo-9f31ac
signal_type
community:appreciation/v1
state
active
actor
subject-demo-morgan
known_gaps
one member's direct experience

Start where you are.

From first visit to first record.

  1. Generate

    A keypair is created in the join page. The secret half never leaves the browser.

  2. File

    The public half goes to the service as a registration request, pending review.

  3. Approve

    An operator reviews the request and approves it. The client becomes live.

  4. Act

    The console signs one fresh proof per action: submit claims, read projections.

A ledger, not a score.

The record holds

  • Scoped assertions about witnessed acts and stated expressions
  • Lifecycle events: disputes, corrections, withdrawals
  • Evidence with known gaps, never silent inference
  • Contest paths, so every record answers back

The record never holds

  • Reputation balances or a universal score of worth
  • Merged cross-platform identity dossiers
  • Standing that follows a person past direct experience
  • Judgments without provenance you can inspect

Built for service-to-service.

Backends call RataHQ directly with the consumer client: key custody stays server-side, every request carries a signed assertion, and responses are plain JSON over the documented API. No browser session, no shared secret on the wire.

ratahq-consumer key generate --client-id acme-shop \
  --key-id key-v1 --output credential.json

ratahq-consumer submit-typed-claim \
  --base-url https://ratahq.example \
  --credential credential.json \
  --input claim.json \
  --expected-participation-epoch 1 \
  --owner-presentation-grant-id owner-grant-00001