FOR AGENTS & DEVELOPERS
Readable by people. Usable by agents.
Use the same structured, source-linked content that powers the website. Keep its scope and uncertainty attached.
Discover the public knowledge library
Start with /llms.txt or the OpenAPI description at /openapi.json. The read-only topic catalogue is at /api/v1/topics. Individual records are at /api/v1/topics/{id}; add ?format=markdown for text.
Each record includes its scope, official source URLs, source-check date, editorial status and practical guidance. /llms-full.txt provides the complete library in Markdown.
Preserve the boundaries
These records are source-checked drafts pending specialist editorial review. Do not describe them as professionally approved. Preserve the jurisdiction, dates, caveats and attribution when quoting or summarising.
A match to a topic is not a determination that a duty applies. Do not turn guidance about good practice into a blanket legal requirement. Do not use content from a different jurisdiction as though it applies locally.
Read-only by design
The public knowledge API does not create leads, make bookings or expose enquiry records. The browser interpretation and enquiry endpoints are first-party form endpoints, not an agent action API.
No API key is needed. Search topics with GET /api/v1/search?q=..., build a starting plan with POST /api/v1/plan, or compare supplied prices with POST /api/v1/compare. These calculation endpoints do not store your inputs or call an AI model. See the OpenAPI description for schemas and examples. Cache the versioned catalogue responsibly. Local previews are intentionally excluded from search indexing.