Qwilt
Qwilt operates a global content delivery network built on the Open Edge Cloud — a true edge cloud with thousands of deeply embedded caching nodes inside service-provider networks — for OTT video streaming, low-latency live, gaming, and software delivery. Qwilt exposes programmatic control of its CDN through the Sites API (media-delivery site objects, versioned configurations, and publish/un-publish operations), the Certificate Manager API (TLS certificates and Qwilt-managed CSR workflows), the Origin Allow List API, plus Delivery Reports and Keys Manager APIs. Automation is available via the official Qwilt Terraform provider and the qctl command-line interface. Authentication uses QC Services API keys (Viewer/Editor) sent as an X-API-KEY Authorization header, or a username/password bearer token.
Qwilt publishes 6 APIs on the APIs.io network, including Certificate Templates API, Certificates API, Origin Allow List API, and 3 more. Tagged areas include Company, Media, CDN, Content Delivery Network, and Edge Computing.
Qwilt’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, changelog, authentication, and 22 more developer resources.
Kin Score
APIs 6
Individual APIs this provider publishes, each with its own machine-readable definition.
Qwilt Certificate Templates API
Certificate templates for Qwilt-managed CSR workflows
Qwilt Certificates API
TLS certificates
Qwilt Origin Allow List API
Qwilt CDN egress IP addresses for origin allow-listing
Qwilt Publishing Operations API
Publish, un-publish, republish and cancel operations
Qwilt Site Configurations API
Versioned site configuration revisions
Qwilt Sites API
CDN media-delivery site objects
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
qwilt-mcp.yml
MCP SERVERSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API