How Caper approaches this Eve…ther than an exception to it. Verified live on 17 AugustRead again on 23 October 2026: caper.network/llms.txt…k/llms.txt) returns the index, and llms-full.txt (https://is the only one since caper.network/ removed llms-full.txt) the, its whole-corpus file, on 21 October 2026; every wiki page also answers…list call to /api/mcp returns thirsixteen tools (eightnine reading, five behind atwo for the ROLA-signed token-in and five that need the token it returns) and the per-DAO endpoint at … agent asking quote_swap what 1,000 XRDa trade of a given size buys is not reading a number …rs suggest is hardest to keep.

How Caper approaches this Eve…ather than an exception to it.Verified live on 17 August 202…mitted rather than left empty.From 17 August 2026 this page …rs suggest is hardest to keep.

How Caper approaches this Eve… one. Still standing: a caper with no members or proposals yet ships members: [],ships proposals: [] and activityLog: [] in its dao.json, where the specification says an empty field should be omitted – reproduced on 17 August 2026 against $XRD field with no value should be omitted rather than left empty. From 17 August 2026 this page reproduced that against /capers/XRD/dao.json, then the one caper in the directory with no members; the genesis redeploy of 18 September 2026 (/wiki/markets/trading) removed that caper, and the URL has returned 404 since. Read again on 20 September 2026, the $CAPER document (https://caper.network/capers/XRDCAPER/dao.json) , the one caper in the directory with zero members is 2,072 bytes carrying three members, seven contracts and both other arrays empty, so the empty arrays do not depend on a caper being new: the route emits them for any field with nothing in it. What does hold is the fourt…rs suggest is hardest to keep.

The surface DAOs already have:…les above links to it as data. The grants layer has gone the same way. Karma (/wiki/dao-governance/tooling/analytics/karma) published agent skills (https://github.com/show-karma/skills) in March 2026 so an agent can find funding opportunities, create a project and post milestone updates without opening the site, and its research tool over US nonprofit filings answers over MCP inside ChatGPT or Claude ( Karma (https://www.karmahq.org/blog/karma-skills-making-the-entire-karma-platform-agent-friendly) ; Karma (https://www.karmahq.org/blog/karma-for-philanthropic-funding) ). For a DAO that runs a grants programme on such a platform, the machine-readable surface for its funding is the vendor's, on the vendor's terms.

The surface DAOs already have: Snapshot's API The machine-readable governance record most DAOs already have is one they do not publish themselves. Snapshot (/wiki/dao-governance/tooling/voting/snapshot) 's public GraphQL API returns every space's settings, proposals and votes, and it was answering 540 million requests a month in 2023, when Snapshot put it behind keys to stop runaway bots taking it down ( Snapshot Labs (https://paragraph.com/@shot/introducing-api-keys-to-the-hub-graphql-api) ). Keyless callers now get 100 requests a minute and keyed callers 200,000 a month, a tenth of the 2 million a month offered when keys were introduced ( Snapshot docs (https://docs.snapshot.box/tools/api/api-keys) , read 19 September 2026). A second API at api.snapshot.box serves Governor and Snapshot X proposals, votes and execution history from one schema, and its indexer can be self-hosted ( sx-monorepo (https://github.com/snapshot-labs/sx-monorepo/tree/master/apps/api) ). Snapshot's MCP server wraps the same data for agents. For most DAOs, then, the readable governance surface exists already, is run by their voting vendor, and is rate-limited by that vendor. None of the eighteen llms.txt files above links to it as data.

How Caper approaches this Eve…ms.txt (https://caper.network/wiki/capers/CAPER/llms.txt) and its own …o.json (https://caper.network/wiki/capers/CAPER/dao.json) ; there is an…) and the per-DAO endpoint at /wiki/capers/{cashtag}/mcp returns eight, includingthree, all of them chain reads: get_ledger for treasury, time… $XRD (https://caper.network/wiki/capers/XRD/dao.json) , the one caper…rs suggest is hardest to keep.

How Caper approaches this Eve…tion to it. Verified live on 127 August 2026: caper.network/l…aper.network/.well-known/agent-card.json) and an OpenAPI docume…list call to /api/mcp returns eight tools,thirteen tools (eight reading, five behind a ROLA-signed token) and the per-DAO endpoint at /…i/caper/{cashtag}/mcp returns sixeight, including get_ledger for tre…, grants and inter-DAO funding. Two, get_market for live price and supply, and quote_swap, which prices a hypothetical trade of a given size against that DAO's own bonding curve. The full surface is documented at Querying a caper from an AI agent (/wiki/foundations/querying-a-caper-from-an-ai-agent) . That last tool is the sharpest illustration of the endpoint-versus-document argument, because there is no document that could carry it. An agent asking quote_swap what 1,000 XRD buys is not reading a number someone published; it is running the curve. A file cannot answer a question whose answer depends on the size of the question. One honest deductions still applyies against the standard set out above., and one has been retired. Retired: this page previously recorded that Caper's agent card sitsat only at the legacy /.well-known/agent.json path, sowhere a spec-compliant A2A 1.0.0 client willould not find it – the sam. Re-probed on 17 August 2026, /.well-known/agent-card.json (https://caper.network/.well-known/agent-card.json) returns the identical 4,501-byte document, so the defect the July 2026 survey … 15 of the 65 cards it located. And no longer describes this one. Still standing: a caper with no members or proposals yet ships members: [] and, proposals: [] and activityLog: [] in its dao.json, where the sp… empty field should be omitted – reproduced on 17 August 2026 against $XRD (https://caper.network/wiki/caper/XRD/dao.json) , the one caper in the directory with zero members. What does hold is the fourt…rs suggest is hardest to keep.

Topic How a DAO publishes itself to software rather than to people The four surfaces daoURI() / EIP-4824 · /llms.txt · A2A agent card at /.well-known/agent-card.json · Model Context Protocol server Lineages An Ethereum ERC (2022) · a community proposal by an AI researcher (2024) · a Linux Foundation agent protocol (2025) · an open protocol from an AI lab (2024) Census (12 August 2026) Of the 70 organizations in this wiki's DAO directory (/wiki/daos) that publish a website, 66 answered a clean probe: 18 serve /llms.txt, 1 serves an MCP server card, 0 serve an A2A agent card What none of them publishes Live governance state. Not one of the 18 llms.txt files names a live proposal, a member, or a treasury balance The shared failure mode Every surface is an off-chain pointer that somebody has to keep paying to host Related EIP-4824 (/wiki/dao-governance/concepts/analysis/eip-4824) · DAOstar (/wiki/dao-governance/tooling/analytics/daostar) · DAO tooling discontinuity (/wiki/dao-governance/concepts/analysis/dao-tooling-discontinuity) · DAO metrics and analytics (/wiki/dao-governance/concepts/analysis/dao-metrics-and-analytics)

A DAO (/wiki/dao-governance/concepts/fundamentals/what-is-a-dao) that nobody can read is, for most practical purposes, a private company with a public ledger. Its members exist as addresses in a contract, its decisions as calldata, its treasury as balances no outsider can attribute. The gap between "the data is on-chain" and "a stranger can read the organization" is filled by a description the organization publishes about itself – and increasingly, that description is written for software rather than for people. Four such surfaces now exist, and they arrived from four unrelated directions. One came out of DAO governance itself. One came from an AI researcher's blog post. One came from an agent-interoperability working group. One came from a model vendor's protocol. None of them was designed with the other three in mind, none of them supersedes the others, and a DAO wanting to be legible to machines in 2026 has to decide, without much guidance, which of them to publish. This page describes the four, then reports a census: on 12 August 2026, every organization in this wiki's DAO directory (/wiki/daos) was probed for all four. The results are the useful part, and they are not what the volume of writing about agentic infrastructure would lead you to expect.

Four surfaces, four lineages daoURI() and the DAOIP family. The oldest and the only one built for DAOs specifically. EIP-4824 (/wiki/dao-governance/concepts/analysis/eip-4824) , authored through DAOstar (/wiki/dao-governance/tooling/analytics/daostar) and created in February 2022, defines a single on-chain function that returns a URI pointing at a JSON-LD (https://www.w3.org/TR/json-ld11/) document listing the DAO's members, proposals, activity log, governance rules, and contracts. It is the only one of the four whose vocabulary is about governance: it has a field for a proposal's on-chain calls, and a field for who voted. It is also the only one with an on-chain discovery mechanism, an index contract that emits a registration event. Four and a half years after creation it still carries the status Review (https://eips.ethereum.org/EIPS/eip-4824) , and a census of its four production index deployments found 30 registrations, the most recent in February 2025. /llms.txt. Proposed by Jeremy Howard in September 2024 (https://llmstxt.org/) , this is a Markdown file at a site's root whose only mandatory element is an H1 with the project name. Everything else – a blockquote summary, prose sections, H2-delimited lists of links with one-line notes – is optional. It is explicitly a community proposal rather than a standard: no registry, no validator, no conformance suite. What it has instead is reach. Its own documentation notes that thousands of sites publish one, that OpenAI, Anthropic and Google ship them for their documentation, and that Chrome's Lighthouse now audits for it. It says nothing about governance because it says nothing about anything in particular – it is a table of contents for a language model. The A2A agent card. The Agent2Agent protocol (https://a2a-protocol.org/latest/specification/) , now published under the Linux Foundation, defines an AgentCard object served at a registered well-known URI. The registration entry names the suffix agent-card.json, with the A2A Protocol Working Group as change controller. The card declares what an agent can do, what protocols and authentication it supports, and what skills it exposes. The path is itself a migration hazard: version 0.3 renamed it from /.well-known/agent.json, and a spec-compliant 1.0.0 client will not look at the old location. An MCP server. The Model Context Protocol (https://modelcontextprotocol.io/specification/latest) is the most capable of the four and the least like a file. Instead of publishing a document, an organization runs a JSON-RPC endpoint that exposes tools, resources and prompts, so an agent asks questions rather than downloading a snapshot. That difference matters for a DAO: a document describes the treasury as it stood when the document was generated, while a tool answers about the treasury now.

The census: what DAOs actually publish The four surfaces are cheap to probe, so on 12 August 2026 every organization in this wiki's DAO directory (/wiki/daos) was checked for all of them. The directory holds 71 organizations, 70 of which record a website ( ConstitutionDAO (/wiki/daos/social/constitutiondao) , dissolved in 2021, does not). Each domain was requested at /llms.txt, /.well-known/agent-card.json, /.well-known/agent.json and /.well-known/mcp.json under a browser user-agent, following redirects. The probe needs one discriminator to be worth anything. Most of these sites are single-page applications that answer every path with HTTP 200 and their own HTML shell, so a naive status check reports a file that does not exist. The test used here is the response's content type: a real llms.txt comes back as text/plain, a real agent card as application/json, and the SPA fallback as text/html. As a control, each positive was re-probed at a nonsense path (/llms-caper-control-9f3a.txt); fifteen returned 404 and three – yearn.fi, rocketpool.net and cosmos.network – returned 200 with text/html, exactly the behaviour the content-type test is there to catch. Four domains could not be resolved either way and are excluded from the denominators: balancer.fi returned HTTP 429, sky.money and jito.network returned Cloudflare 403 challenges, osmosis.zone answered the well-known path with a redirect loop, and ether.fi returned HTTP 500 for /llms.txt. That leaves 66 organizations that answered cleanly. Surface Published Of 66 answering /llms.txt 18 27% MCP server card at /.well-known/mcp.json 1 1.5% A2A agent card (either path) 0 0% The eighteen serving /llms.txt are 1inch, Aragon, Cosmos Hub, Kleros, Lido, Maple Finance, Ondo Finance, Pendle, Polygon, Rocket Pool, Safe, The Graph, THORChain, Euler, Helium, Starknet, The LAO and Yearn. The zero for agent cards is not an artefact of the probe: thirteen domains returned HTTP 200 for one of the two agent-card paths, and all thirteen were the SPA HTML shell. That result is consistent with the wider web. A survey published on 29 July 2026 (https://apievangelist.com/2026/07/29/most-published-agent-cards-are-not-actually-a2a/) probed 22,341 hosts drawn from the APIs.io catalogue, of which 20,185 answered, and found 65 serving any agent card at all – 0.29 percent – of which only 10 passed every structural check in the A2A 1.0.0 AgentCard object, and 15 were still sitting at the pre-0.3 agent.json path.

The one MCP endpoint, examined The single MCP result is worth reading closely, because it shows how thin the line between publishing a surface and operating one can be. THORChain (/wiki/daos/dexs/thorchain) serves a well-formed server card at thorchain.org/.well-known/mcp.json declaring a read-only endpoint named thorchain-public-discovery, three tools (get_site_summary, get_agent_rules, list_public_api_references), no required authentication, and an HTTP transport at thorchain.org/mcp. It also serves an AGENTS.md at its root describing the rules it asks AI clients to follow – a fifth convention, and one no other organization in the directory publishes either. Two details qualify it. The card's $schema points at modelcontextprotocol.io/schemas/server-card/v1.0, which returns 404 – the MCP specification, revision 2026-07-28, defines a wire protocol and a registry, not a well-known server-card URI, so this is a convention the publisher has adopted rather than a spec it conforms to. And a JSON-RPC initialize posted to the declared endpoint returns the site's HTML, not a protocol response: /mcp serves the same static document as the well-known path. THORChain has published discovery metadata for an MCP server. It has not, as of this probe, put a live MCP server behind it. That is not a criticism so much as a measurement of where the field is. The most agent-forward organization in a 70-strong directory of the largest DAOs in existence has shipped a JSON file and a Markdown file describing an interface that does not yet answer.

What the published files say – and what they leave out The more revealing finding is not the count but the content. All eighteen llms.txt files were retrieved and read. Every one of them is a product summary. They describe what the protocol does, list the documentation, and point at the app. Not one names a live proposal. Not one lists a member or a delegate. Not one states a treasury balance. Four of the eighteen link a governance venue at all – Cosmos Hub to forum.cosmos.network, Euler to its forum plus Snapshot (https://snapshot.org/#/eulerdao.eth) and Tally (https://www.tally.xyz/gov/euler) , Kleros to its forum and Snapshot space, Yearn to gov.yearn.fi – and in every case the link is to the venue's human-facing front page, not to a machine-readable proposal list. Seven files mention the words proposal, treasury, voting or delegate anywhere; the mentions are almost all links to marketing pages about a governance token. One of the eighteen is not even a deliberate act of publication. Starknet's file opens with a byte-order mark and the line "Generated by Yoast SEO v27.3, this is an llms.txt file, meant for consumption by LLMs" – it is the output of a WordPress SEO plugin, an artefact of the marketing site rather than a decision by the organization. Put together with the EIP-4824 (/wiki/dao-governance/concepts/analysis/eip-4824) registry, which is the one surface with governance vocabulary and has 30 registrations across its entire history, the pattern is consistent: the surfaces that describe governance are barely adopted, and the surface that is adopted describes the product. An agent that reads every machine-readable file the largest DAOs publish will come away able to explain how to swap a token and unable to say who decides anything.

The failure mode all four share Each of the four surfaces resolves, in the end, to a hostname. daoURI() stores a pointer on-chain and the document lives off it. llms.txt is a file on a web server. An agent card is a file on a web server at a more specific path. An MCP endpoint is a running service, which is the same dependency plus a process that has to stay up. This is the single structural weakness the whole category inherits, and it is not hypothetical. The EIP-4824 registry is the worked example: an immutable on-chain pointer, registered once, aimed at an off-chain document that eventually stopped answering, with nobody obliged to notice. It is the same mechanism documented on DAO tooling discontinuity (/wiki/dao-governance/concepts/analysis/dao-tooling-discontinuity) – a DAO's legibility outsourced to infrastructure that runs on somebody's renewal cycle, and quietly ends when a grant does. The asymmetry is what makes it dangerous rather than merely annoying. The pointer is durable; the thing it points at is not. A registration event from 2023 sits on Ethereum forever, advertising a description that has been gone for a year, and there is no on-chain signal that distinguishes the two states. Anyone specifying the next such standard has an obvious lesson available: a pointer with no liveness check is a claim, not a fact (/wiki/dao-governance/concepts/analysis/dao-metrics-and-analytics) .

What a DAO that wants to be readable should actually do The census supports a short, unglamorous set of conclusions. - Publish llms.txt, but do not mistake it for governance transparency. It is the cheapest of the four, it has real reach, and 27% of the largest DAOs already have one. It is also, as published today, a marketing artefact. A DAO can distinguish itself here almost for free by including what everyone else omits: the governance forum, the voting venue, the treasury address, and the proposal list, as links a machine can follow. - Treat the agent card as unclaimed ground. Zero adoption across 66 major DAOs, and 0.29% across 20,185 hosts on the wider web, means the format is early rather than settled. If a DAO publishes one, publish at /.well-known/agent-card.json, since a 1.0.0 client will not read the legacy path. - An endpoint beats a document for anything that changes. Treasury balances, open proposals and vote tallies are stale the moment a file is written. This is the argument for MCP over any of the file formats, and the reason the one published MCP card in the directory is more interesting than the eighteen files. - Prefer surfaces whose underlying data survives the host. A description that is generated on request from chain state can be re-created by anyone from the chain. A description that was written once and uploaded cannot.

How Caper approaches this Every caper (/wiki/foundations/what-is-a-caper) is a DAO, and the platform publishes all four surfaces – which makes it a fair test of the argument above rather than an exception to it. Verified live on 12 August 2026: caper.network/llms.txt (https://caper.network/llms.txt) returns the index and llms-full.txt (https://caper.network/llms-full.txt) the whole corpus; every wiki page also answers at its own URL with a .md suffix as text/markdown; each DAO has its own per-DAO llms.txt (https://caper.network/wiki/caper/CAPER/llms.txt) and its own EIP-4824 dao.json (https://caper.network/wiki/caper/CAPER/dao.json) ; there is an agent card (https://caper.network/.well-known/agent.json) and an OpenAPI document (https://caper.network/.well-known/openapi.json) ; and the MCP endpoints are live rather than declared – a tools/list call to /api/mcp returns eight tools, and the per-DAO endpoint at /wiki/caper/{cashtag}/mcp returns six, including get_ledger for treasury, timeline, grants and inter-DAO funding. Two honest deductions apply against the standard set out above. Caper's agent card sits at the legacy /.well-known/agent.json path, so a spec-compliant A2A 1.0.0 client will not find it – the same defect the July 2026 survey found in 15 of the 65 cards it located. And a caper with no members or proposals yet ships members: [] and proposals: [] in its dao.json, where the specification says an empty field should be omitted. What does hold is the fourth conclusion. Every one of those documents is generated from ledger and platform state on request rather than stored, so there is no snapshot to go stale, and the data underneath is Radix component state: the members, the proposals, the votes and the treasury exist on-ledger whether or not caper.network serves anything at all. If the site stopped answering tomorrow, what would be lost is the convenience of the common interface, not the record. That is a narrower promise than "the DAO is machine-readable", and it is the part of the promise the last four years suggest is hardest to keep.

References - Joshua Tan, Isaac Patka, Ido Gershtein, Eyal Eithcowich, Michael Zargham, and Sam Furter (2022). ERC-4824: Common Interfaces for DAOs (https://eips.ethereum.org/EIPS/eip-4824) . Status: Review. See also this wiki's page on the standard (/wiki/dao-governance/concepts/analysis/eip-4824) and its registry census. - Jeremy Howard. The /llms.txt file (https://llmstxt.org/) – proposal, format, and adoption notes. - A2A Protocol. Agent2Agent (A2A) Protocol Specification (https://a2a-protocol.org/latest/specification/) , published under the Linux Foundation; section 14.3 registers the agent-card.json well-known URI suffix. - Kin Lane. Most Published Agent Cards Are Not Actually A2A (https://apievangelist.com/2026/07/29/most-published-agent-cards-are-not-actually-a2a/) , API Evangelist, 29 July 2026 – the 22,341-host / 65-card / 10-conformant survey. - Anthropic and contributors. Model Context Protocol specification (https://modelcontextprotocol.io/specification/latest) , revision 2026-07-28. - THORChain. MCP server card (https://thorchain.org/.well-known/mcp.json) and AGENTS.md (https://thorchain.org/AGENTS.md) . - Directory census (12 August 2026): all 70 websites recorded in this wiki's DAO directory (/wiki/daos) probed at /llms.txt, /.well-known/agent-card.json, /.well-known/agent.json and /.well-known/mcp.json under a browser user-agent with redirects followed; positives re-probed at a control path and separated from single-page-application fallbacks by response content type; all 18 llms.txt files retrieved and read in full.