DropToCDN API
65
AI ReadinessAI-Aware (B)65/100
Official vendor OpenAPI document · agent-readyMediaContent DeliveryapiKey5 EndpointsREST
For 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.
Use for: Upload a file to the CDN, Get a public URL for an uploaded file, List all the files I have uploaded, Delete a file from the CDN
Not supported: Does not handle image transformation, video transcoding, or origin storage administration. Use for uploading files to a CDN and serving public URLs only.
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.
Install Jentic One Beta
Connect the DropToCDN API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DropToCDN 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdroptocdn.com%2Fdroptocdn" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdroptocdn.com%2Fdroptocdn" | 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 DropToCDN API.
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
Patterns agents use DropToCDN API for, with concrete tasks.
★ 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.
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.
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.
List the files on the account, then delete the ones whose information shows they are older than a set cutoff.
Key Endpoints
5 endpoints — the droptocdn api uploads a file to a content delivery network with a single post request and returns an instant public url for it.
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
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
Jentic AI Readiness Score
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.
D
DropToCDN API
- AI-Aware (B)65/100
72
Foundational Compliance63
Developer Experience & Jentic Compatibility54
AI-Readiness & Agent Experience94
Agent Usability50
Security70
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
72
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
89%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
54
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
60%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
56%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
70
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
70%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using DropToCDN API through Jentic.
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.
GET STARTED