Registry · Capabilities · openrouter.ai

Capability registry

What openrouter.ai declares an agent can do

Measured 2026-10-04 05:02 UTC from the declarations the site publishes (record xhx3i158o2). Each capability is shown as declared, under the policy class that decides whether anything may call it, beside what a call observed.

Declared versus observed

Where the declaration and the call disagree

None: every capability that was called answered as declared.

Signed certificate

This page’s rows, signed by the observer’s Ed25519 key: every capability’s id, endpoint, safety class, policy class and observed state, the declaration hashes and the record’s sealed manifest. The certificate is derived from the record alone, so the same record always yields the same id.

The certificate as JSON · verify it now · the key directory · machine-readability certificate

To verify it yourself: SHA-256 the certificate object as canonical JSON (keys sorted, no whitespace); the hex digest must equal certificate_sha256 and the id; then check the Ed25519 signature over "crawlcheck-capability-certificate-v1\n" followed by that hex digest, with the key in the directory whose RFC 7638 thumbprint is the kid.

Policy classes