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

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%2Fsimplecdn.com%2Fsimplecdn" | 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

Purge cache

GET STARTED

Start building with SimpleCDN API (formerly PageCDN) API

Explore with Jentic One

View OpenAPI Document

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?

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

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 isolation

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.

Intent-based discovery

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.

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

SimpleCDN API (formerly PageCDN)

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

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityCollaborationapiKey5 EndpointsREST

For Agents

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

Use for: I need to cdn zone, I want to cdn zones, Search for zone details, Find all zone

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

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.

Jentic One on Github View OpenAPI Document

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.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

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.

AI-Readiness & Agent Experience

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

Grade: C-Signals: 4

42%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

62%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

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

SimpleCDN API (formerly PageCDN)

Jentic AI Readiness Score

SimpleCDN API (formerly PageCDN)

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness