Verify before you transact, with no browser

Get access

Reading and verifying need no account and no token. You need access only to publish, to receive webhooks, or to act for an organization.

Scopes: ask only for what the agent does

Clients made before the manage scopes existed keep every scope their tier had. A new client gets only the scopes you give it.

curl -s -X POST https://aisourceoftruth.com/oauth/token -H 'content-type: application/json' -d '{"grant_type":"client_credentials","client_id":"<id>","client_secret":"<secret>","scope":"publish:provenance"}'
curl -s https://aisourceoftruth.com/.well-known/oauth-protected-resource/mcp

37 tools, one per API call

Streamable HTTP at https://aisourceoftruth.com/mcp, protocol 2025-11-25. Reads are anonymous. Writes take a Tier-2 token on the request and a signature by your key, the same as the REST API.

{
  "mcpServers": {
    "aisourceoftruth": {
      "url": "https://aisourceoftruth.com/mcp"
    }
  }
}

Tools

Sign an agent in with PromptReports ID

Across the products Planned state from family.json. Here Switching on.

This registry does not accept the token yet. Until it does, register with OAuth below.

No human in the loop

1. Register a client (RFC 7591), no human in the loop

   curl -X POST https://aisourceoftruth.com/oauth/register -H 'content-type: application/json' -d '{"client_name":"my-agent"}'

2. Mint a Bearer token with client_credentials

   curl -X POST https://aisourceoftruth.com/oauth/token -H 'content-type: application/json' -d '{"grant_type":"client_credentials","client_id":"<id>","client_secret":"<secret>"}'

3. To publish, register a publisher with a key you generated; the registry never sees the private key

   POST https://aisourceoftruth.com/v1/publishers (or the MCP tool register_publisher), signed by the key in the body

Up to 1,000 digests per call. Each result carries the signature status, the inclusion proof (or pending), the cosignature quorum, the errata count and the judge version.

curl -X POST https://aisourceoftruth.com/v1/verify-batch -H 'content-type: application/json' -d '{"digests":["<64-hex record digest>"]}'

1. Publish an identity record (POST /v1/records, profile identity) naming the kind and the subject, signed by your publisher key.
2. Run its check with POST /v1/identity-bindings/verify { digest }, signed the same way. A passed check appends a public identity.verified event.
3. End a binding with a later identity record that names it in revokes. The old binding stays in history.

A binding says this publisher proved control of that identity on that date. It is not an endorsement. Publishers can also add, check and end bindings in the console.

A checkpoint record, signed by your key

{
  "profile": "checkpoint",
  "artifact": {
    "digest": "<root_hash>"
  },
  "checkpoint": {
    "log_id": "my-agent/audit",
    "tree_size": 48211,
    "root_hash": "<root_hash>",
    "algorithm": "sha256-chain",
    "period_end": "<ISO time>"
  },
  "created_at": "<ISO time>"
}

• Post the head of your agent's own hash chain on a timer. Once a head is on this log, a rewrite below it shows.
• A smaller tree_size than your last checkpoint for that log_id is refused as a rollback; the same tree_size with a different root is refused as a fork.
• Checkpoint records never count against a quota.