Capability registry

What speakeasy.com declares an agent can do

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

3declared

0public read-only

0called and verified

0declared ≠ observed

mcpprotocols

Unknown 3

Declared versus observed

Capability	Policy class	Declared	Observed
search_docs mcp	Unknown never called automatically	its effect is not stated in the declaration auth: unknown	not attempted classed unknown: only read-only public actions are ever called
get_doc mcp	Unknown never called automatically	its effect is not stated in the declaration auth: unknown	not attempted classed unknown: only read-only public actions are ever called
give_feedback mcp	Unknown never called automatically	its effect is not stated in the declaration auth: unknown	not attempted classed unknown: only read-only public actions are ever called

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.

certificate_id ccap1:8d08e4b81f1ef48c1caa4e85fa8d485d8f0ccc91040a8b4a5559341a20343c24
alg Ed25519 · kid hcIAczGf-8EFBnkunmZlvFWnD2nHHeHeC9cM4BTiBVo
sig DOEUtQxBvVxKFE332seraRxbQGEr_3wyiCzmOxVaqGWwYh2Ru_9ciRsA0MxZP6f_4FLTbU0w8es3Z_UkxP8jBQ

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

Policy class	Called automatically?	Rule
Public read-only public_read_only	yes, to verify	May be called without credentials. CrawlCheck calls it only to check the declaration: GET with no input, on the scanned origin.
Authenticated read-only authenticated_read_only	never	Never called by CrawlCheck. An agent needs the user's own credentials and consent.
Reversible write reversible_write	never	Never invoked automatically. Needs the owner's written authorisation and a test account.
Irreversible write irreversible_write	never	Never invoked automatically. Deletes or changes something that cannot be undone.
Financial financial	never	Never invoked automatically. Moves money or creates a charge.
External communication external_communication	never	Never invoked automatically. Sends a message, email or notification to someone.
Identity and accounts identity	never	Never invoked automatically. Creates, signs in to or changes an account or credential.
Unknown unknown	never	Never invoked. Its effect cannot be read from the declaration, so it is treated as the riskiest case.
Metadata metadata	never	Nothing to invoke: a listing, a server card or a skill file, not an operation.