Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Developer Tools / cdnjs API
cdnjs API logo

cdnjs API

72
AI ReadinessAI-Aware (A-)72/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticDeveloper ToolsPackage Registrynone5 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Jentic One on GithubView OpenAPI Document

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcdnjs.com%2Fcdnjs" | sh
2

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%2Fcdnjs.com%2Fcdnjs" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

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.

C

cdnjs API

- AI-Aware (A-)
72/100
100
Foundational Compliance
63
Developer Experience & Jentic Compatibility
48
AI-Readiness & Agent Experience
94
Agent Usability
100
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

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.

48

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4
43%

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.

50%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1
100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

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

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the cdnjs API by hand means remembering its library and version path shapes and choosing which fields to request per call yourself. Through Jentic you install once, import cdnjs from the API Directory, and your agent calls it.

Permission scoping

cdnjs puts the library name in the URL path for operations like /libraries/{library}/{version}, so a rule can pin your agent to lookups for one library. The API is read-only over the public catalogue, and you choose which lookup operations it may call.

Credential isolation

The cdnjs API needs no credential, so there is nothing to store, and no key ever enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'look up a JavaScript library version' or 'get file metadata for a library', and Jentic returns the matching cdnjs 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.

Complementary

GitHub API

→

Source repositories backing many cdnjs-hosted libraries

Pair with cdnjs when an agent needs both the package metadata on cdnjs and the source code or release notes on GitHub

Alternative

npm Registry API

→

Package registry for JavaScript dependencies with version and download metadata

Choose npm when the agent is resolving build-time dependencies; choose cdnjs for runtime in-browser script delivery

Complementary

CircleCI API

→

CI pipelines that often consume cdnjs-hosted assets in build steps

Use CircleCI alongside cdnjs when an agent triggers a build that references CDN-hosted libraries

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 with Jentic One, the self-hosted execution layer.

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.

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

Yes. Because you run Jentic One yourself, your own rules decide which cdnjs operations the agent may call, and the API is read-only over the public catalogue, so it can only browse and look up libraries, not change anything. Since cdnjs puts the library name in the URL path for operations like GET /libraries/{library}/{version}, you can write a rule that pins the agent to lookups for a single library or restricts it to specific endpoints such as /libraries, /whitelist, or /stats. The cdnjs API needs no credential, so there is nothing to store and no key ever enters the agent's context.

GET STARTED

Start building with cdnjs API

Explore with Jentic One
View OpenAPI Document