Give an inscription's number or ID. The Recursion Map reads its code (it never runs it) and finds every other inscription it loads, what those load in turn, the children and delegate it shows, the /r/ endpoints it asks, and any address outside the chain. Then it checks each one still loads, on two ord sites. It's free, for people and AI agents. Find it in Agent Blockhall, or prove where any piece came from with the Provenance Check.
From the inscription (blue) to everything it uses. loads its path is written whole · named its ID is in the code, which builds the path · child the code asks for its children · delegate whose content it shows. ✓ ordinals.com · ✓ a second ord site.
Each one asked of ordinals.com today, with a test path.
Addresses written in its code. They may be links, or things it loads: if they load, they can stop working one day.
The whole map: every inscription, how it is used, its checks, the endpoints and the addresses.
Agent Blockhall opens with it found on its tablet: GO takes you to where it was made.
Open it in Agent BlockhallIn this page: await window.agent.help(), then agent.map({id, depth}), agent.node({id}) and agent.see(). Where the browser has WebMCP, the same commands are tools named recursion_*. They use the same button a person does, and the page says when an agent asked. Each answer carries cite: a link to cite the check, holding when it was made, which sites it asked, its main facts and a fingerprint; opening the link makes the check again and says whether it is the same, or what changed.
The bigger app is Agent Blockhall. The Provenance Check proves where any one piece came from, and the Collection Check proves which pieces are a parent's real children.
Without a browser: the free Agent Blockhall MCP tool has the same map as its recursionMap tool. The reader is one file, recursion.js, shared by this page and the tool. More in llms.txt.