{
  "companion_to": "2026-11-20.2",
  "dataset_version": "2026-11-20-tools.2",
  "entries": [
    {
      "category": "frameworks",
      "getting_started": [
        "Build a single read-only agent with the language-specific quickstart.",
        "Add a deterministic validation step and evaluate against a small fixture set before composing more agents."
      ],
      "how_it_works": [
        "Combine LLM agents with tools and deterministic nodes so routing or validation can stay in application code.",
        "Compose multi-step workflows using templated patterns or the newer graph-based workflow APIs."
      ],
      "id": "google-adk",
      "limitations": [
        "Workflow and feature availability differs across language bindings and versions; verify feature parity before porting."
      ],
      "maintainer_links": [
        {
          "name": "Google",
          "role": "Project maintainer",
          "url": "https://github.com/google/adk-python"
        },
        {
          "name": "Open-source contributors",
          "role": "Project contributors",
          "url": "https://github.com/google/adk-python"
        }
      ],
      "maintainers": [
        "Google",
        "Open-source contributors"
      ],
      "maturity": "Active open-source toolkit; 2.0 workflow APIs are documented alongside earlier workflow patterns.",
      "name": "Google Agent Development Kit (ADK)",
      "sources": [
        {
          "title": "Agent Development Kit (ADK)",
          "type": "documentation",
          "url": "https://adk.dev/"
        },
        {
          "title": "Workflows: multi-agent, multi-node applications",
          "type": "documentation",
          "url": "https://adk.dev/workflows/"
        }
      ],
      "summary": "Google’s code-first toolkit for building, evaluating and deploying agent applications; fits Gemini teams without requiring every workflow step to be a model call.",
      "use_when": [
        "Choose it when Gemini or Google Cloud already anchors the project.",
        "Use it when a predictable sequence needs one or two judgment-heavy steps."
      ]
    },
    {
      "category": "frameworks",
      "getting_started": [
        "Build a small graph with a single branch and inspect state after each step.",
        "Test stop/resume with a checkpointer and validate how repeated actions are handled."
      ],
      "how_it_works": [
        "Model workflow state and transitions in a graph, then run model calls, tools and ordinary functions as nodes.",
        "Use a checkpointer to save state by thread, enabling resumption and human approval pauses."
      ],
      "id": "langgraph",
      "limitations": [
        "A checkpoint does not make external side effects idempotent; the application still owns that behavior."
      ],
      "maintainer_links": [
        {
          "name": "LangChain",
          "role": "Project maintainer",
          "url": "https://github.com/langchain-ai/langgraph"
        },
        {
          "name": "Open-source contributors",
          "role": "Project contributors",
          "url": "https://github.com/langchain-ai/langgraph"
        }
      ],
      "maintainers": [
        "LangChain",
        "Open-source contributors"
      ],
      "maturity": "Active open-source orchestration runtime with documented persistence and human-in-the-loop support.",
      "name": "LangGraph",
      "sources": [
        {
          "title": "LangGraph overview",
          "type": "documentation",
          "url": "https://docs.langchain.com/oss/python/langgraph/overview"
        },
        {
          "title": "Persistence",
          "type": "documentation",
          "url": "https://docs.langchain.com/oss/python/langgraph/persistence"
        }
      ],
      "summary": "Low-level orchestration runtime for building stateful workflows that can be resumed, inspected and interrupted. It makes you define the control flow rather than handing you a preconfigured assistant.",
      "use_when": [
        "Choose it when retries, branching and human approvals are core to the workflow.",
        "Use it for long-running processes whose state must survive interruptions."
      ]
    },
    {
      "category": "frameworks",
      "getting_started": [
        "Create a small Flow and run one short Crew with fixed inputs.",
        "Capture failure cases and compare quality and cost against a single-agent baseline."
      ],
      "how_it_works": [
        "Crews group agents around roles and tasks, while Flows handle triggers, routing and shared state.",
        "A Flow can call ordinary Python functions, a single agent, or an entire Crew and route subsequent work based on its result."
      ],
      "id": "crewai",
      "limitations": [
        "Adding roles can increase model calls and cost without improving results; role separation does not itself validate the output."
      ],
      "maintainer_links": [
        {
          "name": "CrewAI, Inc.",
          "role": "Project maintainer",
          "url": "https://github.com/crewAIInc/crewAI"
        },
        {
          "name": "Open-source contributors",
          "role": "Project contributors",
          "url": "https://github.com/crewAIInc/crewAI"
        }
      ],
      "maintainers": [
        "CrewAI, Inc.",
        "Open-source contributors"
      ],
      "maturity": "Active open-source framework; official docs verified on the v1.15.44 branch.",
      "name": "CrewAI",
      "sources": [
        {
          "title": "Introduction",
          "type": "documentation",
          "url": "https://docs.crewai.com/v1.15.44/en/introduction"
        },
        {
          "title": "Flows",
          "type": "documentation",
          "url": "https://docs.crewai.com/v1.15.44/en/concepts/flows"
        }
      ],
      "summary": "Python framework that separates role-based collaboration inside a Crew from event-driven application control in a Flow.",
      "use_when": [
        "Choose it when the task naturally divides into roles such as researcher, drafter and reviewer.",
        "Use a Flow when human review or deterministic checks should control when the crew runs."
      ]
    },
    {
      "category": "frameworks",
      "getting_started": [
        "Start with the AskAgent sample and one small public dataset.",
        "Evaluate query results against the source records before connecting the endpoint to a wider audience."
      ],
      "how_it_works": [
        "Ingest structured site data using formats such as Schema.org and RSS, then retrieve relevant results for natural-language queries.",
        "Serve the same site data through a natural-language interface and an MCP ask endpoint, with structured Schema.org responses."
      ],
      "id": "nlweb",
      "limitations": [
        "Answer coverage depends on the content and retrieval configuration. The repository describes A2A as forthcoming, not shipped."
      ],
      "maintainer_links": [
        {
          "name": "NLWeb project contributors",
          "role": "Reference implementation contributors",
          "url": "https://github.com/nlweb-ai/NLWeb"
        },
        {
          "name": "Microsoft",
          "role": "Project originator",
          "url": "https://news.microsoft.com/source/features/company-news/introducing-nlweb-bringing-conversational-interfaces-directly-to-the-web/"
        }
      ],
      "maintainers": [
        "NLWeb project contributors",
        "Originated at Microsoft"
      ],
      "maturity": "Open-source Python reference implementation; the original Microsoft repository redirects to nlweb-ai/NLWeb.",
      "name": "NLWeb (originated at Microsoft)",
      "sources": [
        {
          "title": "nlweb-ai/NLWeb",
          "type": "repository",
          "url": "https://github.com/nlweb-ai/NLWeb"
        },
        {
          "title": "Introducing NLWeb: Bringing conversational interfaces directly to the web",
          "type": "announcement",
          "url": "https://news.microsoft.com/source/features/company-news/introducing-nlweb-bringing-conversational-interfaces-directly-to-the-web/"
        }
      ],
      "summary": "Reference implementation and protocol for asking questions of a website’s structured content. It is a publishing and retrieval layer, not an agent orchestration SDK.",
      "use_when": [
        "Choose it when an existing catalog, venue directory or events feed should become queryable by agents.",
        "Use it when a public website needs a conversational search surface without turning it into a general-purpose agent."
      ]
    },
    {
      "category": "frameworks",
      "getting_started": [
        "Run the core SDK quickstart with one non-mutating tool and a configured model provider.",
        "Set explicit turn limits and trace key tool decisions before adding another provider or agent."
      ],
      "how_it_works": [
        "Define model, instructions and typed tools; the model proposes tool calls, and the SDK executes permitted tools and returns results to the model.",
        "Compose the loop with session state, lifecycle hooks, run budgets, and tracing instead of assembling those elements from scratch."
      ],
      "id": "strands-agents",
      "limitations": [
        "The SDK runs in your process, not a hosted control plane; application operators own deployment, credentials and durable storage choices."
      ],
      "maintainer_links": [
        {
          "name": "Strands Agents maintainers",
          "role": "Project maintainers and governance",
          "url": "https://github.com/strands-agents/harness-sdk/tree/main/team"
        },
        {
          "name": "Open-source contributors",
          "role": "Project contributors",
          "url": "https://github.com/strands-agents/harness-sdk"
        },
        {
          "name": "Amazon Web Services",
          "role": "Project originator",
          "url": "https://aws.amazon.com/blogs/opensource/introducing-strands-agents-an-open-source-ai-agents-sdk/"
        }
      ],
      "maintainers": [
        "Strands Agents maintainers and contributors",
        "Originated at Amazon Web Services"
      ],
      "maturity": "Active open-source SDK; the former Python repository now redirects to the Strands monorepo, which includes Python and TypeScript SDKs.",
      "name": "AWS Strands Agents SDK",
      "sources": [
        {
          "title": "Strands Agents",
          "type": "repository",
          "url": "https://github.com/strands-agents/harness-sdk"
        },
        {
          "title": "Introducing Strands Agents, an Open Source AI Agents SDK",
          "type": "announcement",
          "url": "https://aws.amazon.com/blogs/opensource/introducing-strands-agents-an-open-source-ai-agents-sdk/"
        }
      ],
      "summary": "AWS-originated open-source Python and TypeScript SDK for running a configurable, model-driven agent loop inside your own app.",
      "use_when": [
        "Choose it when you want control over the runtime and tool loop but don’t want to implement the loop yourself.",
        "Use it when Amazon Bedrock is convenient now but you want to keep another supported provider as an option."
      ]
    },
    {
      "category": "frameworks",
      "getting_started": [
        "Install from the official guide and choose a supported provider.",
        "Start with a read-only extension and a small sample workspace; review what the provider and tools can see."
      ],
      "how_it_works": [
        "Run an interactive assistant from the desktop or CLI with a configured model provider.",
        "Extend it with MCP tools; turn repeatable tasks into recipes rather than rebuilding the assistant loop."
      ],
      "id": "goose",
      "limitations": [
        "A locally installed interface does not imply local inference or isolated tools; permissions and data exposure depend on configuration."
      ],
      "maintainer_links": [
        {
          "name": "goose project maintainers",
          "role": "Project maintainers",
          "url": "https://github.com/aaif-goose/goose"
        },
        {
          "name": "Open-source contributors",
          "role": "Project contributors",
          "url": "https://github.com/aaif-goose/goose"
        },
        {
          "name": "Block",
          "role": "Original developer and project donor",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-Agentic-ai-foundation"
        },
        {
          "name": "Agentic AI Foundation",
          "role": "Project host",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-Agentic-ai-foundation"
        },
        {
          "name": "Linux Foundation",
          "role": "Host of the Agentic AI Foundation",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-Agentic-ai-foundation"
        }
      ],
      "maintainers": [
        "goose project maintainers and contributors",
        "Originally developed by Block; hosted by the Agentic AI Foundation"
      ],
      "maturity": "Active open-source project hosted by the Agentic AI Foundation at the Linux Foundation, with desktop and CLI distributions.",
      "name": "goose (Agentic AI Foundation)",
      "sources": [
        {
          "title": "aaif-goose/goose",
          "type": "repository",
          "url": "https://github.com/aaif-goose/goose"
        },
        {
          "title": "Install goose",
          "type": "documentation",
          "url": "https://goose-docs.ai/docs/getting-started/installation/"
        }
      ],
      "summary": "An installable desktop and command-line assistant with pluggable model providers and extensions. More ready to use than a lower-level SDK.",
      "use_when": [
        "Choose it when someone needs a usable assistant on a workstation rather than a new agent service.",
        "Use it to try low-risk, repeatable tasks across approved model and tool configurations."
      ]
    },
    {
      "category": "frameworks",
      "getting_started": [
        "Start with the Python or TypeScript quickstart and one read-only lookup tool.",
        "Add one testable handoff and review its traces; configure sensitive-data capture before using real records."
      ],
      "how_it_works": [
        "Define an agent with instructions and tools, then use a runner to step through tool calls and return the final response.",
        "Use handoffs to transfer control to specialized agents and traces to inspect model calls, tool calls and other run events."
      ],
      "id": "openai-agents-sdk",
      "limitations": [
        "Tracing is observability, not independently verified proof; sensitive inputs and outputs need explicit handling."
      ],
      "maintainer_links": [
        {
          "name": "OpenAI",
          "role": "SDK maintainer",
          "url": "https://developers.openai.com/blog/skills-agents-sdk"
        },
        {
          "name": "Open-source contributors",
          "role": "Project contributors",
          "url": "https://github.com/openai/openai-agents-python"
        }
      ],
      "maintainers": [
        "OpenAI",
        "Open-source contributors"
      ],
      "maturity": "Active open-source Python and TypeScript SDKs with official quickstarts.",
      "name": "OpenAI Agents SDK",
      "sources": [
        {
          "title": "OpenAI Agents SDK",
          "type": "documentation",
          "url": "https://openai.github.io/openai-agents-python/"
        },
        {
          "title": "Quickstart",
          "type": "documentation",
          "url": "https://openai.github.io/openai-agents-python/quickstart/"
        },
        {
          "title": "SDKs and CLI",
          "type": "documentation",
          "url": "https://developers.openai.com/api/docs/libraries"
        }
      ],
      "summary": "OpenAI’s code-first Python and TypeScript libraries for composing agent runs, tools and handoffs. This is distinct from calling a hosted Agents API directly.",
      "use_when": [
        "Choose it when building an OpenAI-centered assistant that needs tool calls and routing without a custom loop.",
        "Use it when you want to inspect why a decision or handoff occurred before adding more specialized agents."
      ]
    },
    {
      "category": "frameworks",
      "getting_started": [
        "Follow the SDK quickstart using approved API authentication and a small sample workspace.",
        "Start with read-only capabilities, define explicit approvals, and run the first sessions with non-sensitive fixtures."
      ],
      "how_it_works": [
        "Runs the Claude Code agent loop and context management via a library interface rather than requiring the application to implement its own tool loop.",
        "Exposes sessions, permissions and hooks, plus optional custom tools, MCP integrations and focused subagents."
      ],
      "id": "claude-agent-sdk",
      "limitations": [
        "It is tied to the Claude Code runtime and Anthropic’s terms; the SDK is not itself a deployment sandbox."
      ],
      "maintainer_links": [
        {
          "name": "Anthropic",
          "role": "SDK maintainer",
          "url": "https://github.com/anthropics/claude-agent-sdk-python"
        }
      ],
      "maintainers": [
        "Anthropic"
      ],
      "maturity": "Active official SDK with documented Python and TypeScript support and separate release changelogs.",
      "name": "Claude Agent SDK",
      "sources": [
        {
          "title": "Agent SDK overview",
          "type": "documentation",
          "url": "https://code.claude.com/docs/en/agent-sdk/overview"
        },
        {
          "title": "anthropics/claude-agent-sdk-python",
          "type": "repository",
          "url": "https://github.com/anthropics/claude-agent-sdk-python"
        }
      ],
      "summary": "Anthropic’s Python and TypeScript SDK for embedding the Claude Code agent loop in an application you operate, unlike the interactive CLI or hosted Managed Agents.",
      "use_when": [
        "Choose it when the intended assistant works with an approved project workspace or document collection.",
        "Use it when you want to reuse Claude Code’s agent behavior while defining project-specific permissions."
      ]
    },
    {
      "category": "frameworks",
      "getting_started": [
        "Use the official TypeScript starter and pin compatible Mastra packages. Start with one schema-validated read-only tool and a two-step workflow.",
        "Run the workflow in local Studio, then test rejection, missing-data, and timeout cases before enabling any writes."
      ],
      "how_it_works": [
        "Agents combine instructions, a selected model, and schema-defined tools; tools and agents can be invoked inside workflow steps.",
        "Workflows chain typed steps with control flow for branches and parallel work; suspend-and-resume supports human input. Studio exposes local runs for testing."
      ],
      "id": "mastra",
      "limitations": [
        "Choosing the framework does not produce reliable workflows by itself: model quality, storage, deployment, and authority checks still need separate choices. Use the documentation for your installed version."
      ],
      "maintainer_links": [
        {
          "name": "Mastra team",
          "role": "Project maintainers",
          "url": "https://github.com/mastra-ai/mastra"
        },
        {
          "name": "Open-source contributors",
          "role": "Project contributors",
          "url": "https://github.com/mastra-ai/mastra"
        }
      ],
      "maintainers": [
        "Mastra team and open-source contributors (mastra-ai GitHub organization)."
      ],
      "maturity": "Released 1.x core; official GitHub release notes verified for @mastra/core 1.84.0 (Nov. 17, 2026).",
      "name": "Mastra",
      "sources": [
        {
          "title": "Get started with Mastra",
          "type": "guide",
          "url": "https://mastra.ai/docs"
        },
        {
          "title": "Control flow | Workflows",
          "type": "documentation",
          "url": "https://mastra.ai/docs/workflows/control-flow"
        },
        {
          "title": "November 17, 2026",
          "type": "release",
          "url": "https://github.com/mastra-ai/mastra/releases/tag/@mastra/core@1.84.0"
        }
      ],
      "summary": "TypeScript framework for building LLM agents and explicitly orchestrated workflows in one application. Choose it when the team wants both agent flexibility and a coded process around it.",
      "use_when": [
        "Build an internal Node.js assistant whose document lookup or triage process has defined steps and review points.",
        "Choose it over a thin agent loop when the app also needs explicit orchestration, persisted context, or integrated local testing."
      ]
    },
    {
      "category": "frameworks",
      "getting_started": [
        "Install pydantic-ai per the official guide, pick a supported model, and define one small output model plus a read-only tool.",
        "Pass stubbed dependencies in local tests. Separately check source grounding and rules such as allowed domains, maximum results, or missing facts."
      ],
      "how_it_works": [
        "An Agent pairs a model with instructions, functions, a dependency type, and an output type. RunContext makes app dependencies such as a read-only repository or fixture available to tools.",
        "Pydantic-generated schemas describe tool inputs and outputs; validation and configurable retries help the application reject malformed results."
      ],
      "id": "pydantic-ai",
      "limitations": [
        "Schema validation proves shape and any explicitly coded checks, not factual correctness. Native structured output support and behavior also depend on the provider."
      ],
      "maintainer_links": [
        {
          "name": "Pydantic team",
          "role": "Project maintainers",
          "url": "https://github.com/pydantic/pydantic-ai"
        },
        {
          "name": "Open-source contributors",
          "role": "Project contributors",
          "url": "https://github.com/pydantic/pydantic-ai"
        }
      ],
      "maintainers": [
        "Pydantic team and pydantic/pydantic-ai open-source contributors."
      ],
      "maturity": "Released 2.x; public GitHub release v2.71.0 dated November 18, 2026.",
      "name": "Pydantic AI",
      "sources": [
        {
          "title": "Agents",
          "type": "documentation",
          "url": "https://pydantic.dev/docs/ai/core-concepts/agent/"
        },
        {
          "title": "Installation",
          "type": "guide",
          "url": "https://pydantic.dev/docs/ai/overview/install/"
        },
        {
          "title": "v2.71.0 (2026-11-18)",
          "type": "release",
          "url": "https://github.com/pydantic/pydantic-ai/releases/tag/v2.71.0"
        }
      ],
      "summary": "Python agent framework built around type-checked dependencies, tool parameters, and validated outputs. Best when the consumer needs typed application data, not just chat text.",
      "use_when": [
        "Produce citations, document classifications, or extraction records that downstream Python code must consume reliably.",
        "Prefer it over a broader runtime when your application already handles persistence and orchestration and mostly needs typed model interactions."
      ]
    },
    {
      "category": "frameworks",
      "getting_started": [
        "Install a pinned smolagents release. Start with ToolCallingAgent, an approved model adapter, a small step limit, and one read-only tool over fixture data.",
        "If you evaluate CodeAgent, use an isolated executor with no secrets and narrowly scoped filesystem, network, and resource access; test without production data."
      ],
      "how_it_works": [
        "ToolCallingAgent asks the model for structured calls to the tools you expose. CodeAgent instead expresses actions in executable Python, which makes it easier to combine multiple calculations and tools in one action.",
        "The agent runs against a model adapter and a bounded series of steps. Hugging Face provides local and hosted model adapters; the framework also supports alternative providers."
      ],
      "id": "smolagents",
      "limitations": [
        "Generated code is a materially larger execution surface than fixed tool calls. The library's lightweight loop is not production isolation, access control, or durable orchestration."
      ],
      "maintainer_links": [
        {
          "name": "Hugging Face",
          "role": "Project maintainer",
          "url": "https://github.com/huggingface/smolagents"
        },
        {
          "name": "Open-source contributors",
          "role": "Project contributors",
          "url": "https://github.com/huggingface/smolagents"
        }
      ],
      "maintainers": [
        "Hugging Face and huggingface/smolagents open-source contributors."
      ],
      "maturity": "Released 1.x; official GitHub latest release observed v1.26.0.",
      "name": "Hugging Face smolagents",
      "sources": [
        {
          "title": "smolagents",
          "type": "documentation",
          "url": "https://huggingface.co/docs/smolagents/index"
        },
        {
          "title": "Agents - Guided tour",
          "type": "guide",
          "url": "https://huggingface.co/docs/smolagents/main/guided_tour"
        },
        {
          "title": "v1.26.0",
          "type": "release",
          "url": "https://github.com/huggingface/smolagents/releases/tag/v1.26.0"
        }
      ],
      "summary": "Small Python library for model-driven tool loops. It offers conventional tool calls and a code-action variant, rather than requiring a full product runtime.",
      "use_when": [
        "Prototype retrieval or analysis with a few simple tools, or compare how the same task performs with typed calls versus compositional code actions.",
        "Prefer it over an integrated workflow stack when you want a lightweight evaluation prototype and own deployment yourself."
      ]
    },
    {
      "category": "frameworks",
      "getting_started": [
        "Read the official docs and use the CLI or starter for the chosen release. Run a single character locally with one model provider and a minimal plugin set.",
        "Test locally with read-only or mock actions first; configure retention and review plugin permissions before adding external channels."
      ],
      "how_it_works": [
        "A character configuration defines identity, instructions and style. AgentRuntime loads plugins that supply model providers, contextual inputs, and integrations.",
        "Plugins extend the runtime with actions, providers, services and evaluators, letting a project add capabilities without rewriting the core agent loop."
      ],
      "id": "elizaos",
      "limitations": [
        "Third-party plugins can materially expand the agent's privileges. Pin and review them; a character prompt is not an enforcement boundary."
      ],
      "maintainer_links": [
        {
          "name": "elizaOS maintainers",
          "role": "Project maintainers",
          "url": "https://github.com/elizaOS/eliza"
        },
        {
          "name": "Open-source contributors",
          "role": "Project contributors",
          "url": "https://github.com/elizaOS/eliza"
        }
      ],
      "maintainers": [
        "elizaOS maintainers and contributors (elizaOS/eliza GitHub monorepo)."
      ],
      "maturity": "Released 2.x; release v2.0.5 is marked latest and published to npm. Release notes explicitly flag incomplete release-workflow checks.",
      "name": "elizaOS",
      "sources": [
        {
          "title": "Overview - ElizaOS Documentation",
          "type": "documentation",
          "url": "https://docs.elizaos.ai/"
        },
        {
          "title": "elizaOS source and developer README",
          "type": "repository",
          "url": "https://github.com/elizaOS/eliza"
        },
        {
          "title": "v2.0.5",
          "type": "release",
          "url": "https://github.com/elizaOS/eliza/releases/tag/v2.0.5"
        }
      ],
      "summary": "Open TypeScript runtime and product stack for character-driven agents. It gives persistent and channel-facing agents an extensible runtime rather than just a single request loop.",
      "use_when": [
        "Build a persistent persona or a community assistant with carefully controlled capabilities across an app or chat channel.",
        "Choose it if character configuration and plugin reuse are more important than keeping runtime dependencies minimal."
      ]
    },
    {
      "category": "frameworks",
      "getting_started": [
        "For an existing harness, consult the original repository and match its examples to the pinned dependency version.",
        "For a new experiment, read Lucid's integration guide and wrap an approved read-only function as an endpoint. Verify request and response handling locally before adding external integrations."
      ],
      "how_it_works": [
        "In the original harness, createDreams composes contexts and actions. A context defines its own state and memory, and typed actions let the model reach application functions.",
        "The current Lucid Agents SDK wraps application-defined capabilities as service endpoints with optional protocol adapters. The underlying workflow, model and memory still belong to the application, not Lucid."
      ],
      "id": "daydreams",
      "limitations": [
        "The original repository explicitly says the harness is no longer the core focus; Lucid does not replace a model, memory, or workflow runtime."
      ],
      "maintainer_links": [
        {
          "name": "Daydreams contributors",
          "role": "Project contributors",
          "url": "https://github.com/daydreamsai/daydreams"
        }
      ],
      "maintainers": [
        "Daydreams contributors (daydreamsai GitHub organization)."
      ],
      "maturity": "Original harness is no longer the maintainers' focus. Lucid framework integration docs marked stable and verified against 2.5.0 (July 2026).",
      "name": "Daydreams",
      "sources": [
        {
          "title": "Daydreams - AI Agent Framework",
          "type": "repository",
          "url": "https://github.com/daydreamsai/daydreams"
        },
        {
          "title": "Lucid Agents Docs: Agent Frameworks integration",
          "type": "guide",
          "url": "https://docs.daydreams.systems/docs/integrate/agent-frameworks"
        },
        {
          "title": "Lucid Agents: Build and Monetize AI Agents",
          "type": "documentation",
          "url": "https://www.daydreams.systems/products/lucid-agents"
        }
      ],
      "summary": "The original Daydreams TypeScript harness uses context-scoped state and actions. The maintainers have shifted focus to Lucid Agents, an agent-service layer that can sit in front of another runtime.",
      "use_when": [
        "Audit or maintain existing @daydreamsai/core code that uses its context abstraction.",
        "For a new service, consider Lucid if you need a standard endpoint around an existing workflow; compare it with a thin HTTP adapter if commerce integrations are unnecessary."
      ]
    },
    {
      "category": "discovery",
      "getting_started": [
        "Pick the TypeScript or Python SDK from agent0lab. Configure a supported network and the documented data/RPC connection; start with read-only lookup by known chain and agent ID.",
        "Compare returned registration metadata with the endpoint or owner independently; keep registration and feedback writes out of initial tests."
      ],
      "how_it_works": [
        "An agent registration file describes the agent and can advertise endpoints such as A2A and MCP; identity and metadata references are handled through ERC-8004 contracts.",
        "Search uses indexed multi-chain registry data. The SDK can load agent metadata and feedback and the TypeScript repository documents A2A client workflows using advertised interfaces."
      ],
      "id": "agent0-sdk",
      "limitations": [
        "Registry and feedback data do not establish that work was performed well or that the advertised endpoint is safe. Search coverage follows the configured subgraphs and networks."
      ],
      "maintainer_links": [
        {
          "name": "Agent0 team",
          "role": "SDK project team and repository owner",
          "url": "https://github.com/agent0lab"
        },
        {
          "name": "Open-source contributors",
          "role": "SDK contributors",
          "url": "https://github.com/agent0lab/agent0-ts"
        },
        {
          "name": "Marco De Rossi",
          "role": "Credited SDK lead",
          "url": "https://github.com/agent0lab/agent0-ts#license"
        },
        {
          "name": "Consensys",
          "role": "Credited SDK collaborator",
          "url": "https://github.com/agent0lab/agent0-ts#license"
        },
        {
          "name": "MetaMask",
          "role": "Credited SDK collaborator",
          "url": "https://github.com/agent0lab/agent0-ts#license"
        },
        {
          "name": "Agent0, Inc.",
          "role": "Credited SDK collaborator",
          "url": "https://github.com/agent0lab/agent0-ts#license"
        }
      ],
      "maintainers": [
        "Agent0 team and open-source contributors. The project credits Marco De Rossi in collaboration with Consensys, MetaMask, and Agent0, Inc."
      ],
      "maturity": "Public MIT-licensed TypeScript and Python SDKs; available in package registries. No common latest version asserted across implementations.",
      "name": "Agent0 SDK (ERC-8004)",
      "sources": [
        {
          "title": "agent0-ts: TypeScript SDK for agent portability, discovery and trust based on ERC-8004",
          "type": "repository",
          "url": "https://github.com/agent0lab/agent0-ts"
        },
        {
          "title": "agent0-py: Agent0 is the SDK for agentic economies",
          "type": "repository",
          "url": "https://github.com/agent0lab/agent0-py"
        },
        {
          "title": "Agent Zero AI framework (separate project)",
          "type": "repository",
          "url": "https://github.com/agent0ai/agent-zero"
        }
      ],
      "summary": "TypeScript and Python SDKs for reading and writing ERC-8004 agent identity and feedback and discovering indexed agents. This is agent0lab's SDK, not the similarly named Agent Zero runtime.",
      "use_when": [
        "Build a read-only directory or lookup workflow for existing ERC-8004 agents in supported networks.",
        "Choose this if chain-backed identity, endpoint metadata, and portable feedback are useful. It is not a replacement for the local runtime or actual endpoint permissions."
      ]
    },
    {
      "category": "discovery",
      "getting_started": [
        "Select a verified network/subgraph in The Graph docs and follow the gateway API-key instructions; keep the key server-side and do not publish it.",
        "Query a limited page of agents and registration fields; record network, subgraph deployment, and query time and check the chain directly when freshness matters."
      ],
      "how_it_works": [
        "Per-network subgraphs index identity and reputation registry data and normalize records such as registration files, endpoint fields, and feedback for query.",
        "The Graph gateway serves GraphQL queries to network-specific subgraph deployments. A direct query is useful when you need to select fields or build your own cache without the Agent0 SDK."
      ],
      "id": "agent0-the-graph",
      "limitations": [
        "Coverage varies by supported chain and indexed fields. Index and off-chain registration-file freshness can lag, and user-provided feedback does not verify performance."
      ],
      "maintainer_links": [
        {
          "name": "Agent0",
          "role": "Subgraph builder and maintainer",
          "url": "https://thegraph.com/docs/en/subgraphs/existing-subgraphs/agent0/"
        },
        {
          "name": "The Graph",
          "role": "Subgraph infrastructure and project partner",
          "url": "https://thegraph.com/docs/en/subgraphs/existing-subgraphs/agent0/"
        },
        {
          "name": "The Graph Foundation",
          "role": "ERC-8004 data API collaborator",
          "url": "https://thegraph.com/blog/understanding-x402-erc8004/"
        },
        {
          "name": "BuildersDAO",
          "role": "ERC-8004 data API collaborator",
          "url": "https://thegraph.com/blog/understanding-x402-erc8004/"
        }
      ],
      "maintainers": [
        "Agent0 builds and maintains the subgraphs in partnership with The Graph.",
        "The Graph Foundation and BuildersDAO identify Agent0 as a partner in building ERC-8004 data APIs; that does not make the SDK a Foundation product."
      ],
      "maturity": "Live production subgraphs documented by The Graph; supported deployments are listed in the current docs.",
      "name": "Agent0 ERC-8004 Subgraphs on The Graph",
      "sources": [
        {
          "title": "Agent0 Subgraphs (ERC-8004)",
          "type": "documentation",
          "url": "https://thegraph.com/docs/en/subgraphs/existing-subgraphs/agent0/"
        },
        {
          "title": "Understanding Coinbase’s x402 and Ethereum’s ERC-8004",
          "type": "announcement",
          "url": "https://thegraph.com/blog/understanding-x402-erc8004/"
        },
        {
          "title": "agent0lab/subgraph: A subgraph for indexing ERC-8004 protocol data",
          "type": "repository",
          "url": "https://github.com/agent0lab/subgraph"
        }
      ],
      "summary": "Agent0-maintained GraphQL indexes for ERC-8004 data, built in partnership with The Graph. This is the indexed data layer used for discovery, distinct from the Agent0 SDK and the contracts themselves.",
      "use_when": [
        "Power a chain-filtered read-only catalog, research dashboard, or registry audit export.",
        "Choose direct subgraph queries over SDK convenience methods when you only need indexed metadata and can own pagination and refresh logic."
      ]
    },
    {
      "category": "discovery",
      "getting_started": [
        "Use the maintainer's v2 reference implementation to register a test agent and resolve its associated card from a separate client."
      ],
      "how_it_works": [
        "Agent Facts Cards describe an agent and its capabilities so consumers can discover candidates. A card is not itself authorization.",
        "NandaIndex v2 offers an index for reaching agents that do not operate their own public DNS domains; it separates discoverability from owning a domain."
      ],
      "id": "project-nanda",
      "limitations": [
        "Research software and discovery claims are not a readiness guarantee, peer authorization, or proof of completed work."
      ],
      "maintainer_links": [
        {
          "name": "MIT Media Lab Nanda",
          "role": "Research group and project origin",
          "url": "https://www.media.mit.edu/groups/nanda/overview/"
        },
        {
          "name": "Project NANDA contributors",
          "role": "Open-source development and reference implementations",
          "url": "https://github.com/projnanda"
        }
      ],
      "maintainers": [
        "MIT Media Lab Nanda research team and Project NANDA contributors."
      ],
      "maturity": "Active research with open-source NandaIndex v2 reference implementation.",
      "name": "Project NANDA (MIT Media Lab)",
      "sources": [
        {
          "title": "MIT Media Lab: Nanda overview",
          "type": "research group",
          "url": "https://www.media.mit.edu/groups/nanda/overview/"
        },
        {
          "title": "MIT Media Lab: NandaIndex",
          "type": "project announcement",
          "url": "https://www.media.mit.edu/articles/nandaindex-making-ai-agents-discoverable-without-owning-a-domain/"
        },
        {
          "title": "NandaIndex v2 reference implementation",
          "type": "repository",
          "url": "https://github.com/projnanda/nanda-index-v2"
        }
      ],
      "summary": "MIT-origin research and open-source work on how independently operated agents can find one another. NandaIndex is a concrete reference implementation.",
      "use_when": [
        "Explore discovery for a test agent without assuming it owns a public domain."
      ]
    },
    {
      "category": "discovery",
      "getting_started": [
        "Start with the Agent Directory docs and one OASF test record. Publish it in a test environment and search for it by capability from a separate client."
      ],
      "how_it_works": [
        "Directory stores, publishes, and searches agent records by skills and attributes using the Open Agentic Schema Framework (OASF) and distributed content routing.",
        "SLIM provides a communication layer distinct from the Directory and schema; AGNTCY also documents identity and observability components."
      ],
      "id": "agntcy",
      "limitations": [
        "Check compatibility and operational readiness per component. A discoverable record is not a vetted counterparty or authorization to invoke it."
      ],
      "maintainer_links": [
        {
          "name": "AGNTCY contributors",
          "role": "Project governance and component development",
          "url": "https://github.com/agntcy/governance"
        },
        {
          "name": "Linux Foundation",
          "role": "Foundation host for AGNTCY",
          "url": "https://agntcy.org/"
        },
        {
          "name": "Cisco Outshift",
          "role": "Early contributor",
          "url": "https://outshift.cisco.com/the-internet-of-agents/agntcy"
        }
      ],
      "maintainers": [
        "AGNTCY contributors under the Linux Foundation; Cisco Outshift was an early contributor."
      ],
      "maturity": "Active Linux Foundation open-source project with independently released components.",
      "name": "AGNTCY",
      "sources": [
        {
          "title": "AGNTCY project",
          "type": "project site",
          "url": "https://agntcy.org/"
        },
        {
          "title": "AGNTCY component documentation",
          "type": "documentation",
          "url": "https://docs.agntcy.org/index.html"
        },
        {
          "title": "Agent Directory documentation",
          "type": "documentation",
          "url": "https://dir.agntcy.org/latest/"
        }
      ],
      "summary": "Linux Foundation project offering loosely coupled open-source components for finding, connecting, and operating agents across vendors.",
      "use_when": [
        "Try structured capability discovery across independent runtimes, or evaluate a messaging component without adopting the full stack."
      ]
    },
    {
      "category": "ecosystem",
      "getting_started": [
        "Start from the current AAIF project list and follow the project-specific docs and repository for implementation or contributions."
      ],
      "how_it_works": [
        "AAIF hosts a portfolio that includes MCP, A2A, goose, AGENTS.md, and agentgateway; the projects address different parts of the stack.",
        "Projects use their own maintainers, specifications, and repositories within a shared foundation structure. Organizations can propose projects through the published intake process."
      ],
      "id": "aaif",
      "limitations": [
        "Foundation hosting does not make projects interoperable by default or confer a blanket maturity level."
      ],
      "maintainer_links": [
        {
          "name": "Linux Foundation",
          "role": "Host of the AAIF directed fund",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-Agentic-ai-foundation"
        },
        {
          "name": "AAIF Technical Committee",
          "role": "Technical governance body",
          "url": "https://github.com/aaif/technical-committee"
        },
        {
          "name": "Anthropic",
          "role": "Co-founder and founding contributor of MCP",
          "url": "https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agentic-ai-foundation"
        },
        {
          "name": "Block",
          "role": "Co-founder and founding contributor of goose",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-Agentic-ai-foundation"
        },
        {
          "name": "OpenAI",
          "role": "Co-founder and founding contributor of AGENTS.md",
          "url": "https://openai.com/index/agentic-ai-foundation/"
        }
      ],
      "maintainers": [
        "Linux Foundation and the AAIF governing community.",
        "Founding project contributors included Anthropic, Block, and OpenAI."
      ],
      "maturity": "Operating foundation. Founding contributions announced December 2025; portfolio continues to expand.",
      "name": "Agentic AI Foundation (AAIF)",
      "sources": [
        {
          "title": "About AAIF",
          "type": "governance",
          "url": "https://aaif.io/about"
        },
        {
          "title": "Current AAIF projects",
          "type": "project directory",
          "url": "https://aaif.io/projects"
        },
        {
          "title": "Linux Foundation founding announcement",
          "type": "announcement",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-Agentic-ai-foundation"
        }
      ],
      "summary": "A neutral Linux Foundation home for open agentic AI projects; it is a governance organization, not one runtime or spec.",
      "use_when": [
        "Find official project governance and contribution paths, or distinguish related projects that solve different problems."
      ]
    },
    {
      "category": "identity",
      "getting_started": [
        "Use the official Go local quickstart to register a test agent and verify its receipt before integrating with a real domain."
      ],
      "how_it_works": [
        "A Registration Authority registers an agent against a DNS domain and its version. DNS records help peers find profiles and evidence, including a pointer to a public transparency log.",
        "A peer verifies evidence for the current registration and key possession; the published authentication specification describes mTLS and DPoP options."
      ],
      "id": "agent-name-service",
      "limitations": [
        "The current project specification and the IETF Internet-Draft are not interchangeable with a ratified IETF RFC; a verified registration does not establish legal identity, competence, or permission to perform an action."
      ],
      "maintainer_links": [
        {
          "name": "ANS Technical Steering Committee",
          "role": "Project-wide technical direction and governance",
          "url": "https://ansinfo.ai/governance/"
        },
        {
          "name": "Linux Foundation",
          "role": "Foundation host of the current ANS project",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-welcomes-agent-name-service-to-bring-verifiable-identity-and-discovery-to-ai-agents"
        },
        {
          "name": "OWASP GenAI Security Project",
          "role": "Origin of the earlier ANS research proposal",
          "url": "https://genai.owasp.org/resource/agent-name-service-ans-for-secure-al-agent-discovery-v1-0/"
        },
        {
          "name": "GoDaddy",
          "role": "Industry contributor and operator of a specific ANS implementation",
          "url": "https://www.godaddy.com/en/ans"
        }
      ],
      "maintainers": [
        "ANS technical steering committee under the Linux Foundation.",
        "OWASP research authors and industry contributors including GoDaddy are part of the project's history; GoDaddy is not synonymous with the standard."
      ],
      "maturity": "Linux Foundation project launched November 10, 2026; early ecosystem integrations and reference implementations; IETF work remains a draft.",
      "name": "Agent Name Service (ANS)",
      "sources": [
        {
          "title": "ANS specifications",
          "type": "specification",
          "url": "https://ansinfo.ai/docs/"
        },
        {
          "title": "ANS developer quickstart",
          "type": "documentation",
          "url": "https://ansinfo.ai/for-developers/"
        },
        {
          "title": "Linux Foundation ANS project launch",
          "type": "announcement",
          "url": "https://www.linuxfoundation.org/press/linux-foundation-welcomes-agent-name-service-to-bring-verifiable-identity-and-discovery-to-ai-agents"
        }
      ],
      "summary": "Domain-anchored agent identity and discovery. The current Linux Foundation project should be distinguished from the earlier OWASP ANS research proposal and GoDaddy's implementation and registration service.",
      "use_when": [
        "Find an independently operated agent and verify that it is bound to an expected domain and current registration."
      ]
    },
    {
      "category": "ecosystem",
      "getting_started": [
        "Build a read-only A2A task between test agents, then use AP2 materials to simulate authorization and verification of a purchase in a sandbox, without real payment."
      ],
      "how_it_works": [
        "A2A lets agents advertise capabilities and exchange messages and tracked tasks across different implementations.",
        "AP2 adds signed mandate evidence to express what a user approved or delegated for an agent-initiated transaction. It complements rather than replaces communication protocols."
      ],
      "id": "google-cloud-agent-protocols",
      "limitations": [
        "Google originated the work but does not unilaterally govern both projects. AP2 does not substitute for processor integration, chargeback handling, or payment compliance."
      ],
      "maintainer_links": [
        {
          "name": "Google Cloud",
          "role": "A2A originator and contributor; donated A2A to the Linux Foundation",
          "url": "https://opensource.googleblog.com/2026/04/a-year-of-open-collaboration-celebrating-the-anniversary-of-a2a.html"
        },
        {
          "name": "Google",
          "role": "AP2 originator and donor to FIDO Alliance",
          "url": "https://blog.google/products-and-platforms/platforms/google-pay/agent-payments-protocol-fido-alliance/"
        },
        {
          "name": "A2A project community",
          "role": "Maintains the open A2A protocol",
          "url": "https://a2a-protocol.org/"
        },
        {
          "name": "Agentic AI Foundation (AAIF)",
          "role": "Foundation home for A2A",
          "url": "https://aaif.io/projects/agent2agent"
        },
        {
          "name": "FIDO Alliance",
          "role": "Recipient of the AP2 contribution for agentic commerce standards work",
          "url": "https://fidoalliance.org/fido-alliance-to-develop-standards-for-trusted-ai-agent-interactions/"
        }
      ],
      "maintainers": [
        "Google Cloud and Google were originating contributors.",
        "A2A project community under AAIF; FIDO Alliance for the contributed AP2 work."
      ],
      "maturity": "A2A is hosted under AAIF in the Linux Foundation. Google announced AP2's donation to the FIDO Alliance in April 2026; do not imply universal deployment.",
      "name": "Google Cloud / Google: A2A and AP2",
      "sources": [
        {
          "title": "Google: A year of open collaboration with A2A",
          "type": "project history",
          "url": "https://opensource.googleblog.com/2026/04/a-year-of-open-collaboration-celebrating-the-anniversary-of-a2a.html"
        },
        {
          "title": "Google Cloud: Announcing AP2",
          "type": "protocol announcement",
          "url": "https://cloud.google.com/blog/products/ai-machine-learning/announcing-agents-to-payments-ap2-protocol"
        },
        {
          "title": "Google: AP2 donation to FIDO Alliance",
          "type": "governance announcement",
          "url": "https://blog.google/products-and-platforms/platforms/google-pay/agent-payments-protocol-fido-alliance/"
        }
      ],
      "summary": "Google originated A2A for agent communication and led AP2 for evidence of payment authorization. Their stewardship is separate.",
      "use_when": [
        "Evaluate cross-vendor agent handoffs and separately test evidence of user approval for a transaction."
      ]
    },
    {
      "category": "platform",
      "getting_started": [
        "Use the developer guide to deploy a test agent with one read-only Gateway tool, a least-privilege execution role, and observability enabled."
      ],
      "how_it_works": [
        "Runtime runs custom or framework-based agents in managed, isolated sessions with support for multiple model providers and A2A.",
        "Gateway can wrap APIs or Lambda functions as MCP tools and route to existing MCP endpoints; Identity and Observability address access and monitoring."
      ],
      "id": "aws-bedrock-agentcore",
      "limitations": [
        "Verify feature availability by component and Region, quotas, and pricing. Managed infrastructure does not validate task output or remove the need for scoped permissions."
      ],
      "maintainer_links": [
        {
          "name": "Amazon Web Services (AWS)",
          "role": "Developer and operator of the managed AgentCore platform",
          "url": "https://aws.amazon.com/bedrock/agentcore/"
        }
      ],
      "maintainers": [
        "Amazon Web Services (AWS)."
      ],
      "maturity": "Core service generally available since October 2025; feature release stages and Region availability vary.",
      "name": "Amazon Bedrock AgentCore",
      "sources": [
        {
          "title": "AgentCore developer guide overview",
          "type": "documentation",
          "url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/what-is-bedrock-agentcore.html"
        },
        {
          "title": "AWS AgentCore general-availability announcement",
          "type": "announcement",
          "url": "https://aws.amazon.com/about-aws/whats-new/2025/10/amazon-bedrock-agentcore-available/"
        },
        {
          "title": "AgentCore release notes",
          "type": "release notes",
          "url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/release-notes.html"
        }
      ],
      "summary": "AWS managed services for hosting, connecting, and operating agents. The platform is distinct from a model or an open standard.",
      "use_when": [
        "Deploy an agent and expose a controlled tool surface without operating your own runtime fleet."
      ]
    },
    {
      "category": "ecosystem",
      "getting_started": [
        "Read the versioned x401 specification and exercise a synthetic-identity flow on a test endpoint. Test that absent or unacceptable proofs are denied."
      ],
      "how_it_works": [
        "A protected route advertises its credential and mandate requirements over HTTP; the agent obtains a suitable proof with the user's approval where required and resubmits the request.",
        "The verifier checks the credential presentation and relevant claims against its own trusted-issuer and access policy. Proof's wallet and API are implementation options."
      ],
      "id": "proof-company",
      "limitations": [
        "Do not confuse x401 with the x402 payment protocol. Compatibility, issuer coverage, credential custody, and what is actually authorized must be checked."
      ],
      "maintainer_links": [
        {
          "name": "Proof",
          "role": "Originated x401 and maintains its public specification and reference repository",
          "url": "https://github.com/proof/x401"
        }
      ],
      "maintainers": [
        "Proof authored x401 and maintains the public reference repository and its service integrations."
      ],
      "maturity": "Published Proof tooling and public spec; the repository identifies v0.2.0. Pin versions; early and current drafts differ.",
      "name": "Proof (creator of x401)",
      "sources": [
        {
          "title": "Proof launches x401",
          "type": "launch announcement",
          "url": "https://www.proof.com/blog/proof-launches-x401-giving-ai-agents-a-way-to-prove-who-they-represent---and-what-theyre-authorized-to-do"
        },
        {
          "title": "Proof developer documentation",
          "type": "documentation",
          "url": "https://dev.proof.com/"
        },
        {
          "title": "x401 public specification",
          "type": "specification",
          "url": "https://github.com/proof/x401/blob/main/spec.md"
        }
      ],
      "summary": "Identity-verification company that created the HTTP-native x401 protocol and offers a wallet and developer tooling. The company is distinct from the protocol.",
      "use_when": [
        "Evaluate a route that requires verified identity or a narrowly scoped mandate rather than a claim supplied by a model."
      ]
    },
    {
      "category": "ecosystem",
      "getting_started": [
        "Follow the upstream standalone MCP quickstart with a local test server. Confirm routing and access control before exposing public traffic."
      ],
      "how_it_works": [
        "agentgateway sits on the traffic path between clients, model endpoints, MCP tool servers and A2A services, with protocol-aware routing.",
        "Standalone and Kubernetes deployments can centralize policy and telemetry at the gateway; enterprise packaging adds vendor-specific services and features."
      ],
      "id": "solo-io",
      "limitations": [
        "A gateway can enforce configured access at the network boundary, but does not establish agent identity independently or certify task outcomes. Check community versus commercial feature coverage."
      ],
      "maintainer_links": [
        {
          "name": "Solo.io",
          "role": "Created and donated agentgateway; separate commercial offerings",
          "url": "https://www.solo.io/blog/solo-contributes-agentgateway-linux-foundation"
        },
        {
          "name": "agentgateway community",
          "role": "Maintains the community open-source implementation",
          "url": "https://github.com/agentgateway/agentgateway"
        },
        {
          "name": "Agentic AI Foundation (AAIF)",
          "role": "Foundation host of agentgateway",
          "url": "https://aaif.io/projects/agentgateway"
        }
      ],
      "maintainers": [
        "Solo.io created and contributed agentgateway; the AAIF-hosted project is community maintained."
      ],
      "maturity": "Open-source agentgateway was donated in 2025 and is now hosted by AAIF. Solo offers a separate enterprise edition.",
      "name": "Solo.io",
      "sources": [
        {
          "title": "Solo.io contributes agentgateway to the Linux Foundation",
          "type": "announcement",
          "url": "https://www.solo.io/blog/solo-contributes-agentgateway-linux-foundation"
        },
        {
          "title": "Solo agentgateway enterprise documentation",
          "type": "documentation",
          "url": "https://docs.solo.io/agentgateway/standalone/latest/documentation/about/"
        },
        {
          "title": "Upstream MCP quickstart",
          "type": "documentation",
          "url": "https://agentgateway.dev/docs/standalone/latest/documentation/quickstart/mcp/"
        }
      ],
      "summary": "Company that created agentgateway, a protocol-aware traffic gateway for agent systems. Solo's enterprise offering is distinct from the community project.",
      "use_when": [
        "Put a controlled proxy between test agents and a tool server instead of implementing routing and access policy inside every agent."
      ]
    },
    {
      "category": "payments",
      "getting_started": [
        "Use provider examples to map client, resource server and facilitator roles; begin with mock or testnet flows."
      ],
      "how_it_works": [
        "x402 lets services issue HTTP payment requirements and clients retry with a payment authorization; compatible facilitators verify and settle it.",
        "Coinbase CDP offers facilitator tooling; Cloudflare's Agents SDK documents consuming paid endpoints and charging for MCP tool calls."
      ],
      "id": "coinbase-cloudflare-x402",
      "limitations": [
        "Cloudflare compute and Coinbase facilitation are optional choices. Membership does not guarantee parity across facilitators, networks or assets."
      ],
      "maintainer_links": [
        {
          "name": "x402 Foundation",
          "role": "Open-governance steward of the x402 protocol.",
          "url": "https://x402.org/"
        },
        {
          "name": "Linux Foundation",
          "role": "Neutral host of the x402 Foundation.",
          "url": "https://www.linuxfoundation.org/"
        },
        {
          "name": "Coinbase",
          "role": "Originator and contributor of x402, premier foundation member, and maintainer of Coinbase CDP tooling.",
          "url": "https://www.coinbase.com/developer-platform"
        },
        {
          "name": "Cloudflare",
          "role": "Premier foundation member and maintainer of its own Agents SDK integration; not sole protocol steward.",
          "url": "https://developers.cloudflare.com/agents/tools/payments/x402/"
        }
      ],
      "maintainers": [
        "x402 Foundation under the Linux Foundation; Coinbase and Cloudflare as contributors and premier members."
      ],
      "maturity": "Foundation operational launch announced July 2026; public CDP and Cloudflare developer tooling.",
      "name": "Coinbase and Cloudflare: x402",
      "sources": [
        {
          "title": "Foundation operational launch",
          "type": "Foundation announcement",
          "url": "https://x402.org/linux-foundation-announces-operational-launch-of-x402-foundation-to-standardize-internet-native-payments-for-ai-agents-and-applications/"
        },
        {
          "title": "Coinbase CDP x402 starter examples",
          "type": "Official repository",
          "url": "https://github.com/coinbase/cdp-sdk/blob/main/examples/typescript/x402/README.md"
        },
        {
          "title": "Cloudflare Agents SDK x402 docs",
          "type": "Official documentation",
          "url": "https://developers.cloudflare.com/agents/tools/payments/x402/"
        }
      ],
      "summary": "Coinbase originated and contributed x402; Cloudflare co-announced the foundation effort and ships SDK integrations. Both are premier members, not exclusive owners, of the Linux Foundation-hosted x402 Foundation.",
      "use_when": [
        "Understand governance or choose infrastructure for an x402 integration."
      ]
    },
    {
      "category": "payments",
      "getting_started": [
        "Start with the read-only discovery endpoint from PayAI's developer portal; check freshness and reconcile versions against the seller's docs."
      ],
      "how_it_works": [
        "Public discovery resources provide listed endpoints, last-recorded terms and seller-declared schemas where available.",
        "Catalog and settlement statistics have separate definitions; inspect timestamps and fetch live terms directly from the seller before use."
      ],
      "id": "payai-network",
      "limitations": [
        "A listing can persist without refresh and does not prove availability, settlement, trustworthiness or service quality."
      ],
      "maintainer_links": [
        {
          "name": "PayAI Network",
          "role": "Operator of the PayAI facilitator and its Bazaar discovery catalog.",
          "url": "https://payai.network/developers"
        }
      ],
      "maintainers": [
        "PayAI Network"
      ],
      "maturity": "Documented public catalog and facilitator API.",
      "name": "PayAI Network: Bazaar",
      "sources": [
        {
          "title": "Bazaar discovery documentation",
          "type": "Official documentation",
          "url": "https://docs.payai.network/x402/facilitators/bazaar"
        },
        {
          "title": "PayAI developer portal",
          "type": "Official documentation",
          "url": "https://payai.network/developers"
        }
      ],
      "summary": "PayAI operates an x402 facilitator and a discovery catalog for x402-payable services.",
      "use_when": [
        "Find candidate paid APIs or compare declared interfaces without paying."
      ]
    },
    {
      "category": "payments",
      "getting_started": [
        "Review the official reference repo and prototype with staging API keys and test assets; enforce tight budgets and approval boundaries."
      ],
      "how_it_works": [
        "The sample architecture combines Crossmint wallet APIs with x402 middleware on the seller side.",
        "Reference applications illustrate an agent consuming a metered service; the wallet layer and facilitator are separate responsibilities."
      ],
      "id": "crossmint",
      "limitations": [
        "Samples do not prove production readiness, broad network compatibility or that risk controls are enabled by default."
      ],
      "maintainer_links": [
        {
          "name": "Crossmint",
          "role": "Maintainer of its wallet tooling and agentic-finance starter examples.",
          "url": "https://github.com/Crossmint/crossmint-agentic-finance"
        }
      ],
      "maintainers": [
        "Crossmint"
      ],
      "maturity": "Documented commercial platform; public starter repository. Verify production eligibility with the vendor.",
      "name": "Crossmint",
      "sources": [
        {
          "title": "Crossmint agentic finance starter repository",
          "type": "Official repository",
          "url": "https://github.com/Crossmint/crossmint-agentic-finance"
        },
        {
          "title": "Agentic Finance Quickstart",
          "type": "Official documentation",
          "url": "https://www.mintlify.com/Crossmint/crossmint-agentic-finance/quickstart"
        }
      ],
      "summary": "Managed wallet and commerce tooling with official agentic-finance sample applications using x402.",
      "use_when": [
        "Evaluate a managed wallet integration rather than building wallet infrastructure first."
      ]
    },
    {
      "category": "payments",
      "getting_started": [
        "Follow the facilitator guide in a test environment and confirm networks, assets and supported payment schemes before integrating."
      ],
      "how_it_works": [
        "A resource server delegates x402 verification and settlement to the facilitator; verify checks a submitted payment, while settle submits it.",
        "Platform configuration separates facilitator setup from resource-server pricing and endpoint logic."
      ],
      "id": "thirdweb",
      "limitations": [
        "A settled payment does not prove the API returned the expected result. Availability and supported rails are implementation-specific."
      ],
      "maintainer_links": [
        {
          "name": "thirdweb",
          "role": "Operator and documenter of thirdweb's x402 facilitator.",
          "url": "https://portal.thirdweb.com/x402/facilitator"
        }
      ],
      "maintainers": [
        "thirdweb"
      ],
      "maturity": "Public developer documentation and integration tooling.",
      "name": "thirdweb",
      "sources": [
        {
          "title": "x402 Facilitator",
          "type": "Official documentation",
          "url": "https://portal.thirdweb.com/x402/facilitator"
        },
        {
          "title": "thirdweb x402 documentation",
          "type": "Official documentation",
          "url": "https://portal.thirdweb.com/x402"
        }
      ],
      "summary": "Developer platform with a documented x402 facilitator for payment verification and settlement.",
      "use_when": [
        "Compare a managed x402 facilitator with operating one yourself."
      ]
    },
    {
      "category": "payments",
      "getting_started": [
        "Read Faremeter's repository and inspect the sandbox or test examples before enabling any settlement."
      ],
      "how_it_works": [
        "Faremeter supplies client/server components and payment plugins; a compatible client can wrap a normal fetch for an x402 flow.",
        "Corbits publishes example payable APIs, and the Faremeter playground documents a Corbits facilitator integration."
      ],
      "id": "corbits",
      "limitations": [
        "Faremeter is distinct from the Corbits hosted facilitator. Some walkthroughs target mainnet; do not run them with funded production credentials during evaluation."
      ],
      "maintainer_links": [
        {
          "name": "Corbits",
          "role": "Provider of Corbits' hosted infrastructure and example APIs.",
          "url": "https://www.corbits.dev/"
        },
        {
          "name": "Faremeter contributors",
          "role": "Maintainers of the separate open-source Faremeter framework.",
          "url": "https://github.com/faremeter/faremeter"
        }
      ],
      "maintainers": [
        "Corbits; Faremeter contributors"
      ],
      "maturity": "Public open-source framework and hosted integration examples. Current live network matrix not independently verified.",
      "name": "Corbits / Faremeter",
      "sources": [
        {
          "title": "Faremeter framework",
          "type": "Official repository",
          "url": "https://github.com/faremeter/faremeter"
        },
        {
          "title": "Corbits API",
          "type": "Official documentation",
          "url": "https://api.corbits.dev/"
        },
        {
          "title": "Faremeter TypeScript playground",
          "type": "Official repository",
          "url": "https://github.com/faremeter/faremeter-ts-playground"
        }
      ],
      "summary": "Corbits provides x402 infrastructure and public APIs, while Faremeter is an open-source framework for HTTP machine payments.",
      "use_when": [
        "Prototype payment interoperability or evaluate plugin-based multichain designs."
      ]
    },
    {
      "category": "payments",
      "getting_started": [
        "Review AEON's versioned docs and test against an owned mock or approved sandbox before considering a merchant connection."
      ],
      "how_it_works": [
        "The AEON-Project BNB x402 repository documents payment requirements and facilitator interaction.",
        "AEON's QR flow associates an order with a versioned x402 payment request; AgentOS demonstrates client-side consumption of metered services."
      ],
      "id": "aeon",
      "limitations": [
        "A QR/payment integration does not guarantee merchant, regional, asset or chain coverage. No live payment was tested."
      ],
      "maintainer_links": [
        {
          "name": "AEON",
          "role": "Provider of AEON merchant payment tooling and its documented QR flow.",
          "url": "https://aeon-xyz.readme.io/docs/x402-qr-code-payment"
        },
        {
          "name": "AEON-Project",
          "role": "AEON's public GitHub organization for AgentOS and x402 reference code.",
          "url": "https://github.com/AEON-Project"
        }
      ],
      "maintainers": [
        "AEON / AEON-Project"
      ],
      "maturity": "Public V2 documentation and reference projects; confirm region and network availability.",
      "name": "AEON",
      "sources": [
        {
          "title": "BNB x402 reference",
          "type": "Official repository",
          "url": "https://github.com/AEON-Project/bnb-x402"
        },
        {
          "title": "AEON QR code payment v2",
          "type": "Official documentation",
          "url": "https://aeon-xyz.readme.io/docs/x402-qr-code-payment"
        },
        {
          "title": "AEON AgentOS",
          "type": "Official repository",
          "url": "https://github.com/AEON-Project/AgentOS"
        }
      ],
      "summary": "Agent commerce payment infrastructure, with documented x402 integrations for BNB Chain and merchant QR payment flows.",
      "use_when": [
        "Evaluate a BNB Chain implementation or AEON-specific merchant integration."
      ]
    },
    {
      "category": "payments",
      "getting_started": [
        "Review Passport allowance behavior, expiry and revocation with a test session. Use seller docs to confirm supported rails."
      ],
      "how_it_works": [
        "Passport links an agent to wallet access controlled by the user; the user authorizes a spending session with a passkey.",
        "Session allowances bound agent spending; sellers separately integrate protocol-specific payment acceptance."
      ],
      "id": "kite-ai",
      "limitations": [
        "A wallet session is not evidence of task quality or legal delegation. Verify limits and actual rail support independently."
      ],
      "maintainer_links": [
        {
          "name": "Kite AI",
          "role": "Maintainer of Kite Passport and Kite seller integration documentation.",
          "url": "https://docs.gokite.ai/"
        }
      ],
      "maintainers": [
        "Kite AI"
      ],
      "maturity": "Public Passport developer documentation and release notes.",
      "name": "Kite AI / Kite Passport",
      "sources": [
        {
          "title": "Kite Passport",
          "type": "Official documentation",
          "url": "https://docs.gokite.ai/passport"
        },
        {
          "title": "Allowance and sessions",
          "type": "Official documentation",
          "url": "https://docs.gokite.ai/passport/payments/allowance"
        },
        {
          "title": "Service provider guide",
          "type": "Official documentation",
          "url": "https://docs.gokite.ai/passport/seller"
        }
      ],
      "summary": "Agent wallet and spending-control platform. Kite documents x402 and MPP acceptance for sellers.",
      "use_when": [
        "Evaluate user-controlled spend permissions or seller integration."
      ]
    },
    {
      "category": "orchestration",
      "getting_started": [
        "Build a non-payment workflow first; use the docs and case study to assess whether the relevant connector is currently available."
      ],
      "how_it_works": [
        "Questflow organizes specialized agents into workflows for multi-step tasks.",
        "The x402 case study describes payment-enabled agent workflows as an integration pattern, not the orchestration engine becoming a settlement network."
      ],
      "id": "questflow",
      "limitations": [
        "A partnership page does not establish generalized x402 support on every workflow or hosted plan."
      ],
      "maintainer_links": [
        {
          "name": "Questflow",
          "role": "Provider and maintainer of Questflow's platform and product documentation.",
          "url": "https://docs.questflow.ai/"
        }
      ],
      "maintainers": [
        "Questflow"
      ],
      "maturity": "Public product docs and x402 partner case study; no broad availability claim independently confirmed.",
      "name": "Questflow",
      "sources": [
        {
          "title": "Questflow documentation",
          "type": "Official documentation",
          "url": "https://docs.questflow.ai/"
        },
        {
          "title": "Questflow's x402 partnership case study",
          "type": "Official case study",
          "url": "https://questflow.ai/customers/x402/"
        }
      ],
      "summary": "Multi-agent orchestration platform with a published x402 partnership case study.",
      "use_when": [
        "Explore coordinating multiple agents or metered tools inside a workflow."
      ]
    },
    {
      "category": "data",
      "getting_started": [
        "Start from official docs with an authorized test site; set scope and credit limits and retain source URLs."
      ],
      "how_it_works": [
        "Scrape targets individual pages; Crawl discovers and processes related pages within configured bounds.",
        "The hosted service documents credit-based usage and agent onboarding; APIs can return structured or LLM-ready content."
      ],
      "id": "firecrawl",
      "limitations": [
        "Primary-source evidence reviewed did not confirm first-party generally available x402 billing. A community feature request is not a launch."
      ],
      "maintainer_links": [
        {
          "name": "Firecrawl",
          "role": "Provider and maintainer of the Firecrawl web data API.",
          "url": "https://www.firecrawl.dev/"
        }
      ],
      "maintainers": [
        "Firecrawl"
      ],
      "maturity": "Established hosted web data API. x402 availability unconfirmed.",
      "name": "Firecrawl",
      "sources": [
        {
          "title": "Firecrawl pricing and agent onboarding",
          "type": "Official product page",
          "url": "https://www.firecrawl.dev/pricing"
        },
        {
          "title": "Firecrawl Crawl API",
          "type": "Official product page",
          "url": "https://www.firecrawl.dev/crawl"
        },
        {
          "title": "Community proposal in official repository (not product documentation)",
          "type": "Public issue",
          "url": "https://github.com/firecrawl/firecrawl/issues/3279"
        }
      ],
      "summary": "Web data API that turns permitted public pages and sites into machine-readable content. Keep it separate from x402 facilitator entries.",
      "use_when": [
        "Supply source text to a research workflow while respecting rights, site terms and privacy."
      ]
    },
    {
      "category": "trust",
      "getting_started": [
        "Read the Trustline and X402 Secure design docs and evaluate using synthetic transactions or mock decisions."
      ],
      "how_it_works": [
        "Trustline supplies risk assessment and evidence records for X402 Secure.",
        "X402 Secure integrates with facilitator or gateway flows for payment binding and enforcement, including a documented XRPL extension."
      ],
      "id": "t54-labs",
      "limitations": [
        "Not a wallet, custodian or replacement settlement rail. Vendor risk signals are not guarantees of absence of fraud or proof of fulfillment."
      ],
      "maintainer_links": [
        {
          "name": "t54 Labs",
          "role": "Maintainer of X402 Secure and related risk tooling.",
          "url": "https://github.com/t54-labs"
        }
      ],
      "maintainers": [
        "t54 Labs"
      ],
      "maturity": "Public product docs and source repository; hosted proxy availability claimed by the vendor, not tested.",
      "name": "t54 Labs / t54.ai",
      "sources": [
        {
          "title": "t54 documentation and product map",
          "type": "Official documentation",
          "url": "https://docs.t54.ai/"
        },
        {
          "title": "X402 Secure design",
          "type": "Official documentation",
          "url": "https://docs.t54.ai/docs/products/x402-secure"
        },
        {
          "title": "t54-labs X402 Secure source",
          "type": "Official repository",
          "url": "https://github.com/t54-labs/x402-secure"
        }
      ],
      "summary": "The handwritten t54.ai matches the vendor behind X402 Secure, a risk and evidence layer for machine payments.",
      "use_when": [
        "Assess whether merchant-side risk policies and audit evidence are needed around an x402 integration."
      ]
    }
  ],
  "reviewed_on": "2026-11-20",
  "schema_version": "1.1.0",
  "sections": [
    {
      "entry_ids": [
        "google-adk",
        "langgraph",
        "crewai",
        "strands-agents",
        "goose",
        "openai-agents-sdk",
        "claude-agent-sdk",
        "mastra",
        "pydantic-ai",
        "smolagents",
        "elizaos",
        "daydreams"
      ],
      "title": "Frameworks and agent runtimes"
    },
    {
      "entry_ids": [
        "nlweb",
        "project-nanda",
        "agntcy",
        "agent-name-service",
        "agent0-sdk",
        "agent0-the-graph"
      ],
      "title": "Discovery, publishing, and identity"
    },
    {
      "entry_ids": [
        "aaif",
        "google-cloud-agent-protocols",
        "aws-bedrock-agentcore",
        "proof-company",
        "solo-io"
      ],
      "title": "Platforms and standards stewards"
    },
    {
      "entry_ids": [
        "coinbase-cloudflare-x402",
        "payai-network",
        "crossmint",
        "thirdweb",
        "corbits",
        "aeon",
        "kite-ai",
        "questflow",
        "firecrawl",
        "t54-labs"
      ],
      "title": "Commerce and web tooling"
    }
  ],
  "start_here": [
    {
      "goal": "Orchestrate a durable workflow with explicit state",
      "ids": [
        "langgraph",
        "mastra"
      ],
      "note": "Compare interruption and resume behavior, not just the shortest first demo."
    },
    {
      "goal": "Build a typed Python agent or an explicit role-based team",
      "ids": [
        "pydantic-ai",
        "crewai"
      ],
      "note": "Choose typed IO for a service boundary or team roles for workflow readability. A single workflow is often easier to test first."
    },
    {
      "goal": "Match a framework to your model provider or managed runtime",
      "ids": [
        "google-adk",
        "strands-agents",
        "openai-agents-sdk",
        "claude-agent-sdk",
        "aws-bedrock-agentcore"
      ],
      "note": "A framework provides the application loop; a managed runtime is a separate deployment and operational decision."
    },
    {
      "goal": "Publish a site or discover agent capabilities",
      "ids": [
        "nlweb",
        "project-nanda",
        "agntcy",
        "agent-name-service",
        "agent0-sdk",
        "agent0-the-graph"
      ],
      "note": "Publishing searchable content, resolving an agent, discovering capabilities, and verifying an operator are separate jobs."
    },
    {
      "goal": "Add a paid web or API capability",
      "ids": [
        "coinbase-cloudflare-x402",
        "payai-network",
        "crossmint",
        "thirdweb",
        "corbits",
        "aeon",
        "kite-ai",
        "questflow",
        "firecrawl",
        "t54-labs"
      ],
      "note": "Separate payment rails, merchant settlement, credit or custody, and actual task delivery. Start with documentation and read-only discovery or sandbox tests."
    }
  ],
  "title": "Stream Presence — Tools and Ecosystem",
  "unresolved_topics": [
    {
      "label": "Millionhandshakes",
      "note": "The handwritten name looks like Millionhandshakes. Exact-name searches did not identify a primary source matching an agent ecosystem project. It is not included as a verified entry.",
      "status": "unresolved"
    }
  ]
}
