Skip to content
ZIP.tools

Agent guide: reading ZIP.tools

When to use this site: retrieve a numbered Zcash Improvement Proposal, inspect a draft, find the proposals grouped under a network upgrade, or follow proposal citations from a pinned source snapshot. Use /zips for the proposal index, /zip/NUMBER for numbered proposals, /draft/SLUG for drafts, and /nu/ID for an upgrade. This is a reference service, not a wallet, transaction broadcaster, consensus authority, or live blockchain-data source.

Send GET with Accept: text/markdown to any public reference URL for Markdown. Appending .md also selects Markdown without a special header. Requests for HTML keep the normal website. Long documents have numbered parts: follow the part links in the response and preserve the ?part=N query when citing a part. These are parts of the same proposal, not different source revisions. Follow citation and footnote links across parts to collect the whole context.

The proposal response includes status, owners, source links, and the snapshot commit. Cite the canonical page and identify the snapshot when freshness matters. A correct HTTP 404 with a recovery link means the requested proposal or part is absent. The XML sitemap lists public canonical pages. /llms.txt is the short discovery guide. The graph's text list and Markdown response expose citation relationships without requiring WebGL. Reading-list entries are browser-local and cannot be retrieved by sharing /list alone.

The optional supporting API is documented at /openapi.json and discovered through /.well-known/api-catalog. It exposes aggregate popularity, a browser reading counter, and an optional summary endpoint that is currently disabled. Reference reading does not require these endpoints. Send X-API-Version: 1, or omit the header to use version 1. Unsupported versions return a structured 400 response. Incompatible changes require a new version; if retirement is scheduled, responses will publish Deprecation and Sunset headers. No retirement is currently scheduled. API errors use application/problem+json with a stable code and recovery guidance. There is no application-level request quota; the reading counter suppresses repeats rather than returning a rate-limit error. Cloudflare infrastructure protections can still reject requests.

Repository and issue tracker · Browse proposals · Agent discovery guide · Supporting API contract