Overview
The Monkey Network client API is Pterodactyl-compatible and lets you manage your Discord bot hosting servers from scripts, dashboards, or CI pipelines. All requests use the base URL:
https://dash.monkey-network.xyz/api/clientAuthentication
Create a personal API key in the dashboard under Account Settings → API Credentials, then send it as a Bearer token on every request:
curl https://dash.monkey-network.xyz/api/client \
-H "Authorization: Bearer <YOUR_API_KEY>" \
-H "Accept: application/json"Treat API keys like your bot token: keep them in environment variables, never in source control, and revoke any key that leaks. The same rules from our security best practices guide apply.
Endpoints
| Endpoint | Method | Description |
|---|---|---|
/ |
GET | List the servers your API key can access (paginated). Returns 401 on a missing or invalid key. |
/servers/{server} |
GET | Details for a single server, addressed by its short identifier. Returns 404 if not found or not accessible. |
/servers/{server}/resources |
GET | Live CPU, memory and disk usage plus the current power state — handy for external uptime monitoring. |
Example — check a server's live usage:
curl https://dash.monkey-network.xyz/api/client/servers/<SERVER_ID>/resources \
-H "Authorization: Bearer <YOUR_API_KEY>" \
-H "Accept: application/json"Machine-readable resources
For tooling and AI agents, the API is described in standard formats:
- OpenAPI 3.1 specification — the authoritative endpoint reference
- API catalog (RFC 9727)
- Agent skills index and MCP server card
Since the API is Pterodactyl-compatible, existing Pterodactyl client libraries and tools generally work unchanged against the base URL above.