For agents
These docs are built to be read by software as well as people. Every page has a markdown twin, there is a skill you can drop into a coding agent, and the whole corpus is available as one file.
The skill
skill.md is a single file of instructions for a coding agent: the base URL, the authentication header, the endpoints, and the rules for reading a result. Give it to an agent and it can screen an address without you explaining the API.
For Claude Code, put it where skills live:
mkdir -p ~/.claude/skills/zscreen
curl -o ~/.claude/skills/zscreen/SKILL.md https://zscreen.zeruai.org/skill.mdFor anything else, paste the file into the system prompt or attach it as context. It is plain markdown with no dependencies.
The skill leads on the one rule that matters: a response without a verdict is not a clean wallet. An agent that treats a queued or refused answer as CLEAR is the failure this product exists to prevent, so the skill states it before it states anything else.
Every page as markdown
Add .md to any docs URL and you get the same page as markdown, without the navigation or the styling. Cheaper for a model to read, and it is generated from the page itself, so it cannot fall out of step with what you see here.
https://zscreen.zeruai.org/docs.md
https://zscreen.zeruai.org/docs/endpoints.md
https://zscreen.zeruai.org/docs/limits.mdEvery page also declares its twin with <link rel="alternate" type="text/markdown">, so a crawler finds it without guessing.
Copy page
Copy pageat the top of any page puts that page's markdown on your clipboard, ready to paste into a model. View as Markdown opens it instead. Both use the same file a crawler would read, so what you paste is what the machine sees.
The whole corpus
llms.txt indexes the documentation, with the base URL, the authentication header and the response rules at the top. llms-full.txt is every page concatenated, for when you want to hand over the lot in one go.
curl https://zscreen.zeruai.org/llms.txt # the index
curl https://zscreen.zeruai.org/llms-full.txt # every page, one fileTools instead of HTTP
If your client speaks Model Context Protocol, it can call zScreen as tools rather than reading these docs and writing requests. See MCP server.