EXPLOREINDUSTRIESGUIDESLEARNGLOSSARYBOOKSWHITEPAPERTOOLSRESOURCESPIONEERMARKETSCOUNTRIESFEESMISSION FUNDPASSPORT
SUPPORTLOGINJOIN THE PROTOCOL →
GETREADYANDJUMP.COM · BUILT IN DETROIT

DEVELOPER
ON GRAJ.

Developer on the GRAJ protocol. One fee. 195 countries. Join the protocol.

JOIN THE PROTOCOL →
Developers

BUILDING ON
THE PROTOCOL.

Live now

The point of calling this a protocol rather than a platform is that other people can build on it. A versioned HTTP API exists today and is the surface to build against; the language SDKs and tooling around it are at various stages, and each page says which.

What exists right now

A versioned REST surface under /api/v1, authenticated with a bearer token, returning JSON. It is the same data the dashboards read, through the same guards, so nothing is reachable through it that the operator could not see anyway.

How authentication works

Requests carry an operator's bearer token. Authorisation is evaluated per request against the actor rather than against an API key with ambient powers — an integration acts as a specific operator and can do exactly what that operator can do.

Versioning is a promise about breakage

The v1 prefix exists so that a change which would break an integration goes into v2 rather than into v1 on a Tuesday. Anything under an unversioned path is internal and can move.

What is honestly not there yet

No published language SDK, no webhooks you can subscribe to, and no self-service key management. Those are named on their own pages rather than implied by a developer page that lists them as though they shipped.

Rate limits and good behaviour

Public endpoints are rate limited per address. An integration that retries without backing off will be limited, which is the system working rather than failing.

Where to go next
/api/sdk/mcp-endpoints/api-status
JOIN THE PROTOCOL