{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"what-is-url-is-api","urls":{"read":"https://miscsubjects.com/api/articles/what-is-url-is-api/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/what-is-url-is-api/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/what-is-url-is-api/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/what-is-url-is-api/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/what-is-url-is-api/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/what-is-url-is-api/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/what-is-url-is-api/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"what-is-url-is-api","title":"What Is \"The URL Is the API\"","register":"standard","tags":["oip","kimi-import","self-explaining","voxel","concepts","what-is-url-is-api"],"updated_at":"2026-07-15T04:21:06.867Z","body_excerpt":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Protocol Concepts](https://miscsubjects.com/a/oip-protocol-concepts) › **What Is \"The URL Is the API\"**\n>\n> **Shelf:** Protocol Concepts · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# What Is \"The URL Is the API\"\n\n## §SELF — what-is-url-is-api\n\n**What this page is:** An explanation of why a URL can serve as its own API specification, replacing the need for separate manifests or schemas.\n**What it explains:** How a URL plus a contract at the destination can replace pre-registered tool manifests, and what changes when models discover capabilities by following links instead of reading catalogs.\n**Why read it:** To understand why removing the manifest layer between a model and a capability makes the set of available tools unbounded rather than fixed.\n\n### What \"The URL Is the API\" Is\n\n\"The URL is the API\" means: the link itself contains everything needed to invoke the capability it points to. You do not need a separate API specification. You do not need to register the tool in a manifest. You do not need to describe it in a schema. The URL is the tool definition.\n\nA URL (Uniform Resource Locator) is a web address that points to a resource. In this model, it does more than point. It carries:\n\n- A pointer to an object (the destination).\n- A contract at that destination describing what the object does, what arguments it takes, and how to use it.\n- A capability token (embedded in or alongside the URL) that proves permission to invoke.\n\nThe model opens the URL, reads the contract, invokes the object, and receives a receipt. No manifest was consulted. No schema was preloaded. The URL was sufficient.\n\n### Why It Matters\n\nMost tool-calling systems for language models use a manifest model. The model is given a list of available tools at startup — a catalog with names, descriptions, parameter types, and schemas. The model picks from this list. This is how MCP (Model Context Protocol) works.\n\nThe manifest model has three limitations:\n\n1. The set of tools is fixed at startup. The model cannot discover new tools while working.\n2. Someone must maintain the manifest. Adding a tool requires updating the catalog.\n3. The manifest is a bottleneck. Every tool must pass through it to reach the model.\n\nThe URL-is-API model removes the manifest. Every capability on the web is potentially a tool. The model discovers capabilities by following links, not by reading a catalog.\n\nThere are billions of URLs on the web. If models can treat any URL as a potential tool, the set of available capabilities is unbounded. The model's abilities become a property of what it is pointing at, not what it was shipped with.\n\n### The Key Idea\n\nA tool does not need to be described in advance. It describes itself.\n\nWhen a model receives a URL, it visits that URL and finds a contract. The contract is a document that explains:\n\n- WHAT the object does (its purpose and effects).\n- ARGS (arguments) it accepts (inputs and their types).\n- EX (examples) of how to use it.\n- TESTS that verify the object behaves as described.\n\nThe model reads this contract and knows how to invoke the object. The contract is not a separate specification file (like an OpenAPI schema). It is part of the object itself, served at the URL.\n\nThe URL also carries a capability token. This token proves the model has permission to invoke the object. Without the token, the URL resolves to the contract but invocation is denied. With the token, the model can both read and invoke.\n\nAfter invocation, the model receives a receipt. The receipt is a record of what happened: what was called, with what arguments, at what time, with what result. The receipt links back to the ledger (the permanent record of all i","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[],"sources":[],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"what-is-url-is-api","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":0,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":0,"claims_total":0,"sources":0,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}