Skip to main content
This reference covers the console at console.perfgrid.com. The Grid Hosting panel API at hosting-panel.net is a different API with its own tokens: see the Grid Hosting panel API.

Authentication

Create a token in the console under More > API tokens (you need two-factor authentication or a passkey first), and send it in the Authorization header with every request. See API tokens.
A token belongs to one member and one billing account, so paths have no billing account in them. It can do what both its own abilities and the member’s permissions allow.

Base URL

Check a token with GET /me:
abilities lists what the token may do right now: the abilities it was given that the member still has. Responses are JSON with their content under data. Amounts are decimal strings next to their currency, times are ISO 8601 in UTC, and lists are paged with a cursor: pass meta.next_cursor as cursor to get the next page (per_page 1 to 100, default 25).

Abilities

GET /me and /notifications work with any token. Other endpoints need an ability. A “manage” ability doesn’t include the matching “view” one.

Rate limits

Each token may make 120 requests a minute, of which at most 30 may change something (any request other than GET). The API and the MCP server share both limits. Over the limit, the API answers 429 with a Retry-After header.

Errors

Errors come back as JSON with a message.

MCP server

The same tokens connect AI assistants to the PerfGrid MCP server at https://console.perfgrid.com/mcp, with the token in the Authorization header. The tools an assistant sees follow the token’s abilities. See API tokens.
Last modified on October 31, 2026