What authentication does the Cloverly Carbon Offset API use?

The Cloverly API uses an HTTP bearer scheme: the API key is sent as a Bearer token in the Authorization header. Through Jentic the key is stored encrypted in the vault and applied at execution time, so the agent never sees the raw token.

Can I estimate a shipping offset before charging the customer?

Yes. POST /estimates/shipping with the parcel weight, origin, and destination returns an estimate including price and the corresponding verified offset. The estimate is held under a slug, and you can convert it into a purchase via POST /purchases/shipping when the customer confirms.

What carbon-producing activities can I offset with the Cloverly Carbon Offset API?

Four parallel flows are supported: shipping (/estimates/shipping and /purchases/shipping), vehicle transport (/estimates/vehicle, /purchases/vehicle), raw carbon weight (/estimates/carbon, /purchases/carbon), and currency-based (/estimates/currency, /purchases/currency).

What are the rate limits for the Cloverly Carbon Offset API?

The OpenAPI specification does not declare explicit rate limit headers or a 429 response. Cloverly applies plan-based limits documented in its developer portal, and high-volume integrations should batch estimates per cart rather than per item. Through Jentic, retries and backoff are handled by the SDK.

How do I purchase a carbon offset through the Cloverly API via Jentic?

Install the SDK with pip install jentic, search for 'purchase a carbon offset', load the cloverly.com /purchases/shipping (or /purchases/vehicle, /purchases/carbon, /purchases/currency) operation, and execute it with the slug from a prior estimate. Jentic supplies the Bearer token automatically and returns the purchase receipt.

Can I cancel an estimate or a purchase?

Estimates and purchases each support DELETE /estimates/{slug} and DELETE /purchases/{slug} for cancellation. Cancellation rules and timing depend on whether the underlying credits have been retired, which is reflected in the response.

Can I limit what my agent is allowed to do with the Cloverly Carbon Offset API?

Yes. Because you run Jentic One yourself, your own rules decide which Cloverly operations and credentials the agent may use. Cloverly carries no resource id in the URL path, so you scope the agent to the exact operations it needs, such as estimating a shipping or carbon offset, and leave the rest out. Purchase operations like POST /purchases/carbon and cancellations like DELETE /purchases/{slug} are excluded unless you explicitly add them.