documentation
cache.directory API documentation
Use this cache.directory API documentation to call the public JSON catalog, discover operations from OpenAPI, and throttle with standard rate-limit headers. The same material lives under /developers for name-based search queries for “cache.directory developer resources”.
Authentication
Public read endpoints do not use API keys. Send a normal HTTPS GET. There is no OAuth, no sandbox key, and no paid API tier. Unknown methods return JSON 405. Private operator tooling is not on this origin.
Endpoints
Canonical operations are listed in the cache.directory OpenAPI specification. Function-calling clients should import that document and use the operationId values getHealth, searchCatalog, listShelf, resolveEntry, getRawArtifact, getOpenApiDocument, and getOpenApiYaml.
Example request
curl -s https://cache.directory/api/health
returns JSON with status, service, and timestamp.
curl -s https://cache.directory/api/v1/skills.json
returns the skills shelf.
curl -s -o /dev/null -w "%{http_code}" https://cache.directory/api/v1/does-not-exist
returns 404 with JSON error.code, error.message, and error.resolution instead of an HTML page.
Markdown pages: curl -sH "Accept: text/markdown" https://cache.directory/docs.
Rate-limit convention
Successful and error API responses include RateLimit, RateLimit-Policy, X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset. A 429 also includes Retry-After. The public window is 60 requests per 60 seconds per IP.