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

# SimpleCDN API (formerly PageCDN)

SimpleCDN (formerly PageCDN) provides CDN services for accelerating web content delivery. Note: Public API documentation is not readily available; this specification is based on typical CDN API patterns. The API exposes 5 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create cdn zone, list cdn zones. Covers 5 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for productivity only.

## Capabilities

- Create CDN zone
- List CDN zones
- Get zone details
- Delete zone
- Purge cache

## Use cases

### Productivity Operations

Use the SimpleCDN API (formerly PageCDN) to perform productivity operations programmatically. The API provides 5 endpoints covering core functionality including create cdn zone, list cdn zones, get zone details.

Example prompt: Call POST /zones to create cdn zone

### Automated zones Management

Automate zones operations by combining multiple SimpleCDN API (formerly PageCDN) endpoints. Agents can list cdn zones and then get zone details in a single workflow.

Example prompt: Call GET /zones to list cdn zones, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SimpleCDN API (formerly PageCDN) endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create cdn zone', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/zones` | Create CDN zone |
| GET | `/zones` | List CDN zones |
| GET | `/zones/{zone_id}` | Get zone details |
| DELETE | `/zones/{zone_id}` | Delete zone |
| POST | `/zones/{zone_id}/purge` | Purge cache |

## Key resources

- **zones** — Operations related to zones

## 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:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 70 / 100
- **View full report:** https://jentic.com/apis/simplecdn.com/simplecdn/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 SimpleCDN by hand means sending its X-API-Key header, pointing calls at https://api.simplecdn.com/v1, and tracking zone ids for purges yourself. Through Jentic you install once, import SimpleCDN from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** SimpleCDN puts the zone id in the URL path (`/zones/{zone_id}`), so a rule can pin your agent to one zone: it can read and purge that zone and nothing else. You choose the operations it may call, so destructive ones like deleting a zone are not included unless you add them.
- **Credential handling:** Your SimpleCDN 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 'create a CDN zone' or 'purge a zone', and Jentic returns the matching SimpleCDN operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the SimpleCDN API (formerly PageCDN) use?

The SimpleCDN API (formerly PageCDN) uses an API key passed in the `X-API-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create cdn zone with the SimpleCDN API (formerly PageCDN)?

Yes. Use the POST /zones endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SimpleCDN API (formerly PageCDN)?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create cdn zone through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create cdn zone'. Jentic returns the matching SimpleCDN API (formerly PageCDN) operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SimpleCDN API (formerly PageCDN) have?

The SimpleCDN API (formerly PageCDN) exposes 5 endpoints covering zones operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which SimpleCDN operations and credentials your agent may use. Because SimpleCDN puts the zone id in the URL path (`/zones/{zone_id}`), you can pin the agent to a single zone and grant only the calls you choose, such as listing zones, reading a zone's details, and purging its cache. Destructive operations like deleting a zone stay off unless you explicitly add them.