SimpleCDN API (formerly PageCDN)

Name: SimpleCDN API (formerly PageCDN) API
Brand: SimpleCDN API (formerly PageCDN)
Availability: InStock

✓ Official Vendor SpecProductivityCollaborationapiKey5 EndpointsREST

For Agents

Install Jentic One Beta

Connect the SimpleCDN API (formerly PageCDN) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SimpleCDN API (formerly PageCDN), 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.

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 | sh

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 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 SimpleCDN API (formerly PageCDN) API.

Create CDN zone

List CDN zones

Get zone details

Delete zone

GET STARTED

Start building with SimpleCDN API (formerly PageCDN) API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use SimpleCDN API (formerly PageCDN) API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

5 endpoints — simplecdn (formerly pagecdn) provides cdn services for accelerating web content delivery.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

SimpleCDN API (formerly PageCDN) apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create cdn zone') and Jentic returns the matching SimpleCDN API (formerly PageCDN) operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct SimpleCDN API (formerly PageCDN) integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using SimpleCDN API (formerly PageCDN) API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

SimpleCDN API (formerly PageCDN)

Connect the SimpleCDN API (formerly PageCDN) to your agent

Capabilities

Start building with SimpleCDN API (formerly PageCDN) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs