Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 5centsCDN - Zones, 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 | shStep 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 instanceJentic 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.
What an agent can do with 5centsCDN - Zones API.
Zones
Zone
Get Servers
Create Zone
GET STARTED
For Agents
Programmatically zones, zone. Covers 178 operations with apiKey authentication.
Use for: I need to zones, I want to zone, Search for servers, Find all zone
Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.
API for managing Zones in <a href="https://www.5centscdn.net" target="_blank">5centsCDN</a>. The API exposes 178 endpoints secured with apiKey authentication.
Update Info
Delete Info
Patterns agents use 5centsCDN - Zones API for, with concrete tasks.
★ HR and Recruiting Operations
Use the 5centsCDN - Zones to perform hr recruiting operations programmatically. The API provides 178 endpoints covering core functionality including zones, zone, get servers.
Call GET /zones to zones
Automated List Zones Management
Automate list zones operations by combining multiple 5centsCDN - Zones endpoints. Agents can zone and then get servers in a single workflow.
Call GET /zones/http/push to zone, then verify the result
AI Agent Integration via Jentic
AI agents discover and call 5centsCDN - Zones 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 'zones', load the operation schema, and execute with Jentic-managed credentials
178 endpoints — api for managing zones in <a href="https://www.
METHOD
PATH
DESCRIPTION
/zones
Zones
/zones/http/push
Zone
/zones/http/push/servers
Get Servers
/zones/http/push/new
Create Zone
/zones/http/push/{zoneid}
Update Info
/zones/http/push/{zoneid}
Zone
/zones/http/push/{zoneid}
Delete Info
/zones/http/push/{zoneid}/ssl
Update SSL
/zones
Zones
/zones/http/push
Zone
/zones/http/push/servers
Get Servers
/zones/http/push/new
Create Zone
/zones/http/push/{zoneid}
Update Info
/zones/http/push/{zoneid}
Three things that make agents converge on Jentic-routed access.
Credential isolation
Your 5centsCDN 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 'list zones' or 'create a push zone', and Jentic returns the matching 5centsCDN Zones operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Time to first call
Alternatives and complements available in the Jentic catalogue.
Specific to using 5centsCDN - Zones API through Jentic.
What authentication does the 5centsCDN - Zones use?
The 5centsCDN - Zones 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 zones with the 5centsCDN - Zones?
Yes. Use the GET /zones endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the 5centsCDN - Zones?
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 zones through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'zones'. Jentic returns the matching 5centsCDN - Zones operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the 5centsCDN - Zones have?
The 5centsCDN - Zones exposes 178 endpoints covering list zones, http push zones, http pull zones operations.
Can I limit what my agent is allowed to do with the 5centsCDN Zones API?
Yes. Because you run Jentic One yourself, your own rules decide which 5centsCDN Zones operations and which stored API key the agent may use. Since 5centsCDN puts the zone id in the URL path (/zones/http/push/{zoneid}/...), you can pin the agent to a single zone so it reads that zone and manages its SSL and nothing else. You also choose the exact operations it may call, so a destructive one like deleting a zone stays off the list unless you add it.
Zone
/zones/http/push/{zoneid}
Delete Info
/zones/http/push/{zoneid}/ssl
Update SSL