API and MCP documentation
The catalogue provides read-only, public interfaces for people and software. No API key is required. All URLs below are relative to this site and use HTTPS in production.
Start here
- Dataset metadata (JSON-LD) — identifier, licence, provenance and distributions.
- OpenAPI 3.1 contract — machine-readable REST interface.
- MCP Streamable HTTP endpoint — tools for MCP clients.
- llms.txt — concise integration index.
REST API
Use GET /api/v1/search?q=diazinon&mode=text for lexical search. mode may be text, semantic or hybrid; use category, active, crop, pest, formulation, registrant, poison_schedule and status to refine results. Repeating a filter parameter selects multiple values.
Get a record at GET /api/v1/products/{product-number}. Use the numbered-and-slugged product subresources documented in OpenAPI for uses, accessible-label pages and retained history. Responses are JSON, include ETags for conditional requests, and include source and validation context.
HTML, JSON and RSS
Public HTML product, use, label and browse pages have JSON twins: append .json to the page URL. Any search result can be subscribed to by replacing /search with /search.rss and retaining its query parameters. A product page also offers an RSS link while label processing is pending.
MCP
Connect an MCP client to /mcp using Streamable HTTP. Available tools include search_products, get_product, get_use, get_withholding_periods, get_label_section, compare_products, similar_products, get_permit and dataset_status. Tool results contain a provenance envelope; quote label facts with their source pages and never treat catalogue output as a spray recommendation.
Reuse and operational expectations
Attribute APVMA PubCRIS as required by its CC BY 3.0 AU licence. Keep source URLs, retrieval timestamps and label-page references when redistributing facts. Respect HTTP cache validators and do not scrape labels through this service. For legal, safety or regulatory decisions, consult the original APVMA record and approved label.