canonical: https://jentic.com/apis/droptocdn.com/droptocdn

# DropToCDN API

The DropToCDN API uploads a file to a content delivery network with a single POST request and returns an instant public URL for it. It lists the files on an account, reads information about an individual file, and deletes a file when it is no longer needed. It can also publish raw HTML as a public web page served from the CDN, so generated assets and simple pages are reachable over a public link without running separate hosting.

## For AI agents

Upload a file to a CDN in one request and get an instant public URL, list and inspect uploaded files, delete them, and publish raw HTML as a public page. A small, focused API for serving assets over a public link.

## Scope

Does not handle image transformation, video transcoding, or origin storage administration. Use for uploading files to a CDN and serving public URLs only.

## Capabilities

- Upload a file to the CDN in a single request and receive an instant public URL
- List the files on your account and read an individual file's information
- Delete a file from the CDN when it is no longer needed
- Publish raw HTML as a public web page served from the CDN

## Use cases

### Agent asset hosting

An AI agent connected through Jentic can host the artifacts it produces: it uploads a generated image, report, or export in one request and receives a public URL it can hand back to the user or embed in a message. Because the upload is a single POST and returns the link immediately, the agent gets a shareable asset without provisioning storage or a bucket.

Example prompt: Upload a generated PDF to the CDN and return the public URL in the reply.

### Publish a generated web page

DropToCDN can take raw HTML and publish it as a public web page on the CDN, so an agent that assembles a snippet of HTML can turn it into a reachable link. This suits one-off landing pages, shareable reports, or preview pages that do not justify a full hosting setup.

Example prompt: Publish a block of generated HTML as a public web page and return its URL.

### Clean up stored assets

The file endpoints let a tool list everything on an account, read each file's information, and delete files that are no longer needed. An agent running a retention routine can list the uploaded files, identify those past a cutoff, and delete them to keep storage tidy and public links from lingering.

Example prompt: List the files on the account, then delete the ones whose information shows they are older than a set cutoff.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/files` | Upload a file and receive a public URL |
| GET | `/files` | List your files |
| GET | `/files/{id}` | Get file information |
| DELETE | `/files/{id}` | Delete a file |
| POST | `/pages` | Publish HTML as a public web page |

## Key resources

- **Files** — Upload a file, list files, read file information, and delete a file
- **Pages** — Publish raw HTML as a public web page served from the CDN

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 72 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 70 / 100
- **View full report:** https://jentic.com/apis/droptocdn.com/droptocdn/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring DropToCDN by hand means creating an API key in the dashboard, sending it in the Authorization header, and building the multipart upload and public-URL handling yourself. Through Jentic you install once, import DropToCDN from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** DropToCDN puts the file id in the URL path, so a rule can allow the upload and read operations while withholding delete. You choose the operations your agent may call, so file deletion and page publishing are not included unless you add them.
- **Credential handling:** Your DropToCDN API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'upload a file to the CDN' or 'publish an HTML page', and Jentic returns the matching DropToCDN operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudinary Upload API** — Cloudinary uploads media and serves it over a CDN, with transformation on top of DropToCDN's plain upload
- **Filestack** — Filestack handles file upload and delivery with processing, overlapping DropToCDN's upload and hosting
- **Bunny.net** — Bunny.net provides CDN and storage zones that can host larger asset libraries alongside DropToCDN
- **KeyCDN Tools** — KeyCDN tooling complements DropToCDN with CDN diagnostics and lookups

## FAQ

### What authentication does the DropToCDN API use?

The DropToCDN API authenticates with an API key sent in the Authorization header, per its OpenAPI spec, and you create the key in the dashboard settings. Every endpoint requires it. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.

### Is there a DropToCDN MCP server?

You don't need an MCP server to give your agent the DropToCDN API. Jentic connects it directly from the API Directory: import DropToCDN, store your key once, and your agent calls its operations. Operations are discovered on demand, so no extra server's tool definitions are loaded into the agent's context.

### Can I limit what my agent is allowed to do with the DropToCDN API?

Yes. Write a rule that allows only the upload and read operations, so your agent can store assets and fetch their public URLs but cannot delete files or publish pages, and every call it makes is logged. The file id travels in the URL path, so you can also scope read and delete rules to the specific files the agent should touch.

### Can I publish an HTML page with the DropToCDN API?

Yes. The pages endpoint accepts raw HTML and publishes it as a public web page served from the CDN, returning a public URL. This lets an agent turn a generated HTML snippet into a shareable link without running its own web host.

### What are the rate limits for the DropToCDN API?

This OpenAPI spec does not specify rate limits. Check your DropToCDN dashboard and documentation for the limits that apply to your plan before running bulk uploads.

### How do I upload a file with the DropToCDN API through Jentic?

Install Jentic One, import DropToCDN from the API Directory, and store your API key once. Your agent then searches by intent, for example 'upload a file to the CDN', and Jentic returns the upload operation with its input schema so the agent sends the file and reads back the public URL. To run it on your own infrastructure, install Jentic One from its GitHub repo.