canonical: https://jentic.com/apis/pterodactyl.io/pterodactyl

# Pterodactyl Panel API

REST API for Pterodactyl Panel, an open-source game server management platform. Includes both Client API (for server users) and Application API (for administrators) covering server management, user administration, node management, location management, and more. The API exposes 64 endpoints secured with bearer authentication.

## For AI agents

Programmatically list all accessible servers, get available permissions. Covers 64 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for cloud infrastructure only.

## Capabilities

- List all accessible servers
- Get available permissions
- Enable 2FA
- Generate 2FA QR code
- Disable 2FA
- Update email address

## Use cases

### Cloud Infrastructure Operations

Use the Pterodactyl Panel API to perform cloud infrastructure operations programmatically. The API provides 64 endpoints covering core functionality including list all accessible servers, get available permissions, get account details.

Example prompt: Call GET `/api/client` to list all accessible servers

### Automated Application Management

Automate application operations by combining multiple Pterodactyl Panel API endpoints. Agents can get available permissions and then get account details in a single workflow.

Example prompt: Call GET `/api/client/permissions` to get available permissions, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Pterodactyl Panel API 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 bearer tokens manually.

Example prompt: Search Jentic for 'list all accessible servers', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/client` | List all accessible servers |
| GET | `/api/client/permissions` | Get available permissions |
| GET | `/api/client/account` | Get account details |
| POST | `/api/client/account/two-factor` | Enable 2FA |
| GET | `/api/client/account/two-factor` | Generate 2FA QR code |
| POST | `/api/client/account/two-factor/disable` | Disable 2FA |
| PUT | `/api/client/account/email` | Update email address |
| PUT | `/api/client/account/password` | Change password |

## Key resources

- **Application** — Operations for application
- **Client** — Operations for client

## AI readiness

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.

- **Score:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 92 / 100
  - Security: 60 / 100
  - AI Discoverability: 71 / 100
- **View full report:** https://jentic.com/apis/pterodactyl.io/pterodactyl/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Pterodactyl Panel API by hand means setting bearer auth, pointing requests at your own panel-domain host, and managing account and server calls yourself. Through Jentic you install once, import Pterodactyl Panel from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Pterodactyl scopes client operations under `/api/client`, so you limit the agent to the operations it needs, such as listing accessible servers or reading account details. You choose the operations it may call, so account changes like updating the email, password, or two-factor settings are not included unless you add them.
- **Credential handling:** Your Pterodactyl Panel API token 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.
- **Discovery method:** Agents search Jentic by intent such as 'list accessible servers' or 'read account details', and Jentic returns the matching Pterodactyl operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### What authentication does the Pterodactyl Panel API use?

The Pterodactyl Panel API uses a Bearer token in the Authorization 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 list all accessible servers with the Pterodactyl Panel API?

Yes. Use the GET `/api/client` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Pterodactyl Panel API?

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 list all accessible servers through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list all accessible servers'. Jentic returns the matching Pterodactyl Panel API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Pterodactyl Panel API have?

The Pterodactyl Panel API exposes 64 endpoints covering application, client operations.

### Can I limit what my agent is allowed to do with the Pterodactyl Panel API?

Yes. Jentic One is self-hosted, so your own rules decide which Pterodactyl operations the agent may call and which token it uses. Because Pterodactyl scopes client operations under `/api/client`, you can allow read-only calls such as GET `/api/client` to list accessible servers or GET `/api/client/account` to read account details, while leaving account changes like updating the email, password, or two-factor settings out unless you explicitly add them. The bearer token is injected only for the operations you permit.