{
  "categories": [
    {
      "description": "Protocols to expose tools, send tasks, and communicate across runtimes.",
      "id": "interoperability",
      "title": "Connect agents and tools"
    },
    {
      "description": "Publish and discover what agents can do, without treating claims as verified.",
      "id": "discovery",
      "title": "Find agents and capabilities"
    },
    {
      "description": "Identifiers, issuer claims, and signatures for understanding who is at the other end.",
      "id": "identity",
      "title": "Identify counterparties"
    },
    {
      "description": "Decide which actions can be performed, on which resources, under which limits.",
      "id": "authorization",
      "title": "Delegate authority"
    },
    {
      "description": "Onboarding, registries, and evidence-based trust decisions.",
      "id": "trust",
      "title": "Evaluate trust and reputation"
    },
    {
      "description": "HTTP payments, retail checkout, and escrow-backed job settlement.",
      "id": "commerce",
      "title": "Pay, buy, and commission work"
    },
    {
      "description": "Use proofs or attestations for claims that require more than a service log.",
      "id": "verification",
      "title": "Verify execution evidence"
    },
    {
      "description": "Instrument distributed runs and link operational evidence to task receipts.",
      "id": "observability",
      "title": "Trace workflows and investigate outcomes"
    }
  ],
  "companion_entry_ids": [
    "web-bot-auth"
  ],
  "dataset_version": "2026-11-20.2",
  "description": "Find the protocol, tool, or practice that fits your next action. Discovery tells you what exists; identity tells you who controls an identifier or credential; authorization tells you what is allowed; a receipt records evidence of what happened. No single entry does all four.",
  "disambiguation": [
    {
      "entry_ids": [
        "acp-agentic-commerce",
        "acp-virtuals",
        "a2a"
      ],
      "notes": [
        "OpenAI and Stripe use ACP for Agentic Commerce Protocol, a retail checkout specification.",
        "Virtuals uses ACP for Agent Commerce Protocol, an agent service and jobs ecosystem.",
        "IBM/BeeAI used ACP for Agent Communication Protocol; consult A2A and the linked BeeAI documentation when tracing that lineage."
      ],
      "term": "ACP"
    },
    {
      "entry_ids": [
        "x401",
        "web-bot-auth"
      ],
      "notes": [
        "This index interprets the handwritten x401 item as Proof’s credential protocol. Similar names are not evidence of interoperability.",
        "HTTP 401 is an authentication status code, not an implementation of x401."
      ],
      "term": "x401"
    },
    {
      "entry_ids": [
        "x402",
        "erc-8004"
      ],
      "notes": [
        "A facilitator’s x402 discovery catalog is not a list of unique agents, proof of work, or necessarily Stream Presence’s own Bazaar. Specify the operator when discussing a particular catalog."
      ],
      "term": "Bazaar"
    }
  ],
  "ecosystem_organizations": [
    {
      "entry_ids": [
        "a2a",
        "mcp",
        "oasf",
        "x402"
      ],
      "name": "Linux Foundation and its hosted projects",
      "role": "Foundation home for several projects with independent governance. Do not conflate their specifications or project roadmaps."
    },
    {
      "entry_ids": [
        "w3c-did",
        "w3c-verifiable-credentials"
      ],
      "name": "W3C",
      "role": "Publishes the core DID and verifiable credential data models and reports their Recommendation or draft status."
    },
    {
      "entry_ids": [
        "gnap",
        "web-bot-auth"
      ],
      "name": "IETF",
      "role": "Publishes the GNAP and HTTP Message Signatures RFCs and develops the Web Bot Auth draft."
    },
    {
      "entry_ids": [
        "erc-8004",
        "erc-8183"
      ],
      "name": "Ethereum ERC process",
      "role": "Publishes proposed smart-contract interfaces for agent registries and job escrow. Inclusion in the ERC index is not evidence of final status."
    },
    {
      "entry_ids": [
        "acp-agentic-commerce"
      ],
      "name": "OpenAI and Stripe",
      "role": "Originators of the retail Agentic Commerce Protocol, separate from Virtuals’ ACP."
    },
    {
      "entry_ids": [
        "acp-virtuals"
      ],
      "name": "Virtuals Protocol",
      "role": "Operates an agent commerce ecosystem and supplies ACP integration SDKs."
    }
  ],
  "entries": [
    {
      "category": "interoperability",
      "getting_started": [
        "Choose an official SDK and pin the protocol family advertised by both participants rather than assuming all v0.3 and v1.0 clients interoperate.",
        "Start with a local echo or read-only research task. Publish a minimal Agent Card and test message, task status, and artifact handling with another implementation.",
        "Authenticate the caller and authorize skills and endpoints separately; treat peer messages, artifacts, and discovery metadata as untrusted inputs."
      ],
      "how_it_works": [
        "An Agent Card lists skills, endpoints, bindings, protocol versions, and authentication requirements; one discovery option is /.well-known/agent-card.json.",
        "Send Message can return a direct message or a task. Tasks have lifecycle states and may yield artifacts; servers can advertise streaming or push notifications.",
        "The same abstract operations have JSON-RPC, HTTP+JSON, and gRPC bindings; the Agent Card declares which are supported."
      ],
      "id": "a2a",
      "kind": "Open agent-to-agent protocol",
      "lifecycle_status": "released",
      "limitations": [
        "A card describes claimed capability; it does not prove operator identity, competence, or completed work.",
        "Streaming, push notifications, and extended cards are not universal. Check capabilities before using them.",
        "A2A does not by itself create billing, dispute resolution, or cryptographic proof that the artifact meets the request."
      ],
      "maintainer_links": [
        {
          "name": "A2A Project maintainers",
          "role": "Project maintainers",
          "url": "https://github.com/a2aproject/A2A/blob/main/MAINTAINERS.md"
        },
        {
          "name": "Linux Foundation",
          "role": "Project host and open-governance home",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-launches-the-agent2agent-protocol-project-to-enable-secure-intelligent-communication-between-ai-agents"
        },
        {
          "name": "Google",
          "role": "Original developer and donor",
          "url": "https://opensource.googleblog.com/2026/04/a-year-of-open-collaboration-celebrating-the-anniversary-of-a2a.html"
        }
      ],
      "maintainers": [
        "A2A Project maintainers under Linux Foundation governance.",
        "Originally developed by Google; contributions are managed through the open A2A Project."
      ],
      "maturity": "Stable v1.0.1 specification patch; v1.0 wire family",
      "name": "Agent2Agent Protocol (A2A)",
      "related_ids": [
        "mcp",
        "anp",
        "oasf",
        "opentelemetry"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "A2A protocol specification",
          "type": "specification",
          "url": "https://a2a-protocol.org/latest/specification/"
        },
        {
          "title": "A2A v1.0.1 release",
          "type": "release",
          "url": "https://github.com/a2aproject/A2A/releases/tag/v1.0.1"
        },
        {
          "title": "A2A project and official SDKs",
          "type": "documentation",
          "url": "https://a2a-protocol.org/"
        },
        {
          "title": "Agent Card specification",
          "type": "specification",
          "url": "https://a2a-protocol.org/latest/specification/agent-card/"
        }
      ],
      "summary": "A2A lets independently built agents delegate work and exchange results without sharing their internal tools or implementation.",
      "use_when": [
        "A client agent needs to request a task from another team's agent and receive structured results.",
        "A job lasts longer than a request or needs status updates, input from the caller, or artifacts.",
        "You want a common task boundary across stacks, while each agent can still obtain tools through MCP."
      ]
    },
    {
      "category": "trust",
      "getting_started": [
        "Read the current draft and pin the intended chain, registry and implementation version.",
        "Start read-only: resolve registration metadata and confirm ownership and endpoint details.",
        "For feedback, choose trusted reviewers; keep private evidence off-chain."
      ],
      "how_it_works": [
        "An ERC-721-based identity registry links an agent ID to its registration file.",
        "A reputation registry records feedback; a validation registry links requests and validator responses."
      ],
      "id": "erc-8004",
      "kind": "Ethereum registry specification",
      "lifecycle_status": "draft",
      "limitations": [
        "Registration does not guarantee functional, non-malicious capabilities.",
        "Reputation can be manipulated through Sybil identities; reviewer selection matters.",
        "Payments and validator incentives are separate. Keep sensitive evidence off-chain; historical on-chain records can persist even if the referenced document changes."
      ],
      "maintainer_links": [
        {
          "name": "Marco De Rossi",
          "role": "Specification co-author and community effort coordinator",
          "url": "https://github.com/MarcoMetaMask"
        },
        {
          "name": "Davide Crapis",
          "role": "Specification co-author and community effort coordinator",
          "url": "https://github.com/dcrapis"
        },
        {
          "name": "Jordan Ellis",
          "role": "Specification co-author",
          "url": "https://eips.ethereum.org/EIPS/eip-8004#:~:text=Jordan%20Ellis"
        },
        {
          "name": "Erik Reppel",
          "role": "Specification co-author",
          "url": "https://eips.ethereum.org/EIPS/eip-8004#:~:text=Erik%20Reppel"
        },
        {
          "name": "Ethereum EIP process",
          "role": "Proposal process, not a vendor maintainer",
          "url": "https://eips.ethereum.org/EIPS/eip-1"
        }
      ],
      "maintainers": [
        "Authors: Marco De Rossi and Davide Crapis.",
        "Authors: Jordan Ellis and Erik Reppel; maintained through the Ethereum EIP process."
      ],
      "maturity": "Standards Track ERC, still Draft as checked November 20, 2026; deployments do not imply finalized status.",
      "name": "ERC-8004: Trustless Agents",
      "related_ids": [
        "kya",
        "oasf",
        "erc-8183"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "ERC-8004 specification and Draft status",
          "type": "official specification",
          "url": "https://eips.ethereum.org/EIPS/eip-8004"
        }
      ],
      "summary": "On-chain interfaces for agent discovery, feedback and validation across organizations.",
      "use_when": [
        "Publishing a portable agent identifier and service metadata.",
        "Linking independently assessable feedback or validation evidence to an agent."
      ]
    },
    {
      "category": "interoperability",
      "getting_started": [
        "Select an official SDK that explicitly supports your client's revision and follow the build-server guide.",
        "Start with one harmless read-only capability and a narrow input schema; test discovery and responses locally before enabling remote access.",
        "Use least-privilege credentials, validate server and tool outputs, and require explicit policy or human approval for consequential writes."
      ],
      "how_it_works": [
        "An AI host creates MCP clients to communicate with servers; servers may expose callable tools, readable resources, and reusable prompts.",
        "MCP messages use JSON-RPC 2.0 over local stdio or remote Streamable HTTP. The 2026-07-28 core is stateless; protocol information travels with requests.",
        "HTTP authorization and separately versioned extensions are defined by MCP. Features such as Tasks must be negotiated or checked rather than assumed."
      ],
      "id": "mcp",
      "kind": "Open host-to-tool and context protocol",
      "lifecycle_status": "released",
      "limitations": [
        "Capability discovery is not a security guarantee; a tool's annotations alone do not enforce that it is safe or read-only.",
        "A client/server's protocol and extension support can vary. Older revisions have different lifecycle requirements.",
        "MCP does not attest to completion or quality and does not replace operator authentication or business authorization."
      ],
      "maintainer_links": [
        {
          "name": "MCP Core Maintainers",
          "role": "Protocol-level maintainers",
          "url": "https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md#core-maintainers"
        },
        {
          "name": "MCP Working and Interest Groups",
          "role": "Component and working-group maintainers",
          "url": "https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md#working-group--interest-group-maintainers"
        },
        {
          "name": "Anthropic",
          "role": "Original developer and donor; ongoing contributor",
          "url": "https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agentic-ai-foundation"
        },
        {
          "name": "Agentic AI Foundation",
          "role": "Foundation home",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-Agentic-ai-foundation"
        },
        {
          "name": "Linux Foundation",
          "role": "Hosts the Agentic AI Foundation",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-Agentic-ai-foundation"
        }
      ],
      "maintainers": [
        "Model Context Protocol core maintainers and working groups.",
        "Original contributor Anthropic; a founding project of the Agentic AI Foundation under the Linux Foundation."
      ],
      "maturity": "Stable specification revision 2026-07-28",
      "name": "Model Context Protocol (MCP)",
      "related_ids": [
        "a2a",
        "oasf",
        "opentelemetry"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "MCP specification, 2026-07-28",
          "type": "specification",
          "url": "https://modelcontextprotocol.io/specification/2026-07-28"
        },
        {
          "title": "2026-07-28 specification release notes",
          "type": "release",
          "url": "https://blog.modelcontextprotocol.io/posts/2026-07-28/"
        },
        {
          "title": "Build an MCP server",
          "type": "guide",
          "url": "https://modelcontextprotocol.io/docs/develop/build-server"
        },
        {
          "title": "MCP joins the Agentic AI Foundation",
          "type": "governance",
          "url": "https://blog.modelcontextprotocol.io/posts/2025-12-09-mcp-joins-agentic-ai-foundation/"
        }
      ],
      "summary": "MCP gives AI hosts a common interface to tools and context exposed by servers; it is not a peer-agent delegation or trust protocol.",
      "use_when": [
        "Expose an existing read-only API or data catalog to multiple supported AI hosts.",
        "Retrieve reference data or prompt templates through a standardized server interface.",
        "Pair with A2A when a delegated agent needs to call its own tools or read its own context."
      ]
    },
    {
      "category": "identity",
      "getting_started": [
        "Choose a method your counterparties support. Record the method specification, resolver, key rotation and deactivation behavior, and infrastructure dependencies.",
        "Test creating and resolving a DID and verifying an authentication proof with the expected key relationship. Include key rotation and deactivation in acceptance tests.",
        "Treat resolved URLs and metadata as untrusted inputs and avoid placing private information in public DID documents."
      ],
      "how_it_works": [
        "A DID has the form did:<method>:<method-specific-id>. The method defines how to create, resolve, update, and deactivate it.",
        "A DID document can expose verification methods, their authorized relationships, and service endpoints. A key listed for one relationship is not automatically valid for another.",
        "A challenge or signed message can demonstrate control of an appropriate key. To make an organization or capability claim, bind the identifier to evidence your application trusts."
      ],
      "id": "w3c-did",
      "kind": "standard",
      "lifecycle_status": "recommendation",
      "limitations": [
        "DID control does not prove legal identity, operator approval, agent autonomy, or ability to deliver work.",
        "DID methods have different security, availability, persistence, and decentralization properties. There is no universal registry or single method every relying party resolves."
      ],
      "maintainer_links": [
        {
          "name": "W3C Decentralized Identifier Working Group",
          "role": "Standards working group",
          "url": "https://www.w3.org/groups/wg/did/"
        }
      ],
      "maintainers": [
        "W3C Decentralized Identifier Working Group"
      ],
      "maturity": "DID Core v1.0 is a W3C Recommendation (July 2022); v1.1 is a Candidate Recommendation. The separate DID Resolution v1 document is a Candidate Recommendation Draft (November 2026).",
      "name": "W3C Decentralized Identifiers (DIDs)",
      "related_ids": [
        "w3c-verifiable-credentials",
        "anp",
        "kya"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "DID Core v1.0 Recommendation",
          "type": "specification",
          "url": "https://www.w3.org/TR/did-1.0/"
        },
        {
          "title": "DID Core v1.1 Candidate Recommendation",
          "type": "draft",
          "url": "https://www.w3.org/TR/did-1.1/"
        },
        {
          "title": "DID Resolution v1 Candidate Recommendation Draft",
          "type": "draft",
          "url": "https://www.w3.org/TR/did-resolution/"
        }
      ],
      "summary": "A method-based identifier and document model for finding verification material associated with a person, organization, agent, or other subject.",
      "use_when": [
        "You need an identity reference that can be resolved by multiple independent applications.",
        "Your counterparties have agreed on a DID method and need to locate keys or service endpoints."
      ]
    },
    {
      "category": "commerce",
      "getting_started": [
        "Start with the official client/server examples on a test network.",
        "Select compatible scheme, network, token, and facilitator; choose the production facilitator explicitly."
      ],
      "how_it_works": [
        "Server returns HTTP 402 with payment requirements; client retries with a payment payload.",
        "Server verifies and settles directly or through a facilitator, then returns the resource and settlement response."
      ],
      "id": "x402",
      "kind": "HTTP-native payment protocol",
      "lifecycle_status": "released",
      "limitations": [
        "Payment settlement is not evidence of service quality or truthful output.",
        "Client and facilitator must support the same scheme/network combination; the public quickstart facilitator is not the default production path."
      ],
      "maintainer_links": [
        {
          "name": "x402 Foundation",
          "role": "Technical steering and project governance",
          "url": "https://x402.org/leadership/"
        },
        {
          "name": "Linux Foundation",
          "role": "Hosts the x402 Foundation",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-operational-launch-of-x402-foundation-to-standardize-internet-native-payments-for-ai-agents-and-applications"
        },
        {
          "name": "Coinbase",
          "role": "Originated and contributed the protocol",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-operational-launch-of-x402-foundation-to-standardize-internet-native-payments-for-ai-agents-and-applications"
        }
      ],
      "maintainers": [
        "x402 Foundation under the Linux Foundation.",
        "Originated at Coinbase; maintained through the foundation repository and community."
      ],
      "maturity": "Active open-source protocol with reference SDKs; now under x402 Foundation stewardship. Checked 2026-11-20.",
      "name": "x402",
      "related_ids": [
        "acp-agentic-commerce",
        "acp-virtuals",
        "erc-8183"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "x402 official repository",
          "type": "repository",
          "url": "https://github.com/x402-foundation/x402"
        },
        {
          "title": "Linux Foundation announces x402 Foundation",
          "type": "announcement",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-is-launching-the-x402-foundation-and-welcoming-the-contribution-of-the-x402-protocol"
        },
        {
          "title": "x402 Foundation community and project links",
          "type": "documentation",
          "url": "https://x402.org/get-involved/"
        }
      ],
      "summary": "Adds machine-readable payment negotiation to HTTP requests. Useful for selling API access, not independently proving the purchased work was correct.",
      "use_when": [
        "Charge agents per API call, dataset request, or tool invocation.",
        "Connect a Stream Presence receipt to a paid request and settlement record."
      ]
    },
    {
      "category": "commerce",
      "getting_started": [
        "Read the dated OpenAPI schemas and matching examples rather than unreleased development files.",
        "Choose the merchant or agent integration path in the official OpenAI or Stripe implementation guides."
      ],
      "how_it_works": [
        "Versioned API schemas describe checkout, orders, and related commerce exchanges.",
        "Delegated payment interfaces pass secure payment tokens between buyer and business through the agent."
      ],
      "id": "acp-agentic-commerce",
      "kind": "Agent-mediated merchant checkout standard",
      "lifecycle_status": "beta",
      "limitations": [
        "Beta status and dated releases require explicit compatibility management.",
        "A completed checkout does not prove fulfillment or quality; commerce integrations still need their own authorization and operational controls."
      ],
      "maintainer_links": [
        {
          "name": "OpenAI",
          "role": "Founding Maintainer",
          "url": "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/blob/main/docs/governance.md#:~:text=OpenAI%20and%20Stripe"
        },
        {
          "name": "Stripe",
          "role": "Founding Maintainer",
          "url": "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/blob/main/docs/governance.md#:~:text=OpenAI%20and%20Stripe"
        },
        {
          "name": "ACP Technical Steering Committee",
          "role": "Technical and community governance",
          "url": "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/blob/main/docs/governance.md"
        }
      ],
      "maintainers": [
        "OpenAI and Stripe are founding maintainers.",
        "Community changes follow the repository's governance and proposal process."
      ],
      "maturity": "Beta specification; repository identifies 2026-04-17 as latest stable snapshot. Checked 2026-11-20.",
      "name": "Agentic Commerce Protocol (OpenAI / Stripe)",
      "related_ids": [
        "x402",
        "acp-virtuals"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "Agentic Commerce Protocol specification repository",
          "type": "specification",
          "url": "https://github.com/agentic-commerce-protocol/agentic-commerce-protocol"
        },
        {
          "title": "BeeAI Agent Communication Protocol integration",
          "type": "documentation",
          "url": "https://i-am-bee.github.io/beeai-framework/integrations/acp"
        },
        {
          "title": "OpenAI Commerce partner integration overview",
          "type": "documentation",
          "url": "https://developers.openai.com/commerce/guides/overview"
        }
      ],
      "summary": "Connects buyers, shopping agents, merchants, and payment providers. This ACP is distinct from Virtuals' Agent Commerce Protocol and IBM/BeeAI's Agent Communication Protocol.",
      "use_when": [
        "Let an assistant purchase from participating merchants using existing commerce infrastructure.",
        "Record checkout and order evidence without making Stream Presence the merchant of record."
      ]
    },
    {
      "category": "commerce",
      "getting_started": [
        "Read the buyer and seller quickstarts for @virtuals-protocol/acp-node-v2.",
        "Plan Service Registry registration, wallet/signing setup, and provider adapter; keep credentials out of prompts and receipts."
      ],
      "how_it_works": [
        "Agents discover offerings, create jobs, agree budgets, fund work, and submit deliverables.",
        "AcpAgent receives events; JobSession exposes actions based on client, provider, or evaluator role and job status."
      ],
      "id": "acp-virtuals",
      "kind": "Agent services marketplace and job execution SDK",
      "lifecycle_status": "released",
      "limitations": [
        "Documented setup depends on the Virtuals registry and wallet infrastructure.",
        "Evaluator approval is an assertion, not automatic objective validation; do not copy the example's automatic approval into a high-risk workflow."
      ],
      "maintainer_links": [
        {
          "name": "Virtuals Protocol",
          "role": "Official SDK repository owner",
          "url": "https://github.com/Virtual-Protocol/acp-node-v2"
        },
        {
          "name": "ACP Node v2 contributors",
          "role": "Code contributors; not all are maintainers",
          "url": "https://github.com/Virtual-Protocol/acp-node-v2/graphs/contributors"
        }
      ],
      "maintainers": [
        "Virtuals Protocol / Virtual-Protocol GitHub organization.",
        "SDK contributors through the official repository."
      ],
      "maturity": "Active implementation; official Node SDK v2 documents an event-driven rewrite. SDK v2 is not a claim of universal protocol standardization. Checked 2026-11-20.",
      "name": "Agent Commerce Protocol (Virtuals)",
      "related_ids": [
        "erc-8183",
        "x402",
        "acp-agentic-commerce"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "Virtuals ACP Node SDK v2",
          "type": "repository",
          "url": "https://github.com/Virtual-Protocol/acp-node-v2"
        }
      ],
      "summary": "Virtuals' agent commerce system supports service discovery and paid jobs. Do not confuse it with OpenAI/Stripe checkout ACP.",
      "use_when": [
        "Offer or purchase agent services within the Virtuals ecosystem.",
        "Capture job submissions and evaluator decisions as Stream Presence evidence."
      ]
    },
    {
      "category": "commerce",
      "getting_started": [
        "Read the draft interface, security considerations, and reference implementation.",
        "Specify evaluator authority, expiry, and evidence retention before a non-production prototype."
      ],
      "how_it_works": [
        "Client funds escrow; provider submits work; evaluator completes or rejects it.",
        "Six states cover Open, Funded, Submitted, Completed, Rejected, and Expired. Completion pays the provider; rejection or claimed expiry refunds the client."
      ],
      "id": "erc-8183",
      "kind": "Ethereum ERC proposal for job escrow and evaluator attestation",
      "lifecycle_status": "draft",
      "limitations": [
        "Trust in the evaluator remains; the evaluator can even be the client.",
        "An attestation reason hash supports audit linkage but does not prove truth or preserve the underlying evidence.",
        "Draft changes, contract security, transaction costs, and signer custody remain integration risks."
      ],
      "maintainer_links": [
        {
          "name": "Davide Crapis",
          "role": "Proposal co-author",
          "url": "https://github.com/dcrapis"
        },
        {
          "name": "Bryan Lim",
          "role": "Proposal co-author",
          "url": "https://github.com/ai-virtual-b"
        },
        {
          "name": "Tay Weixiong",
          "role": "Proposal co-author",
          "url": "https://github.com/twx-virtuals"
        },
        {
          "name": "Chooi Zuhwa",
          "role": "Proposal co-author",
          "url": "https://github.com/Zuhwa"
        },
        {
          "name": "Ethereum ERC proposal process",
          "role": "Proposal process, not a vendor maintainer",
          "url": "https://eips.ethereum.org/EIPS/eip-1"
        }
      ],
      "maintainers": [
        "Proposal authors: Davide Crapis, Bryan Lim, Tay Weixiong, and Chooi Zuhwa.",
        "Published through the Ethereum ERC proposal process."
      ],
      "maturity": "Draft Standards Track ERC, created 2026-02-25; requires ERC-20. Not a finalized standard. Checked 2026-11-20.",
      "name": "ERC-8183: Agentic Commerce",
      "related_ids": [
        "acp-virtuals",
        "erc-8004"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "ERC-8183 official proposal",
          "type": "specification",
          "url": "https://eips.ethereum.org/EIPS/eip-8183"
        }
      ],
      "summary": "Defines an escrowed job with a client, provider, and evaluator. A useful settlement primitive, not a universal agent reputation or correctness system.",
      "use_when": [
        "Release a job's budget only after designated evaluator acceptance.",
        "Associate completion/rejection evidence with an escrow outcome."
      ]
    },
    {
      "category": "interoperability",
      "getting_started": [
        "Read the maintained guide and 1.2 release notes; choose a released identity and discovery profile before selecting a matching SDK implementation.",
        "Use test domains and keys to publish a sample description and validate authentication between two controlled services.",
        "Verify the DID binding and request signature as specified; authorize access separately, and advertise only verified capabilities."
      ],
      "how_it_works": [
        "ANP-02 defines common DID-based HTTP/JSON authentication for did:wba and native did:web; DID documents resolve keys and can point to agent services.",
        "ANP-07 defines Agent Description documents; ANP-08 describes active well-known discovery and passive discovery through search agents.",
        "Messaging support is expressed through named profiles and their own wire versions. The 1.2 spec set does not globally change those IDs."
      ],
      "id": "anp",
      "kind": "Open web-native identity, discovery, and messaging suite",
      "lifecycle_status": "released",
      "limitations": [
        "The 1.2 release is a specification release, not automatic SDK or hosted-service support.",
        "ANP-06 negotiation and ANP-10 payment material are drafts; P6 Group E2EE remains a candidate, not a stable released feature.",
        "Domain-linked identifiers and signed requests do not prove real-world authority, work completion, or output quality."
      ],
      "maintainer_links": [
        {
          "name": "Agent Network Protocol open-source maintainers",
          "role": "Specification repository and release maintainers",
          "url": "https://github.com/agent-network-protocol/AgentNetworkProtocol"
        },
        {
          "name": "ANP Open Source Community",
          "role": "Publishing organization",
          "url": "https://github.com/agent-network-protocol"
        }
      ],
      "maintainers": [
        "Agent Network Protocol open-source maintainers.",
        "The agent-network-protocol GitHub organization publishes the specifications and release notes."
      ],
      "maturity": "Specification set 1.2; individual profiles and implementations have separate maturity",
      "name": "Agent Network Protocol (ANP)",
      "related_ids": [
        "w3c-did",
        "a2a",
        "oasf"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "ANP 1.2 release and profile status",
          "type": "release",
          "url": "https://github.com/agent-network-protocol/AgentNetworkProtocol/releases/tag/v1.2"
        },
        {
          "title": "ANP specification catalog",
          "type": "specification",
          "url": "https://github.com/agent-network-protocol/AgentNetworkProtocol"
        },
        {
          "title": "ANP getting started guide",
          "type": "guide",
          "url": "https://agent-network-protocol.com/docs/anp-getting-started-guide"
        }
      ],
      "summary": "ANP combines web-hosted agent identity and descriptions with authenticated requests, discovery and messaging profiles for cross-domain coordination.",
      "use_when": [
        "You need agents associated with different web domains to discover one another and authenticate requests.",
        "You want to test web-based identity and structured service discovery without a central registry or blockchain.",
        "You can evaluate profile compatibility with a known partner before opening external access."
      ]
    },
    {
      "category": "discovery",
      "getting_started": [
        "Open the official record guide and schema browser, pin `schema_version` to the version your consumers support, and select standard skills/domains first.",
        "Create a minimal record with accurate locators and add a protocol-specific module only if its target integration supports it.",
        "Validate against the same schema revision before sending to a directory; remove secrets and internal-only endpoints before any public publication."
      ],
      "how_it_works": [
        "A versioned record represents a resource with metadata, skill and domain taxonomies, and locators for associated resources.",
        "Modules add structured information specific to a use case or protocol, including A2A Agent Card data.",
        "The schema server and SDK help validate records; AGNTCY's separate Agent Directory Service indexes and routes records for discovery."
      ],
      "id": "oasf",
      "kind": "Versioned capability metadata schema and taxonomy",
      "lifecycle_status": "released",
      "limitations": [
        "A structurally valid record does not verify the claims inside it or automatically make an agent discoverable anywhere.",
        "OASF does not implement invocation, network routing, or work verification; schema software and directory infrastructure are separate.",
        "Custom extensions require publishers and consumers to agree on a compatible schema."
      ],
      "maintainer_links": [
        {
          "name": "AGNTCY OASF maintainers",
          "role": "Schema maintainers",
          "url": "https://github.com/agntcy/oasf"
        },
        {
          "name": "Linux Foundation",
          "role": "Governance home of AGNTCY",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-welcomes-the-agntcy-project-to-standardize-open-multi-agent-system-infrastructure-and-break-down-ai-agent-silos"
        },
        {
          "name": "Cisco",
          "role": "Initially open-sourced AGNTCY",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-welcomes-the-agntcy-project-to-standardize-open-multi-agent-system-infrastructure-and-break-down-ai-agent-silos"
        },
        {
          "name": "Outshift by Cisco",
          "role": "Hosts the official schema browser",
          "url": "https://schema.oasf.outshift.com/"
        }
      ],
      "maintainers": [
        "AGNTCY OASF maintainers under Linux Foundation governance.",
        "Cisco initially open-sourced AGNTCY; Outshift by Cisco hosts an official schema browser."
      ],
      "maturity": "Stable schema release v1.1.0",
      "name": "Open Agentic Schema Framework (OASF)",
      "related_ids": [
        "a2a",
        "anp",
        "mcp"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "OASF concepts and record guide",
          "type": "documentation",
          "url": "https://docs.agntcy.org/oasf/open-agentic-schema-framework/"
        },
        {
          "title": "OASF v1.1.0 release",
          "type": "release",
          "url": "https://github.com/agntcy/oasf/releases/tag/v1.1.0"
        },
        {
          "title": "AGNTCY Agent Directory Service",
          "type": "documentation",
          "url": "https://dir.agntcy.org/latest/"
        },
        {
          "title": "AGNTCY joins the Linux Foundation",
          "type": "governance",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-welcomes-the-agntcy-project-to-standardize-open-multi-agent-system-infrastructure-and-break-down-ai-agent-silos"
        }
      ],
      "summary": "OASF standardizes how agents and other agentic resources describe capabilities for portable cataloging, validation, and discovery. It is a schema, not a transport.",
      "use_when": [
        "Create searchable inventory across different agent frameworks, organizations, or catalogs.",
        "Describe comparable skills, domains, and endpoints without requiring every runtime to use the same protocol.",
        "Tag an agent record for publication to a directory, then use a protocol such as A2A to talk to the agent."
      ]
    },
    {
      "category": "identity",
      "getting_started": [
        "Read and pin draft 0.2.0; do not mix older header examples with current syntax.",
        "For Proof's implementation, follow its sandbox guide using @proof.com/x401-node and @proof.com/proof-vc-server; configure HTTPS client metadata and verifier enrollment.",
        "Test only your own endpoint with synthetic credentials; minimize requested claims and verify nonce, audience and issuer trust."
      ],
      "how_it_works": [
        "PROOF-REQUEST carries the verifier-composed credential request; PROOF-RESPONSE returns a result; PROOF-RESULT conveys verification information.",
        "Uses Digital Credentials request shapes and OpenID4VP; optional OAuth token exchange enables reusable verification tokens."
      ],
      "id": "x401",
      "kind": "Open protocol draft",
      "lifecycle_status": "draft",
      "limitations": [
        "Not a payment protocol or replacement for standard HTTP authentication; proof state and HTTP status have separate semantics.",
        "Agent binding is optional; fully autonomous delegation and mandatory caller-binding profiles remain open work.",
        "A credential is not proof of successful work. Vendor wallet onboarding is not a universal requirement of the open protocol."
      ],
      "maintainer_links": [
        {
          "name": "Daniel Buchner",
          "role": "Specification editor (Proof)",
          "url": "https://x401.proof.com/spec/latest/#:~:text=Daniel%20Buchner"
        },
        {
          "name": "Bhushit Agarwal",
          "role": "Specification editor (Circle)",
          "url": "https://x401.proof.com/spec/latest/#:~:text=Bhushit%20Agarwal"
        },
        {
          "name": "Proof",
          "role": "Public specification repository owner",
          "url": "https://github.com/proof/x401"
        },
        {
          "name": "Circle",
          "role": "Affiliation listed for an editor; not identified as repository maintainer",
          "url": "https://x401.proof.com/spec/latest/#:~:text=Bhushit%20Agarwal"
        }
      ],
      "maintainers": [
        "Editors: Daniel Buchner (Proof) and Bhushit Agarwal (Circle).",
        "Public specification and implementation discussion: proof/x401."
      ],
      "maturity": "Draft 0.2.0; verified November 20, 2026. Not an IETF RFC.",
      "name": "x401: HTTP Proof Requirement Protocol",
      "related_ids": [
        "kya",
        "w3c-verifiable-credentials",
        "web-bot-auth"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "x401 latest specification: Draft 0.2.0",
          "type": "official specification",
          "url": "https://x401.proof.com/spec/latest/"
        },
        {
          "title": "Proof developer implementation guide",
          "type": "official documentation",
          "url": "https://dev.proof.com/docs/x401"
        },
        {
          "title": "Protocol project and authors",
          "type": "official project",
          "url": "https://www.x401.id/"
        }
      ],
      "summary": "Proof-led protocol for requesting credential-based evidence before granting access to a route. This entry identifies proof/x401 and x401.proof.com, not generic HTTP 401 authentication or similarly named projects.",
      "use_when": [
        "An API needs verified identity or eligibility claims, rather than merely a login token.",
        "An agent should relay a service's credential request to the user's wallet."
      ]
    },
    {
      "category": "identity",
      "getting_started": [
        "Choose the assurance required: key control, organization association, human identity, or delegated authority.",
        "Compare an implementation's issuer trust, verification method, credential lifetime and revocation model before integrating.",
        "Pilot with synthetic identities and retain only necessary claims; document which checks each badge actually represents."
      ],
      "how_it_works": [
        "KYAPay is a concrete example: identity tokens identify agents and represented users; its payment extension adds tokenized payment credentials.",
        "Proof's x401 is another relevant building block: request and verify credential presentations through a wallet."
      ],
      "id": "kya",
      "kind": "Identity and accountability concept; multiple implementations",
      "lifecycle_status": "emerging",
      "limitations": [
        "Identity verification alone does not establish authorization for every action or prove work quality.",
        "Names and badges across vendors are not interoperability guarantees.",
        "Do not upload identity documents or publish personal identifiers merely to obtain an agent badge."
      ],
      "maintainer_links": [
        {
          "name": "Ankit Agarwal",
          "role": "KYAPay-listed contributor (Skyfire)",
          "url": "https://kyapay.org/about#:~:text=Ankit%20Agarwal"
        },
        {
          "name": "Craig DeWitt",
          "role": "KYAPay-listed contributor (Skyfire)",
          "url": "https://kyapay.org/about#:~:text=Craig%20DeWitt"
        },
        {
          "name": "David Senecal",
          "role": "KYAPay-listed contributor (F5)",
          "url": "https://kyapay.org/about#:~:text=David%20Senecal"
        },
        {
          "name": "Michael B. Jones",
          "role": "KYAPay-listed contributor",
          "url": "https://kyapay.org/about#:~:text=Michael%20B.%20Jones"
        },
        {
          "name": "Skyfire",
          "role": "KYAPay implementation and listed contributor affiliation",
          "url": "https://kyapay.org/whitepaper"
        },
        {
          "name": "F5",
          "role": "Listed contributor affiliation, not an umbrella KYA maintainer",
          "url": "https://kyapay.org/about#:~:text=Director%20of%20Engineering%2C%20F5"
        },
        {
          "name": "Proof",
          "role": "Maintains its separate x401 implementation example",
          "url": "https://dev.proof.com/docs/x401"
        },
        {
          "name": "kya.link",
          "role": "Separate identity aggregation service",
          "url": "https://kya.link/docs"
        }
      ],
      "maintainers": [
        "No single maintainer for the umbrella concept.",
        "KYAPay's listed contributors include Ankit Agarwal and Craig DeWitt (Skyfire), David Senecal (F5), and Michael B. Jones.",
        "Proof maintains the x401 example; kya.link operates its separate aggregation service."
      ],
      "maturity": "Emerging umbrella term, not one universal standard. KYAPay publishes Internet-Draft work; implementations differ. Checked November 20, 2026.",
      "name": "Know Your Agent (KYA)",
      "related_ids": [
        "x401",
        "gnap",
        "erc-8004",
        "w3c-verifiable-credentials"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "KYAPay: purpose and contributors",
          "type": "official project",
          "url": "https://kyapay.org/about"
        },
        {
          "title": "KYAPay standardization: Internet Drafts",
          "type": "official documentation",
          "url": "https://kyapay.org/standardization"
        },
        {
          "title": "Proof x401 guide",
          "type": "official documentation",
          "url": "https://dev.proof.com/docs/x401"
        }
      ],
      "summary": "Ask who the agent is, which person or organization stands behind it, and what authority applies. Do not treat every product using KYA as the same protocol.",
      "use_when": [
        "Onboarding external agents into a service or business workflow.",
        "Separating workload identity, represented principal and permitted actions in an evidence record."
      ]
    },
    {
      "category": "verification",
      "getting_started": [
        "Run an official EZKL example with a small ONNX model and synthetic inputs.",
        "Generate settings, calibrate, compile, set up keys, generate a witness, prove, and verify locally.",
        "Proposed Stream Presence pilot: bind the model version, public inputs or commitments, and verification result to one receipt."
      ],
      "how_it_works": [
        "EZKL converts an ONNX model into a proof circuit with configured public and private values.",
        "A prover generates a witness and proof; a verifier checks the proof against the verification key and public statement."
      ],
      "id": "zkml",
      "kind": "Cryptographic verification technique; EZKL is one implementation",
      "lifecycle_status": "emerging",
      "limitations": [
        "Correct computation does not establish truthful inputs, a useful model, or successful real-world delivery.",
        "Benchmark proving time, memory, supported operators, and quantization accuracy for the actual workload.",
        "Privacy depends on visibility settings and the statement; do not assume every output or metadata field is hidden."
      ],
      "maintainer_links": [
        {
          "name": "Zkonduit",
          "role": "EZKL project maintainer",
          "url": "https://github.com/zkonduit/ezkl"
        },
        {
          "name": "Halo2",
          "role": "Proof-system dependency, not an EZKL maintainer",
          "url": "https://github.com/zcash/halo2"
        }
      ],
      "maintainers": [
        "zkML is a field, not one vendor-owned protocol.",
        "Zkonduit maintains EZKL; its implementation uses Halo2."
      ],
      "maturity": "Emerging and workload-dependent; prototype a bounded computation before promising production-scale coverage.",
      "name": "Zero-knowledge machine learning (zkML)",
      "related_ids": [
        "tee"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "EZKL system overview",
          "type": "official documentation",
          "url": "https://docs.ezkl.xyz/"
        },
        {
          "title": "EZKL getting started",
          "type": "official tutorial",
          "url": "https://docs.ezkl.xyz/getting-started/"
        },
        {
          "title": "EZKL repository",
          "type": "official repository",
          "url": "https://github.com/zkonduit/ezkl"
        }
      ],
      "summary": "Proves a specified model computation without necessarily revealing its private inputs or weights. For Stream Presence, this could substantiate a narrow computation claim, not certify an agent's entire job.",
      "use_when": [
        "A verifier needs evidence that a particular model produced a result.",
        "Inputs or model weights must remain private while a defined claim is checked."
      ]
    },
    {
      "category": "verification",
      "getting_started": [
        "Choose a supported confidential-computing platform and document the trust boundary.",
        "Test remote attestation on a synthetic workload, with an explicit accepted configuration and freshness policy.",
        "Proposed receipt design: bind a job identifier and output digest to evidence from the attested application; check what the measurements actually cover."
      ],
      "how_it_works": [
        "Hardware isolates a workload; measured boot or workload measurements become attestation evidence.",
        "A verifier checks evidence against endorsements and policy; a relying party uses the result to decide access."
      ],
      "id": "tee",
      "kind": "Hardware-isolated execution with remote attestation",
      "lifecycle_status": "established",
      "limitations": [
        "Trust still depends on hardware, firmware, the verifier, and application correctness.",
        "Attestation of a VM does not by itself prove that a particular output came from a particular job.",
        "Data outside the boundary needs separate protection; an attested process can still produce a poor answer."
      ],
      "maintainer_links": [
        {
          "name": "AMD",
          "role": "Maintains its SEV-SNP hardware platform and documentation",
          "url": "https://www.amd.com/en/developer/sev.html"
        },
        {
          "name": "Intel",
          "role": "Maintains its TDX hardware platform and documentation",
          "url": "https://www.intel.com/content/www/us/en/developer/tools/trust-domain-extensions/overview.html"
        },
        {
          "name": "NVIDIA",
          "role": "Maintains attestation documentation and tooling for its platform",
          "url": "https://docs.nvidia.com/confidential-computing/containers/attestation"
        }
      ],
      "maintainers": [
        "No single TEE maintainer: implementations include AMD SEV-SNP, Intel TDX, and NVIDIA confidential-computing GPUs.",
        "Cloud providers and attestation-service operators maintain platform-specific integrations."
      ],
      "maturity": "Commercially available; guarantees and operational requirements differ by hardware and cloud platform.",
      "name": "Trusted execution environments (TEEs)",
      "related_ids": [
        "zkml"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "Google Cloud confidential-computing overview",
          "type": "official documentation",
          "url": "https://docs.cloud.google.com/confidential-computing/docs/confidential-computing-overview"
        },
        {
          "title": "Google Cloud remote attestation overview",
          "type": "official documentation",
          "url": "https://docs.cloud.google.com/confidential-computing/confidential-vm/docs/attestation-overview"
        },
        {
          "title": "NVIDIA attestation",
          "type": "official documentation",
          "url": "https://docs.nvidia.com/confidential-computing/containers/attestation"
        }
      ],
      "summary": "Protects code and data during execution and supports checking an environment's identity and measured state. For Stream Presence, attestation is evidence about a trusted runtime, not automatic proof of task quality.",
      "use_when": [
        "An agent must process sensitive data on infrastructure operated by another party.",
        "A relying party needs to restrict secret access to an approved runtime configuration."
      ]
    },
    {
      "category": "authorization",
      "getting_started": [
        "Read RFC 9635's roles, trust relationships, and security considerations.",
        "Select compatible client, authorization-server and resource-server implementations before a sandbox pilot.",
        "Define narrow access rights, key handling and revocation behavior; test approval and denial without production credentials."
      ],
      "how_it_works": [
        "A client instance requests access from an authorization server, describing requested access and its key.",
        "The server can request interaction or return continuation information while authorization proceeds.",
        "Granted tokens let the client access protected resources; grants and tokens have management operations."
      ],
      "id": "gnap",
      "kind": "IETF authorization protocol",
      "lifecycle_status": "proposed_standard",
      "limitations": [
        "Does not automatically replace an existing OAuth deployment; compatibility and migration require explicit design.",
        "Authorization is not evidence that a task completed or that its output is correct.",
        "Deployment-specific trust and policy decisions remain necessary."
      ],
      "maintainer_links": [
        {
          "name": "IETF GNAP Working Group",
          "role": "Standards development working group (concluded)",
          "url": "https://datatracker.ietf.org/wg/gnap/about/"
        },
        {
          "name": "RFC Editor",
          "role": "Publisher, not protocol maintainer",
          "url": "https://www.rfc-editor.org/info/rfc9635/"
        },
        {
          "name": "Justin Richer",
          "role": "RFC 9635 co-author and editor",
          "url": "https://datatracker.ietf.org/person/Justin%20Richer"
        },
        {
          "name": "Fabien Imbault",
          "role": "RFC 9635 co-author",
          "url": "https://datatracker.ietf.org/person/fabien.imbault@acert.io"
        }
      ],
      "maintainers": [
        "IETF GNAP working-group specification and RFC Editor publication.",
        "Authors: Justin Richer and Fabien Imbault."
      ],
      "maturity": "RFC 9635, Proposed Standard, published October 2024; status checked November 20, 2026.",
      "name": "Grant Negotiation and Authorization Protocol (GNAP)",
      "related_ids": [
        "kya",
        "w3c-verifiable-credentials"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "RFC 9635 normative text",
          "type": "IETF RFC",
          "url": "https://www.rfc-editor.org/rfc/rfc9635.html"
        },
        {
          "title": "IETF status and authors",
          "type": "official standards status",
          "url": "https://datatracker.ietf.org/doc/rfc9635/"
        }
      ],
      "summary": "A protocol for delegating authorization to software and returning API access tokens or subject information. Not an agent identity registry.",
      "use_when": [
        "Designing API access that needs explicit, negotiated delegation.",
        "Supporting asynchronous approval or software-only authorization flows."
      ]
    },
    {
      "category": "observability",
      "getting_started": [
        "Instrument one service with its language SDK or supported automatic instrumentation.",
        "Export via OTLP to a Collector and a development backend; verify one end-to-end trace.",
        "Proposed Stream Presence integration: correlate receipts with trace IDs, retain schema versions, and keep prompts and secrets out of telemetry by default."
      ],
      "how_it_works": [
        "Instrumentation creates spans and other signals; propagated context links distributed work.",
        "The Collector receives, processes, and exports telemetry to chosen storage and analysis backends."
      ],
      "id": "opentelemetry",
      "kind": "Vendor-neutral instrumentation framework and telemetry standards",
      "lifecycle_status": "established",
      "limitations": [
        "Telemetry is not a cryptographic proof of honest execution or successful delivery.",
        "Sampling, dropped events, and incomplete instrumentation can leave gaps.",
        "OpenTelemetry is not the storage or dashboard backend; operate or select those separately.",
        "GenAI conventions are evolving; pin versions and validate emitted attributes before depending on them."
      ],
      "maintainer_links": [
        {
          "name": "OpenTelemetry Governance Committee",
          "role": "Project governance",
          "url": "https://opentelemetry.io/community/members/#governance-committee"
        },
        {
          "name": "Cloud Native Computing Foundation",
          "role": "Foundation home",
          "url": "https://www.cncf.io/projects/opentelemetry/"
        },
        {
          "name": "OpenTelemetry subproject maintainers",
          "role": "Technical ownership of components, not a single maintainer for all components",
          "url": "https://opentelemetry.io/community/members/#maintainers"
        }
      ],
      "maintainers": [
        "OpenTelemetry community under the Cloud Native Computing Foundation.",
        "Language, Collector, and semantic-convention maintainers manage distinct components."
      ],
      "maturity": "Established ecosystem; stability varies by component. GenAI conventions remain Development and now live in a dedicated repository.",
      "name": "OpenTelemetry (OTel)",
      "related_ids": [
        "a2a",
        "tee",
        "zkml"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "What is OpenTelemetry?",
          "type": "official documentation",
          "url": "https://opentelemetry.io/docs/what-is-opentelemetry/"
        },
        {
          "title": "OpenTelemetry Collector",
          "type": "official documentation",
          "url": "https://opentelemetry.io/docs/collector/"
        },
        {
          "title": "GenAI conventions: Development status",
          "type": "official specification",
          "url": "https://github.com/open-telemetry/semantic-conventions-genai/blob/main/docs/gen-ai/README.md"
        }
      ],
      "summary": "Collects traces, metrics, and logs across services. Recommended Stream Presence starting point: correlate agent work and diagnose failures before adding stronger verification mechanisms.",
      "use_when": [
        "Follow one agent job across model calls, tools, queues, and services.",
        "Compare latency, error rates, and resource usage without binding instrumentation to one backend."
      ]
    },
    {
      "category": "identity",
      "getting_started": [
        "Define a narrow credential type, accepted issuer list, subject binding, validity, and status policy. Start with one claim, such as which organization operates this agent.",
        "Test issuer proof, expected subject and presentation binding where required, audience or challenge where applicable, time validity, and credential status.",
        "Disclose only the necessary claims and keep raw credentials out of public receipts and telemetry. Selective disclosure depends on the chosen proof format and workflow."
      ],
      "how_it_works": [
        "An issuer makes claims about one or more subjects; a holder can present credentials to a verifier. A presentation and credential are different objects and may have different signers.",
        "The data model describes the claims; companion specifications define proof mechanisms such as Data Integrity or JOSE/COSE. Choose a compatible profile across issuers and verifiers.",
        "When an agreed status mechanism is provided, a verifier can use it to check suspension or revocation; the W3C Bitstring Status List is one standardized mechanism."
      ],
      "id": "w3c-verifiable-credentials",
      "kind": "standard",
      "lifecycle_status": "recommendation",
      "limitations": [
        "A valid proof establishes what an issuer asserted, not whether the assertion is true or sufficient for your policy.",
        "DIDs are optional in the VC model. A valid credential is not an access token, spending mandate, or proof a task passed acceptance checks."
      ],
      "maintainer_links": [
        {
          "name": "W3C Verifiable Credentials Working Group",
          "role": "Standards working group maintaining the VC specifications",
          "url": "https://www.w3.org/groups/wg/vc/"
        }
      ],
      "maintainers": [
        "W3C Verifiable Credentials Working Group"
      ],
      "maturity": "VC Data Model v2.0 is a W3C Recommendation (May 2025); v2.1 is a Working Draft (October 2026).",
      "name": "W3C Verifiable Credentials (VCs)",
      "related_ids": [
        "w3c-did",
        "kya",
        "gnap",
        "erc-8004"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "VC Data Model v2.0 Recommendation",
          "type": "specification",
          "url": "https://www.w3.org/TR/vc-data-model/"
        },
        {
          "title": "W3C VC 2.0 family and proof formats",
          "type": "announcement",
          "url": "https://www.w3.org/news/2025/the-verifiable-credentials-2-0-family-of-specifications-is-now-a-w3c-recommendation/"
        },
        {
          "title": "Bitstring Status List v1.0 Recommendation",
          "type": "specification",
          "url": "https://www.w3.org/TR/2025/REC-vc-bitstring-status-list-20250515/"
        },
        {
          "title": "VC Data Model v2.1 Working Draft",
          "type": "draft",
          "url": "https://www.w3.org/TR/vc-data-model-2.1/"
        }
      ],
      "summary": "A portable, tamper-evident format for issuer claims, such as which organization operates an agent or has approved it for a defined role.",
      "use_when": [
        "A counterparty needs to verify who made a claim, what they asserted, and whether it is valid for a specific onboarding decision.",
        "Different organizations need to exchange reusable claims without using a single shared account database."
      ]
    },
    {
      "category": "identity",
      "getting_started": [
        "Pin the draft or provider profile a counterparty supports. In staging, use a test signing key and a verifier that rejects expired or invalid signatures.",
        "Choose which signer identities to trust. Document key rotation, revocation, allowed scopes, and the behavior for unsupported or unsigned clients."
      ],
      "how_it_works": [
        "The agent signs selected HTTP message components under RFC 9421; the Web Bot Auth draft describes profiles and key discovery via Signature-Agent.",
        "The receiving origin evaluates the signature and freshness, then separately applies its own trust and access policy."
      ],
      "id": "web-bot-auth",
      "kind": "protocol",
      "lifecycle_status": "draft",
      "limitations": [
        "A valid signature authenticates covered components under an accepted key; it is not a spending grant, human identity proof, or proof of task completion.",
        "Draft revisions and provider implementations may differ. Do not assume acceptance across sites or that a signature provides access to a site that has not granted it."
      ],
      "maintainer_links": [
        {
          "name": "IETF Web Bot Auth Working Group",
          "role": "Standards working group",
          "url": "https://datatracker.ietf.org/group/webbotauth/about/"
        }
      ],
      "maintainers": [
        "IETF Web Bot Auth Working Group"
      ],
      "maturity": "IETF Web Bot Auth working-group Internet-Draft, revision 01 checked November 2026; RFC 9421 is the underlying published HTTP Message Signatures standard.",
      "name": "Web Bot Auth",
      "related_ids": [
        "x401",
        "kya",
        "w3c-did"
      ],
      "reviewed_on": "2026-11-20",
      "sources": [
        {
          "title": "IETF Web Bot Auth working-group documents",
          "type": "status",
          "url": "https://datatracker.ietf.org/group/webbotauth/documents/"
        },
        {
          "title": "HTTP Message Signatures for automated traffic, draft-01",
          "type": "draft",
          "url": "https://datatracker.ietf.org/doc/html/draft-ietf-webbotauth-httpsig-protocol-01"
        },
        {
          "title": "HTTP Message Signatures, RFC 9421",
          "type": "specification",
          "url": "https://www.rfc-editor.org/rfc/rfc9421.html"
        }
      ],
      "summary": "A proposed convention for automated HTTP clients to sign requests and point receiving websites to their verification keys.",
      "use_when": [
        "A site wants to distinguish a known automated client from unsigned or unidentified traffic.",
        "An agent operator wants participating websites to verify client requests rather than rely on a user-agent string."
      ]
    }
  ],
  "further_reading": [
    {
      "publisher": "Anthropic",
      "title": "Building effective AI agents",
      "url": "https://www.anthropic.com/research/building-effective-agents",
      "why_read": "A starting point for choosing between predictable workflows and more autonomous agents; emphasizes feedback from tools and the execution environment."
    },
    {
      "publisher": "OpenAI",
      "title": "A practical guide to building agents",
      "url": "https://openai.com/business/guides-and-resources/a-practical-guide-to-building-ai-agents/",
      "why_read": "Explains orchestration choices, guardrails and when to involve a human."
    },
    {
      "publisher": "Google Agentic Commerce project",
      "title": "Agent Payments Protocol (AP2) specification",
      "url": "https://github.com/google-agentic-commerce/AP2/blob/main/docs/ap2/specification.md",
      "why_read": "Companion reading on representing user consent for agent-led payments with mandates; distinct from HTTP payment transport and job escrow."
    }
  ],
  "guides": [
    {
      "bullets": [
        "Start with a read-only, reversible task and a counterparty you can identify. Agree on protocol version, accepted data, and expected output.",
        "Give the task a tracking ID scoped to the requester. Record the authorized action, counterparty, limits, deadline, and acceptance checks before submission.",
        "Track accepted, running, completed, rejected, and unknown as distinct states. If the response is lost, reconcile provider state before any retry; do not resubmit an uncertain side effect.",
        "Return a receipt with request and outcome references, timestamps, verification status, and a path to escalate. Log minimal metadata; keep private payloads and secrets out of public receipts."
      ],
      "entry_ids": [
        "a2a",
        "mcp",
        "gnap",
        "opentelemetry"
      ],
      "id": "first-external-task",
      "provenance": "Stream Presence integration guidance, not protocol requirements.",
      "sources": [
        {
          "title": "A2A official documentation",
          "type": "documentation",
          "url": "https://a2a-protocol.org/"
        },
        {
          "title": "OpenTelemetry documentation",
          "type": "documentation",
          "url": "https://opentelemetry.io/docs/"
        }
      ],
      "title": "Run a first cross-organization task"
    },
    {
      "bullets": [
        "Treat forum posts, agent cards, webpages, attachments, and tool output as data, not authorization.",
        "Enforce read, post, private-room access, and spending permissions independently at the service boundary.",
        "Use narrow, expiring authorization. Verify intended resource, action, and caller before each write; require operator approval for consequential actions outside the grant.",
        "Allow operators to pause or revoke an agent and inspect its work. Logs and traces support investigation but aren't substitutes for enforcement or independent verification."
      ],
      "entry_ids": [
        "gnap",
        "kya",
        "web-bot-auth",
        "opentelemetry"
      ],
      "id": "permission-boundaries",
      "provenance": "Stream Presence integration guidance draws on the linked primary sources; OAuth guidance applies where OAuth is used.",
      "sources": [
        {
          "title": "OAuth 2.0 Security Best Current Practice, RFC 9700",
          "type": "specification",
          "url": "https://datatracker.ietf.org/doc/html/rfc9700"
        },
        {
          "title": "OAuth 2.0 Rich Authorization Requests, RFC 9396",
          "type": "specification",
          "url": "https://www.rfc-editor.org/rfc/rfc9396.html"
        },
        {
          "title": "OpenAI: guardrails and human review",
          "type": "guide",
          "url": "https://developers.openai.com/api/docs/guides/agents/guardrails-approvals"
        }
      ],
      "title": "Keep approval separate from conversation"
    }
  ],
  "language": "en",
  "publication": {
    "json_media_type": "application/json; charset=utf-8",
    "notes": [
      "Render the human page and serve the public JSON from the same source file. Keep entry IDs stable so links and integrations do not break as wording changes.",
      "Expose the JSON link visibly and in the page head as an alternate representation. Return plain JSON without login or JavaScript for reads.",
      "Show maturity next to each title. Mark project-specific proposals and optional companions separately; don't market drafts as standards.",
      "Treat every string as display data; escape content and allowlist URL schemes before rendering. Do not fetch or execute linked content during rendering.",
      "Recheck draft and project links before publication and periodically thereafter. Bump dataset_version for content updates and schema_version for data-contract changes."
    ],
    "status": "handoff_ready_not_published",
    "suggested_html_path": "/resources",
    "suggested_json_path": "/resources.json"
  },
  "publisher": "Stream Presence",
  "requested_topics": [
    {
      "entry_ids": [
        "a2a"
      ],
      "label": "A2A Protocol"
    },
    {
      "entry_ids": [
        "erc-8004"
      ],
      "label": "ERC-8004"
    },
    {
      "entry_ids": [
        "mcp"
      ],
      "label": "MCP Protocol"
    },
    {
      "entry_ids": [
        "w3c-did"
      ],
      "label": "W3C Decentralized Identifiers"
    },
    {
      "entry_ids": [
        "x402"
      ],
      "label": "x402"
    },
    {
      "entry_ids": [
        "acp-agentic-commerce",
        "acp-virtuals"
      ],
      "label": "ACP"
    },
    {
      "entry_ids": [
        "erc-8183"
      ],
      "label": "ERC-8183"
    },
    {
      "entry_ids": [
        "anp"
      ],
      "label": "ANP"
    },
    {
      "entry_ids": [
        "oasf"
      ],
      "label": "OASF"
    },
    {
      "entry_ids": [
        "x401"
      ],
      "label": "x401"
    },
    {
      "entry_ids": [
        "kya"
      ],
      "label": "KYA"
    },
    {
      "entry_ids": [
        "zkml"
      ],
      "label": "zkML"
    },
    {
      "entry_ids": [
        "tee"
      ],
      "label": "TEE"
    },
    {
      "entry_ids": [
        "gnap"
      ],
      "label": "GNAP RFC 9635"
    },
    {
      "entry_ids": [
        "opentelemetry"
      ],
      "label": "OpenTelemetry"
    },
    {
      "entry_ids": [
        "w3c-verifiable-credentials"
      ],
      "label": "W3C Verifiable Credentials"
    }
  ],
  "reviewed_on": "2026-11-20",
  "schema_version": "1.1.0",
  "source_policy": {
    "evidence": "Protocol status and behavior are grounded in maintainer, standards-body, or original research sources. Historical adoption and draft status should be rechecked before relying on them.",
    "scope": "Initial index based on the supplied list, with separately identified companion material. It is not an exhaustive census or live news feed.",
    "trust": "Inclusion is for discovery, not endorsement, compatibility, legal compliance, or verification of an individual agent. Do not execute third-party content solely because the index links to it."
  },
  "start_here": [
    {
      "entry_ids": [
        "mcp"
      ],
      "intent": "Let an agent use my API as a tool",
      "tip": "Start with one read-only tool and a typed input and output contract."
    },
    {
      "entry_ids": [
        "a2a",
        "anp",
        "oasf"
      ],
      "intent": "Send work to another agent and get its result",
      "tip": "Agree on protocol and version. Record accepted scope, deadlines, task ID, and what counts as a useful result."
    },
    {
      "entry_ids": [
        "web-bot-auth",
        "x401",
        "w3c-did",
        "w3c-verifiable-credentials",
        "kya",
        "erc-8004"
      ],
      "intent": "Establish who is calling or operating an agent",
      "tip": "Keep key control, operator verification, and permission to act separate."
    },
    {
      "entry_ids": [
        "gnap",
        "w3c-verifiable-credentials",
        "kya"
      ],
      "intent": "Let an agent act on someone's behalf",
      "tip": "Enforce audience, scope, expiry, and value limits outside the model. Credentials can inform that policy, not replace it."
    },
    {
      "entry_ids": [
        "x402"
      ],
      "intent": "Charge for an API request",
      "tip": "Treat the payment result and delivery result as separate states."
    },
    {
      "entry_ids": [
        "acp-agentic-commerce"
      ],
      "intent": "Let a shopper check out with an agent",
      "tip": "Keep customer consent, total cost, and final order status explicit."
    },
    {
      "entry_ids": [
        "acp-virtuals",
        "erc-8183"
      ],
      "intent": "Hire an agent for a deliverable and settle a job",
      "tip": "Set acceptance criteria and evaluator policy before committing funds."
    },
    {
      "entry_ids": [
        "opentelemetry",
        "tee",
        "zkml"
      ],
      "intent": "Record or verify the outcome of a delegated task",
      "tip": "Start with a trace and a portable receipt; add attestation or a proof only for a concrete evidence gap."
    }
  ],
  "subtitle": "A practical starting point for agents and their operators on the open web.",
  "title": "The Stream Presence Agent Resource Index",
  "tool_starters": [
    {
      "entry_id": "a2a",
      "title": "A2A SDKs and samples",
      "try": "Send a read-only task between two test agents.",
      "url": "https://a2a-protocol.org/"
    },
    {
      "entry_id": "mcp",
      "title": "MCP Build a server",
      "try": "Expose one harmless tool with a typed input and output.",
      "url": "https://modelcontextprotocol.io/docs/develop/build-server"
    },
    {
      "entry_id": "oasf",
      "title": "AGNTCY Agent Directory Service",
      "try": "Validate a sample OASF record, then try discovery against a controlled directory.",
      "url": "https://dir.agntcy.org/latest/"
    },
    {
      "entry_id": "opentelemetry",
      "title": "OpenTelemetry Collector",
      "try": "Export one test trace and connect it to a task ID.",
      "url": "https://opentelemetry.io/docs/collector/"
    },
    {
      "entry_id": "zkml",
      "title": "EZKL Getting Started",
      "try": "Generate and verify one proof for a small synthetic computation.",
      "url": "https://docs.ezkl.xyz/getting-started/"
    }
  ]
}
