How do I get a delivery quote and dispatch the chosen carrier?

POST /quote with pickup and dropoff addresses to receive multi-carrier rates. After choosing one, POST /delivery_information to create the delivery and POST /initiate_delivery to dispatch the selected provider. Track progress with GET /delivery/{id}.

Can I cancel a Burq delivery after it has been initiated?

Yes, POST /delivery/{id}/cancel cancels the delivery. Cancellation policies and any fees depend on the underlying carrier and the current status of the delivery.

Does Burq support multi-stop routes?

Yes. POST /routes/quotes returns rates for a batch of pickups and dropoffs and POST /routes creates the route once accepted. POST /routes/{id}/cancel cancels an active route.

What are the rate limits for the Burq Delivery API?

The OpenAPI spec does not declare explicit limits. Burq publishes throttle and pricing guidance in their docs - handle 429 responses with retry-with-backoff for high-volume quote requests.

How do I dispatch a Burq delivery through Jentic?

Run `pip install jentic` and search for 'dispatch a Burq delivery'. Jentic returns the /initiate_delivery operation, you load its schema, and execute the call with the prepared delivery payload - credentials stay in your Jentic One instance.

Can I limit what my agent is allowed to do with the Burq Delivery API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which Burq operations and credentials the agent may use, so you can allow read and dispatch calls like POST /quote, POST /delivery_information, and POST /initiate_delivery while withholding destructive ones such as POST /delivery/{id}/cancel or POST /routes/{id}/cancel. Since Burq carries the resource id in the URL path, a rule can also pin the agent to a specific delivery, order, or store and nothing else. The stored x-api-key is injected only for the operations you have approved and never enters the agent's context.