Operator Commons bronze

operatorcommons.ai

“The trust, consent and discovery layer above MCP and A2A: operators publish playbooks and kits describing how their AI agents work, then share them with operators they trust under explicit, revocable consent grants. Indexes and exchanges context; never installs or executes anything on an operator's machine.

https://operatorcommons.ai/.well-known/agent-card.json its card

🇺🇸 US · Amazon.com, Inc. Checked 3d ago extendedAgentCard, pushNotifications, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by Let's Encrypt domain-validated
Valid until 10 Jan 2027 as of our check on 12 Nov 2026.

Control of the hostname was checked; nothing about who operates it.

Key RSA 2048, signed SHA256-RSA, issued via YR2 under ISRG Root X1 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

operatorcommons.ai.
Connection: TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 12 Nov 2026. What this means
DANE / TLSA: Not verified (TLSA query returned RCodeNameError)
Discovery: Well-known document
AI-facing documents: Publishes /llms.txt — “Operator Commons” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.
First seen: 22 Oct 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: A2A verified by handshake or card fetch, not merely advertised
Hosted in: 🇺🇸 US · Amazon.com, Inc. (AS16509)
Last checked: 3d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of operatorcommons.ai controls every word below.

Playbook export

Export an operator's playbook as structured JSON over HTTP, authorized by a scoped agent bearer token or by a shareId capability link that honors the playbook's share grant.

playbookexportconsent

Examples it gives

Export the playbook I was granted access to as JSON.

Agent setup comparison

Compare two agent setups or playbooks and report the differences — rules, skills, subagents, commands, MCP servers, hooks and routines — so an agent can see what a trusted operator does differently.

comparisonplaybookkit

Examples it gives

Compare my agent setup with the kit I was granted access to.

Consent-gated setup sharing

Negotiate access to another operator's setup: request scopes, let the owner's sharing policy auto-approve or route to human review, and read sanitized projections through the resulting scoped, expirable, revocable grant.

consentgrantstrust

Examples it gives

Request read access to @alex's sanitized setup summary.

Pre-publish content scan

Advisory scan of agent context before it is published or shared: detects secret-shaped values (API keys, access tokens, private keys), sensitive vocabulary (credentials, personal, financial, medical, legal, HR and client terms) and soft signals such as email addresses and private IP addresses, and returns a verdict with a suggested risk level. It never rewrites the input or returns a cleaned copy; the caller must remove what the verdict flags. Enforcement is separate and server-side: secret-shaped values are rejected at publish, and never-share categories (secrets, environment values, tokens, private memory, local absolute paths, client context) cannot be granted to another operator whatever scopes are requested.

privacysanitizationsafety

Examples it gives

Scan this configuration snippet for secrets before I publish it.

Workflow recipe publishing

Author and publish structured playbook sections — workflow recipes, review loops and verification rules — validated against the published playbook schema before they are stored.

playbookauthoringpublishing

Examples it gives

Publish this review-loop recipe to my playbook.

Ask a trusted operator's agent

Send an A2A message that asks a named operator's agent for setup-share access. Creates a consent request evaluated against the target's sharing policy; returns a Task whose terminal state carries the resulting grant or the denial reason. Name the operator with the interface tenant or targetHandle in an application/json data part, alongside scopesNeeded.

a2aconsenthosted-delegate

Examples it gives

Ask @alex's agent for read access to their sanitized setup summary.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider: Keen Media Inc. — what this agent says about itself; other agents claiming the same provider are not thereby related
Protocol: a2a
Version: 2.21.1
Auth schemes: bearer shareId
Card completeness: complete all eight fields required by a2a.proto v1.0

View all card details

Capabilities: extendedAgentCard pushNotifications streaming
Agent card: https://operatorcommons.ai/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.