Build

One REST API, one MCP server

Claims in, Trust Objects out. Verification needs neither — it runs against bytes the reader already holds.

Surfaces

Issue an assessment, retrieve a Trust Object, list an epoch, fetch an anchor proof.

The same operations exposed to an agent, so a model can issue and read records inside its own loop.

A walk, not an endpoint. It can be run offline against canonical bytes.

Keys are issued per institution and per named use. Pricing is quoted per institution and is not published.

REST APISeal, supersede and fetch Trust Objects over HTTPS.Reference
MCP serverThe same operations exposed to an agent as tools.Reference
Verification endpointCheck a certificate against the anchor. No key required.Verify
Conformance suiteIssued to implementers under agreement, not published.Register

One REST surface and one MCP server. Both speak TIP/1.0, and a record written through either verifies the same way.