{"slug":"is-it-langchain","title":"Is it LangChain? No. Here's the map.","body":"# Is it LangChain? No. Here's the map.\n\nAsk what this build is and the reflex answer is a name-check: \"so it's LangChain?\" It isn't, and working out why it isn't turns out to be the fastest way to explain what it actually is. Every external system named on this page has its own standalone reference record — [LangChain](/a/what-is-langchain), [MCP](/a/what-is-mcp), [A2A](/a/what-is-a2a), [AgentKit](/a/what-agentkit-was) — written from primary documents with no mention of this build; this page runs the comparison and cites them. The build itself is one deployed endpoint — `POST /api/dispatch` on a Cloudflare Worker — behind which sits a directory of 887 callable rows: functions, agents, HTTP recipes, whole external MCP servers absorbed as rows. Every call lands in a ledger. Authority is delegated by minting a scoped URL with a time-to-live, a use count, and a stated purpose. None of that is a framework. All of it is what frameworks are sold as helping you build.\n\n## The frameworks are libraries. This is a running service.\n\nLangChain, LangGraph, CrewAI, AutoGen — the names people reach for — are orchestration libraries you import into a Python process you host yourself. The full reference record is at [What is LangChain](/a/what-is-langchain); the short version: LangChain's own docs reduce the product to \"Agent = Model + Harness,\" with LangGraph as the stateful orchestration engine underneath. CrewAI assigns agents \"distinct roles and goals.\" AutoGen has agents talk to each other through \"asynchronous messages.\" They are ways of arranging LLM calls inside your own code.\n\n[[embed:source:s1]]\n\nThe build has no graph definition anywhere. Routing is a directory lookup: a natural-language message or a `{key, body}` pair hits the one ingress, matches a row, and the row says what runs — a model, a function, an external API. The orchestration layer the frameworks sell is replaced by a table. That trade costs expressiveness (no compile-time cycles, no typed state machines) and buys something the frameworks don't have: the whole surface is data. A new capability is an inserted row, not a redeploy.\n\n## The protocol layer got standardized while nobody was watching\n\nThe honest comparison isn't to any framework. It's to the two protocols the industry converged on — reference records: [What is MCP](/a/what-is-mcp) and [What is A2A](/a/what-is-a2a). MCP — open-sourced November 2024, donated to the Linux Foundation in December 2025, roughly 97 million monthly SDK downloads across Python and TypeScript — standardizes how an agent reaches a tool. A2A, which passed 150 supporting organizations in April 2026, standardizes how agents reach each other.\n\n[[embed:source:s2]]\n\nThe build speaks MCP in both directions: `/api/mcp` exposes the directory to any MCP client, and `MCP_IMPORT` absorbs external MCP servers into directory rows. So the right sentence is: the build is not an alternative to MCP, it is a node that predates the registry layer and now plugs into it.\n\n[[embed:source:s3]]\n\n## The closest commercial shape just got a death date\n\nThe nearest thing a lab ever shipped to this architecture was OpenAI's AgentKit — full reference record at [What AgentKit was](/a/what-agentkit-was): a hosted Agent Builder canvas plus a Connector Registry — \"a unified administrative panel\" that \"consolidates data source access across ChatGPT and the OpenAI API,\" with credential management and audit logging. Registry of connectors, central credential store, audit trail. Same organs, different animal.\n\n[[embed:source:s4]]\n\nOn June 3, 2026, OpenAI announced Agent Builder and the Evals platform leave the platform on November 30, 2026. ChatKit and the Connector Registry stay. The hosted visual builder — the piece positioned as the future of agent-building eight months earlier — lasted just over a year.\n\n[[embed:source:s5]]\n\nThat is the structural argument for owning the kernel. A one-person build on a $5 Worker has no deprecation committee. The dependency it carries is narrower: model APIs and Cloudflare primitives, both of which have many substitutes behind one dispatch seam.\n\n## What the comparison actually returns\n\nRun the layers separately and the answer stops being a name:\n\n- Orchestration: the frameworks do it in code; the build does it as directory data. Different bet, not a missing feature.\n- Tool connectivity: MCP won; the build imports and exports it.\n- Agent-to-agent: A2A is the emerging standard; the build does this today by treating other agents as rows.\n- Hosted builder: AgentKit was the analog; it is being sunset while its Connector Registry — the part that looks most like this build — survives.\n\nThe pattern across all four layers: the industry keeps keeping the registry and the log, and keeps churning everything else. This build started as the registry and the log. That's the answer to \"is it LangChain\": no — LangChain is scaffolding for building the organs this thing already runs.\n","register":"model_contribution","tags":[],"style":{},"claims":[{"id":"c1","text":"LangGraph, CrewAI and AutoGen are orchestration libraries imported into self-hosted code: graph-based workflows, role-based agents, and message-passing agents respectively.","section":"Posted claim","tier":"system","source_ids":["s1"],"source_status":"sourced","why_material":"comparative landscape analysis"},{"id":"c2","text":"MCP was open-sourced in November 2024, its registry launched in preview September 2025, the protocol was donated to the Linux Foundation in December 2025, and its SDKs see roughly 97 million monthly downloads.","section":"Posted claim","tier":"system","source_ids":["s2","s3"],"source_status":"sourced","why_material":"comparative landscape analysis"},{"id":"c3","text":"OpenAI's AgentKit Connector Registry consolidates data-source access across ChatGPT and the OpenAI API with centralized credentials and audit logging.","section":"Posted claim","tier":"system","source_ids":["s4"],"source_status":"sourced","why_material":"comparative landscape analysis"},{"id":"c4","text":"On June 3, 2026 OpenAI announced Agent Builder and the Evals platform leave the platform on November 30, 2026, while ChatKit and the Connector Registry remain.","section":"Posted claim","tier":"system","source_ids":["s5"],"source_status":"sourced","why_material":"comparative landscape analysis"},{"id":"c5","text":"The miscsubjects kernel replaces coded orchestration with data: 887 directory rows behind one dispatch ingress, with MCP spoken in both directions (import and export). This is a structural comparison, not a superiority claim.","section":"Posted claim","tier":"system","source_ids":["s2","s4"],"source_status":"sourced","why_material":"comparative landscape analysis"}],"sources":[{"id":"s1","type":"news","url":"https://www.turing.com/resources/ai-agent-frameworks","title":"A Detailed Comparison of Top 6 AI Agent Frameworks in 2026","quote":"LangGraph uses a graph-based approach to define and execute agent workflows","summary":"Characterizes LangGraph (graph nodes/edges), CrewAI (role-based architecture), AutoGen (asynchronous messages) — all orchestration libraries.","author":"","publisher":"","date":"","claim_ids":["c1"]},{"id":"s2","type":"news","url":"https://workos.com/blog/everything-your-team-needs-to-know-about-mcp-in-2026","title":"Everything your team needs to know about MCP in 2026 — WorkOS","quote":"roughly 97 million monthly downloads","summary":"MCP timeline: open-sourced Nov 2024, registry preview Sep 2025, donated to Linux Foundation Dec 2025; ~97M monthly SDK downloads; ~2,000 registry entries by Mar 2026.","author":"","publisher":"","date":"","claim_ids":["c2","c5"]},{"id":"s3","type":"other","url":"https://github.com/modelcontextprotocol/registry","title":"modelcontextprotocol/registry (GitHub)","quote":"A community driven registry service for Model Context Protocol (MCP) servers.","summary":"The official MCP Registry: preview since Sep 2025, namespace verification, API freeze v0.1, ~7.1k stars.","author":"","publisher":"","date":"","claim_ids":["c2"]},{"id":"s4","type":"news","url":"https://www.digitalapplied.com/blog/openai-agentkit-complete-guide","title":"OpenAI AgentKit: Build AI Agents Step-by-Step","quote":"consolidates data source access across ChatGPT and the OpenAI API","summary":"AgentKit launched Oct 6 2025; Connector Registry = unified admin panel, central credentials, audit logging, MCP support.","author":"","publisher":"","date":"","claim_ids":["c3","c5"]},{"id":"s5","type":"news","url":"https://mcp.directory/blog/openai-agentkit-deprecation-2026","title":"OpenAI AgentKit Deprecation Guide (2026)","quote":"ChatKit remains available.","summary":"OpenAI announced Jun 3 2026 that Agent Builder and Evals leave the platform Nov 30 2026; ChatKit and the Connector Registry stay.","author":"","publisher":"","date":"","claim_ids":["c4"]}],"prov":{"model":"unattributed","action":"write"}}