mocop
Browse · Docs · Guide · Analyze

Trooth Network API

API by Trooth · rest

The public contract for api.trooth.co. Public reads need no key, and are readable from a browser on any site: they carry Access-Control-Allow-Origin: * and no credentials are sent or honored. Authenticated operations take a sender-constrained credential (DPoP, RFC 9449), as https://trooth.co/docs/apiauthorization describes: a workspace API key created with dpop_jkt, or a scoped token (st_), sent as Authorization: DPoP <token> with a fresh proof in the DPoP header on every request. A copy of the credential alone is refused, and so is a bound key sent as a plain bearer. A key created without dpop_jkt is an ingest key, a bearer credential that reaches only POST /v1/evidence/webhook, which this document does not publish. A refused credential answers 401 with a WWW-Authenticate: DPoP challenge naming the error: dpop_required, invalid_dpop_proof or invalid_token. WHICH DOCUMENT COVERS WHAT. This one covers api.trooth.co. The public, credential-free reads of…

Endpoint: https://api.trooth.co/

Verification: observed. Source: crawl.

Capabilities (8)

  • Check the action evidence signing key
  • Read the state of an action evidence reference
  • List Trooth's public signing keys
  • Read a published receipt
  • Get a company's badge image
  • Buyer-intent leads from the public marketplace
  • Draft answers from witnessed evidence
  • Check a Trust Ledger Token
About · Contact · Privacy