What authentication does the Waste Services API require?

The spec defines no security scheme - the API is treated as public read for service and task data. Some council deployments may front the API with their own gateway requiring an API key; check the council-specific deployment URL if 401 responses appear.

Can I look up bin collection dates for a UK address?

Yes. Resolve the address to a UPRN, call GET /sites/{id} to confirm the site exists, then GET /tasks filtered by that site to return upcoming collection dates with their service type.

How do I report a missed bin collection?

POST /cases creates a new service case. Include the site reference, the eventTypeId for 'missed collection' (look it up via GET /event-types), and a description. The council receives the case in its waste system.

What are the rate limits for the Waste Services API?

No public rate limit is documented in the spec. In practice individual council deployments may throttle requests; cache site and feature-type lookups, which change rarely, and back off on 429 responses.

How do I look up a bin schedule through Jentic?

Search Jentic for 'look up uk bin collection schedule', load the schema for GET /tasks, and execute with a site reference. The Jentic Python SDK pattern is await client.search(...), await client.load(...), await client.execute(...).

Can I limit what my agent is allowed to do with the Waste Services API?

Yes. Because you run Jentic One yourself, your own rules decide which Waste Services operations and inputs the agent may use. You can allow read-only lookups like GET /sites/{id}, GET /services, and GET /tasks while leaving case creation via POST /cases out unless you add it. Since the site id travels in the URL path, you can also pin the agent to a specific site so it reads only the collection data you intend.