🖥️ For Developers, By Developers

Deploy Game Servers With Code.

Full REST API. Per-container access. MCP integration. Everything you need to automate game server infrastructure.

API Reference Get Started
50+
API Endpoints
<200ms
Avg Response
99.9%
API Uptime
5 min
To First Deploy

Game Server Tooling Is Broken

You want to automate. The tools won't let you.

Manual Everything

SSH into boxes, write bash scripts, pray the deploy works. Game server management stuck in 2010.

Vendor Lock-in

Proprietary panels with no API. Your automation stops where their UI begins.

No Observability

Black-box infrastructure. No metrics, no logs, no way to debug production issues at 2am.

Platform API

Deploy, scale, and manage your entire fleet programmatically. Every action in the UI is an API call you can make yourself.

GET
/clusters
List clusters with servers, usage metrics, and capacity
POST
/brand/servers/deployments
Create a new deployment across any region
POST
/brand/servers/deployments/{id}/scale
Scale a deployment up or down
GET
/gameservers/{id}/settings
Get configurable variables for a server
POST
/gameservers/{id}/actions/restart
Restart with graceful or hard restart
POST
/gameservers/{id}/actions/update
Update server configuration variables
POST
/gameservers/{id}/auth
Get container token for direct access
DELETE
/gameservers/{id}
Delete a game server
Full API Reference
// List your clusters and servers
GET /api/clusters
{
"clusters": [{
"clusterId": 12345,
"location": "London, UK",
"clusterType": "resource",
"usage": {
"used": 4096, "total": 8192,
"unit": "MB", "percentage": 50
},
"gameservers": [{
"gameName": "Minecraft",
"players": 5,
"memoryRequestMb": 2048
}]
}]
}
// Update server settings
POST /api/gameservers/67890/actions/update
{
"updates": [{
"variable": "SERVER_NAME",
"userValue": "EU Rust #4"
}]
}
✓ Settings updated successfully
// Step 1: Get a container token (5 min TTL)
POST /api/gameservers/67890/auth
{
"token": "eyJhbG...",
"expiresIn": 300
}
// Step 2: Call the container directly
GET https://{container}:8080/status
{
"state": "running",
"players": { "current": 18, "max": 50 },
"memory": { "usedMb": 3840 },
"uptime": "4d 12h 33m"
}

Per-Container Direct Access

Every game server container exposes its own REST API. Get a short-lived token from the platform, then talk to the container directly: files, logs, console, and status.

/status
Server state, player count, memory, uptime
/restart
Restart the game process
/files/list
Browse the filesystem
/files/read
Read file contents
/files/write
Write files remotely
/logs
Stream and filter logs
/health
Kubernetes liveness probe
/ready
Kubernetes readiness probe

Build with AI

PingCore exposes an MCP server. Connect it to Claude, Cursor, or any MCP-compatible client and manage your infrastructure conversationally.

Deploy and scale servers with natural language
Query player counts, resource usage, and server status
Restart, update, or reconfigure servers conversationally
Build custom AI workflows around game server operations
👤
Restart my EU Minecraft server and tell me the player count
→ POST /gameservers/67890/actions/restart
→ GET /gameservers/67890/settings
✦
Done. Server 67890 is restarting. Last player count was 5/20.

Secure by Default

Scoped API keys, granular RBAC, and a full audit trail for every request.

Personal Keys

Up to 5 keys tied to your account. Visible only to you. Perfect for personal projects and scripts.

Authorization: Bearer pc_live_k7x...

Brand Keys

Up to 10 keys shared across your team. Scoped to your brand. Deactivated if the creator leaves.

Authorization: Bearer pc_brand_m9p...

Full Audit Trail

Every API request logged with endpoint, method, status code, duration, and IP. Filter by key scope.

200GET /clusters42ms
200POST /actions/restart128ms

Infrastructure That Doesn't Compromise

Built for game servers. No overcommitment, no noisy neighbors, no surprises.

0%
Overcommit

Request 4 cores, get 4 dedicated cores. No shared tenancy.

<1ms
DDoS Detection

Game-aware filtering at the network edge. Always on.

NVMe
Storage

SSD-only nodes. No spinning disks, no throttling.

10+
Locations

Americas, EU, Asia, OCE. Co-located CDN and compute.

Latency matters. We know.

CDN nodes sit alongside compute clusters. Game files download at wire speed. Packet loss is monitored per-node.

Platform Details

Ready to Start Building?

Get your API key and deploy your first game server in minutes. Full docs, real endpoints, no sandbox limitations.

Get StartedRead the API Docs