Bunny CDN API
✓ Official Vendor SpecCloud InfrastructureNetworkingapiKey17 EndpointsREST
For Agents
Provision and manage bunny.net pull zones, storage zones, and video libraries, purge CDN cache, and pull traffic and billing statistics.
Use for: I need to provision a new pull zone for my origin, Create a storage zone for asset hosting, Purge a single URL from the bunny CDN cache, Wipe the cache for a specific pull zone after a deploy
Not supported: Does not handle DNS records, WAF rules, or edge compute functions — use for bunny.net pull zones, storage zones, video libraries, and cache purges only.
The Bunny CDN API manages bunny.net's content delivery infrastructure: pull zones for caching origin content, storage zones for object hosting, video libraries for video streaming, cache purge operations, and per-zone statistics and billing data. It is used by teams running bunny.net's edge network to provision new zones programmatically, push cache invalidations on deploy, and pull traffic and bandwidth numbers into internal dashboards. Authentication is a single AccessKey header keyed to the bunny.net account.
Install Jentic One Beta
Connect the Bunny CDN API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bunny CDN API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Bunny CDN API.
Create, update, and delete pull zones that cache origin content at the edge
Provision and remove storage zones for object hosting
Create and list video libraries for video streaming
Purge a single URL from the bunny.net edge cache
Purge a pull zone's full cache via /pullzone/{id}/purgeCache
Pull traffic and bandwidth statistics for the account
Retrieve account billing summary and the list of edge regions
Use Cases
Patterns agents use Bunny CDN API for, with concrete tasks.
★ Cache invalidation on deploy
Trigger CDN cache purges as part of a CI/CD pipeline so users see fresh content immediately after a deploy. The /purge endpoint targets a single URL, while /pullzone/{id}/purgeCache wipes a full pull zone. Typical usage runs a single API call per deploy and completes in under a few seconds at the edge.
After a deploy, POST /purge with the changed URL or POST /pullzone/{id}/purgeCache to wipe the entire pull zone's edge cache.
Programmatic zone provisioning
Spin up pull zones and storage zones for new tenants or staging environments without using the bunny.net dashboard. Create the pull zone pointing at the origin, optionally pair it with a storage zone for static assets, and enrol the result into your infrastructure-as-code workflow. Provisioning a new zone typically takes a single POST call.
POST /pullzone with the origin URL and zone name, then POST /storagezone if static asset hosting is also needed, capturing the returned IDs for later configuration.
Traffic and billing visibility
Pull bandwidth and traffic statistics from /statistics and the current account billing summary from /billing into internal dashboards or cost-monitoring systems. This avoids manual logins to the bunny.net portal and supports per-team or per-project chargeback when zones are tagged consistently.
GET /statistics for the current period and GET /billing to assemble a usage and cost snapshot for the account.
AI agent infra automation via Jentic
An AI agent can create a pull zone, attach a storage zone, and purge cache after a deploy as part of an end-to-end release flow. Jentic vaults the bunny.net AccessKey and issues scoped, short-lived access for each operation so the agent never holds the raw account key.
Search Jentic for 'purge bunny.net cache', load the purge schema, and execute it for the specific URL after a deploy completes.
Key Endpoints
17 endpoints — the bunny cdn api manages bunny.
METHOD
PATH
DESCRIPTION
POST
/pullzone
Create a pull zone
GET
/pullzone
List pull zones
POST
/pullzone/{id}/purgeCache
Purge a pull zone cache
POST
/purge
Purge a URL from the edge cache
POST
/storagezone
Create a storage zone
POST
/videolibrary
Create a video library
GET
/statistics
Get traffic and bandwidth statistics
GET
/billing
Get the account billing summary
POST
/pullzone
Create a pull zone
GET
/pullzone
List pull zones
POST
/pullzone/{id}/purgeCache
Purge a pull zone cache
POST
/purge
Purge a URL from the edge cache
POST
/storagezone
Create a storage zone
POST
/videolibrary
Create a video library
GET
/statistics
Get traffic and bandwidth statistics
GET
/billing
Get the account billing summary
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The bunny.net AccessKey is stored encrypted in the Jentic vault. Agents receive a scoped, short-lived token per operation, so the raw account key never enters the agent's context.
Intent-based discovery
Agents search Jentic by intent (e.g., 'purge bunny.net cache') and Jentic returns the matching /purge or /pullzone operation with its full request schema, so the agent calls the correct endpoint without reading bunny.net docs.
Time to first call
Direct bunny.net integration: half a day to a day for AccessKey handling and zone wiring. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Bunny CDN API through Jentic.
What authentication does the Bunny CDN API use?
The API uses an AccessKey header — the account API key generated in the bunny.net dashboard. Through Jentic, the AccessKey is stored encrypted in the vault and a scoped, short-lived token is issued per operation so the raw account key never enters the agent's context.
How do I purge a single URL from the bunny.net edge cache?
POST /purge with the URL you want to invalidate. For a full pull zone purge, POST /pullzone/{id}/purgeCache. Both calls return immediately and propagate through the edge network within seconds.
Can I create a pull zone programmatically?
Yes — POST /pullzone with the zone name and origin URL. The response includes the zone ID, which you then reference for subsequent updates, deletions, or cache purges.
Does the Bunny CDN API expose video streaming?
Yes. The /videolibrary endpoints create and list video libraries used by bunny.net Stream. Use POST /videolibrary to provision a new library and GET /videolibrary/{id} to retrieve its configuration.
What are the rate limits for the Bunny CDN API?
The OpenAPI spec does not declare explicit limits. bunny.net documents account-level throttles in their dashboard — implement 429 retry-with-backoff for batch operations such as bulk pull zone provisioning.
How do I purge bunny.net cache through Jentic?
Run `pip install jentic` and search for 'purge bunny.net cache'. Jentic returns the /purge operation, you load its schema, and execute the call with the URL — the AccessKey is supplied from the Jentic vault automatically.
GET STARTED