Edgegap v2 API
69
AI ReadinessAI-Aware (B+)69/100
Official vendor OpenAPI document · agent-readyCloud InfrastructureContainer OrchestrationapiKey3 EndpointsREST
For Agents
Deploy containerized applications to the Edgegap edge network or a private fleet, and list fleet hosts. Authenticates with an API key.
Use for: I want to deploy a game server to the Edgegap edge network, Deploy my application to a private fleet, List the hosts in one of my private fleets, Place a container at the lowest-latency location for my players
Not supported: Does not build container images or manage billing. Use for edge and private-fleet deployment only.
The Edgegap v2 API lets AI agents deploy containerized applications onto Edgegap's global edge network. An agent submits a deployment and Edgegap places the container at a low-latency location close to the end users, which suits multiplayer game servers and other latency-sensitive workloads. Agents can also target a private fleet of their own hosts and list the machines registered in that fleet before deploying. Every request carries an API key.
Install Jentic One Beta
Connect the Edgegap v2 API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Edgegap v2 API, 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.
1
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%2Fedgegap.com%2Fedgegap" | sh2
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%2Fedgegap.com%2Fedgegap" | 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.
Capabilities
What an agent can do with Edgegap v2 API.
Deploy a containerized application to the Edgegap edge network
Deploy an application to a private fleet of your own hosts
List the hosts registered in a private fleet
Use Cases
Patterns agents use Edgegap v2 API for, with concrete tasks.
★ Agent-Driven Edge Deployment via Jentic
AI agents deploy to Edgegap through Jentic without holding the API key in context. An agent searches by intent, receives the deployment schema, and launches a containerized workload at the edge end to end. Jentic injects the key at execution time, so the agent never sees the secret while it places servers close to end users.
Search Jentic for 'deploy an Edgegap application', load the POST /deployments schema, and launch the deployment with Jentic-managed credentials
Latency-Optimized Game Server Deployment
An agent responds to a spike in players by deploying a fresh game server instance to the edge, where Edgegap places it near the players to cut round-trip latency. The agent can repeat this per region or match, scaling capacity where demand appears instead of running fixed central servers.
Call POST /deployments to place a game server container at the edge location closest to the players
Private Fleet Deployment
An agent that manages its own hardware lists the hosts registered in a private fleet, confirms which are available, and then deploys the application onto that fleet. This keeps workloads on infrastructure the operator controls while still using Edgegap's deployment pipeline.
Call GET /private-fleets/{fleet-name}/hosts to check host availability, then POST /private-fleets/deployments to deploy
Key Endpoints
3 endpoints — the edgegap v2 api lets ai agents deploy containerized applications onto edgegap's global edge network.
METHOD
PATH
DESCRIPTION
POST
/deployments
Deploy a containerized application to the edge network
POST
/private-fleets/deployments
Deploy an application to a private fleet
GET
/private-fleets/{fleet-name}/hosts
List the hosts registered in a private fleet
POST
/deployments
Deploy a containerized application to the edge network
POST
/private-fleets/deployments
Deploy an application to a private fleet
GET
/private-fleets/{fleet-name}/hosts
List the hosts registered in a private fleet
Jentic AI Readiness Score
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.
E
Edgegap v2 API
- AI-Aware (B+)69/100
100
Foundational Compliance81
Developer Experience & Jentic Compatibility52
AI-Readiness & Agent Experience94
Agent Usability50
Security67
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
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.
81
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: ASignals: 4
48%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
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.
52
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
56%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
50
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).
67
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
67%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Edgegap v2 API by hand means setting the Authorization API key header and shaping the deployment request for the edge network or a private fleet yourself. Through Jentic you install once, import the Edgegap v2 API from the API Directory, store the key, and your agent calls it.
Permission scoping
You choose which Edgegap operations your agent may call, so a rule can let it list fleet hosts and deploy while keeping other operations out. Scoping is by operation, so a deployment call runs only when you grant it.
Credential isolation
Your Edgegap 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 'deploy to the edge' or 'list fleet hosts', and Jentic returns the matching Edgegap operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Edgegap v2 API through Jentic.
What authentication does the Edgegap v2 API use?
The Edgegap v2 API authenticates requests with an API key passed in the Authorization header, per its OpenAPI spec. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.
Can I deploy to a private fleet with the Edgegap v2 API?
Yes. Deploy to your own hosts with POST /private-fleets/deployments, and list the hosts in a fleet with GET /private-fleets/{fleet-name}/hosts before you deploy.
What are the rate limits for the Edgegap v2 API?
The OpenAPI spec does not specify rate limits; check the Edgegap documentation for current limits. Through Jentic, requests run from your own instance, so you control the pacing of the agent's calls.
How do I deploy an application with the Edgegap v2 API through Jentic?
Search Jentic for 'deploy an Edgegap application', load the returned POST /deployments operation with its input schema, and your agent launches the deployment with credentials injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there an Edgegap MCP server?
You don't need an MCP server to give your agent the Edgegap v2 API. Jentic connects it directly from the API Directory: import it, store your key, and your agent calls it, discovering operations on demand instead of loading a separate server's tool definitions into its context.
Can I limit what my agent is allowed to do with the Edgegap v2 API?
Yes. You choose which Edgegap operations your agent may call, so you can let it list fleet hosts without launching a deployment, or restrict it to fleet deployments only. Scoping is by operation, so the agent invokes only the endpoints you approve.
GET STARTED