cdnjs API
★ Only Publicly Available OpenAPI DocumentDeveloper ToolsPackage Registrynone5 EndpointsREST
For Agents
Browse and look up the cdnjs library catalogue — find a JavaScript or CSS library version, retrieve its files with SRI hashes, and read CDN statistics.
Use for: I need to find the latest version of a JavaScript library on cdnjs, Get all files for a specific version of a library with their SRI hashes, Search the cdnjs catalogue for a library by name, Retrieve metadata for the React library on cdnjs
Not supported: Does not handle package publishing, dependency resolution, or private CDN hosting — use for browsing the public cdnjs library catalogue and retrieving file metadata only.
Jentic publishes the only available OpenAPI specification for the cdnjs API, keeping it validated and agent-ready. cdnjs is a free public CDN for open source JavaScript and CSS libraries operated by Cloudflare. The API exposes endpoints for browsing the full library catalogue, fetching metadata for a specific library or version, retrieving file lists with SRI hashes, and reading CDN statistics. There is no authentication — the service is open and read-only.
Install Jentic One Beta
Connect the cdnjs API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the cdnjs 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 cdnjs API.
Browse the full cdnjs library catalogue with optional name search
Fetch metadata for a specific library, including all available versions
Retrieve a library version's file list with subresource integrity hashes
Read the file extension whitelist that cdnjs accepts
Read public CDN traffic and request statistics for cdnjs
Use Cases
Patterns agents use cdnjs API for, with concrete tasks.
★ Library Version Discovery for Build Tooling
Build tools and dev assistants use the cdnjs API to find the latest version of a library and pin it in HTML script tags. The agent calls the libraries endpoint with the library name, reads the latest field, and emits a script tag with the matching SRI hash for safer in-browser inclusion.
GET /libraries/jquery and emit the latest version's CDN URL with its SRI hash
SRI-Verified Asset Inclusion
Security-conscious teams require subresource integrity hashes on every CDN-loaded asset. The cdnjs API returns SRI hashes for every file in a versioned library, so an agent can render correct integrity attributes in HTML or templating systems without manual hash computation.
GET /libraries/bootstrap/5.3.0 and return the script tag for bootstrap.min.js including its sri hash as the integrity attribute
Catalogue Search and Library Recommendation
An assistant helping developers pick a charting or UI library searches the cdnjs catalogue for matching libraries, returns the top hits, and shows version counts and last-update times. The libraries endpoint accepts a search query string and returns a paginated listing for further inspection.
GET /libraries?search=chart and summarise the top three charting libraries by version count
AI Agent Integration via Jentic
A web build assistant uses Jentic to call cdnjs operations as part of a longer workflow that also touches package registries and bundler configs. Jentic standardises the call pattern so the agent doesn't keep its own ad-hoc HTTP client for each API.
Use Jentic to search 'find a JavaScript library version on cdnjs', load the schema for /libraries/{library}, and execute for 'react'
Key Endpoints
5 endpoints — jentic publishes the only available openapi specification for the cdnjs api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/libraries
Browse and search libraries
GET
/libraries/{library}
Get a specific library
GET
/libraries/{library}/{version}
Get a specific library version
GET
/whitelist
Get file extension whitelist
GET
/stats
Get CDN statistics
GET
/libraries
Browse and search libraries
GET
/libraries/{library}
Get a specific library
GET
/libraries/{library}/{version}
Get a specific library version
GET
/whitelist
Get file extension whitelist
GET
/stats
Get CDN statistics
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
cdnjs requires no credentials. Jentic still routes the call through a single execution path so usage is observable and an agent's request pattern can be governed centrally.
Intent-based discovery
Agents search Jentic by intent (e.g., 'look up a JavaScript library version') and Jentic returns the cdnjs /libraries operation with its input schema, so the agent doesn't have to remember the path shape.
Time to first call
Direct cdnjs integration: under an hour for the basic call. Through Jentic: a few minutes — search, load schema, execute. The win is consistency across many APIs in the same agent.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using cdnjs API through Jentic.
Why is there no official OpenAPI spec for the cdnjs API?
cdnjs publishes a documentation site but not a structured OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call cdnjs API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the cdnjs API use?
The cdnjs API is open and requires no authentication — the spec declares no security schemes. Through Jentic, calls are still routed via a single execution path so request volume can be tracked and fair-use limits applied.
Can I get SRI hashes for library files?
Yes. GET /libraries/{library}/{version} returns the file list for that version, with each entry including its sri field. You can paste the hash directly into a script or link tag's integrity attribute.
What are the rate limits for the cdnjs API?
cdnjs does not publish a hard rate limit. The service is operated as free public infrastructure by Cloudflare and applies fair-use throttling at the edge — keep traffic reasonable and back off on 429s.
How do I look up a library version through Jentic?
Search Jentic for 'look up a cdnjs library version', load the schema for GET /libraries/{library}, and execute with the library name. The response includes every published version and the latest pointer.
Is the cdnjs API free?
Yes. cdnjs is a free public CDN and its API is also free, with no commercial tier.
GET STARTED