Play your partSUPPORTLOGINGET STARTED →
EXPLOREWHY GRAJAGENTSLEARNFEESPIONEER
GETREADYANDJUMP.COM · BUILT IN DETROIT
Developers

BUILDING ON
THE PLATFORM.

Live now

GRAJ is meant to be built on: other people can make things on top of it without asking. 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.

GET STARTED →GET AN API KEY →API DOCS →
What to know
What exists right now
A versioned REST surface under /api/v1, authenticated with a bearer token or your own API key, returning JSON. It is the same data the dashboards read, through the same guards, so nothing is reachable through it that the participant could not see anyway.
How authentication works
Requests carry a participant's bearer token or an API key that participant issued on screen at Settings → API keys. Authorization is evaluated per request against the actor rather than against a key with ambient powers — an integration acts as a specific participant and can do exactly what that participant 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. Keys are issued and revoked by you at Settings → API keys, and webhooks are set up at Settings → Webhooks; anything still being built is named on its own page rather than implied by a developer page that lists it as though it shipped.
Rate limits and good behavior
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
THE HTTP SURFACE.
Everything GRAJ does — orders, catalog, settlements, tax positions, verification — is behind an HTTP interface, because a dashboard that is the only way in keeps everybody who builds things out.
Read it
CLIENT LIBRARIES.
An SDK is a promise to keep something working across versions, which is why publishing one before the API surface has settled is a promise you break on your own users.
Read it
ADD GRAJ TO YOUR ASSISTANT.
The Model Context Protocol is a standard way to give an AI assistant tools and data.
Read it
IS IT UP RIGHT NOW?
A status page is only worth anything if it is measured rather than declared.
Read it

Files for machines

What an outside agent or tool reads to find GRAJ on its own. Each describes only doors that answer today; most of the API reads; the doors that write — the tool door, creating and changing your own products, and marking your own shipments shipped — need a write-scoped key and take an Idempotency-Key so a retry happens once.

OpenAPI 3.1
/openapi.json
Every /api/v1 door, the parameters it really takes, what it answers with, and whether it needs your key.
llms.txt
/llms.txt
What GRAJ is, the public surface, the rules for machines and where the docs are.
Agent card
/.well-known/agent-card.json
A2A-style: the MCP tools (every one reads but a draft-only one) and how to authenticate. GRAJ runs no A2A task endpoint.
MCP manifest
/.well-known/mcp.json
Where the MCP server is, its transport and protocol versions, how to sign in or use your key, and its tools.
Sign-in for AI apps
/.well-known/oauth-protected-resource
How Claude, ChatGPT or any MCP client signs a person in to GRAJ: OAuth 2.1, PKCE S256 only, apps register themselves.

Collections and changes

Postman collection
/api/developer/postman
Every /api/v1 door as one collection to import into Postman: the public ones with no key, the rest with your key in x-api-key. Save the JSON and import it.
Changelog
/changelog
What shipped and when, newest first, with the live count of what is proven. Public — no key, and nothing to sign in to.
Open data

The open dataset, live

Read just now from /api/platform/open-data — aggregate figures anybody may reuse with attribution. No key, nothing to sign in to.
Reading the protocol…
API reference

Every /api/v1 door

Download OpenAPI 3.1
Read from /openapi.json, the same file you can download. A test fails the build if a v1 route or method is missing from it, or if it lists one that does not exist. Open a door to see its parameters and what it answers with.
Loading the API reference…
Automations

Zapier and Make

App definitions you load into your own account. They are not published on Zapier or Make, and GRAJ has no account with either: you connect them with your own API key, your tasks or operations bill to your own plan, and GRAJ is paid nothing and pays nothing. They only read: new orders, notifications, activity, disputes, returns and sample requests, and product lookups.
Zapier app (not published)
/integrations/graj-zapier-app.js
A Zapier CLI index.js. Make a folder with zapier init, replace its index.js with this file, and zapier push it to your own account as a private integration.
Make app (not published)
/integrations/graj-make-app.json
A Make custom app: base, connection and modules in one file. Create a custom app in your own Make account and paste each block into its tab.
From the protocol

Run your own node, as the protocol specifies it

Read from /api/protocol/self-hosted-spec — the machine-readable specification, at the protocol's own version.
Reading the protocol…
From the protocol

The catalog, machine-readable

Read from /api/catalog/public — the index every AI agent starts from: each brand with a public wholesale catalog, its product count, and the URL that returns one brand's products as JSON.
Reading the protocol…
From the protocol

The endpoints an agent can call, machine-readable

Read from /api/developer/mcp-endpoints — what an AI agent or MCP client wires itself to, with the methods each path answers and what it is for.
Reading the protocol…
From the protocol

What runs on every push

Read from /api/developer/github-actions — the checks a change to GRAJ passes before and after it deploys.
Reading the protocol…

API versions and deprecation

The API is version 1. Nothing in it is removed without at least 180 days of notice, and the notice arrives in the headers of every answer from the door that is going away.

One version, said on every answer
Everything under /api/v1 is version 1, and every answer carries the header API-Version: 1.
Adding is not breaking
A new door, a new field in an answer or a new optional parameter can arrive at any time. Write your code to ignore fields it does not know.
At least 180 days of notice
Nothing is removed or changed incompatibly without at least 180 days between the day it is marked deprecated and the day it stops answering.
The notice travels with the answer
From the day a door is deprecated, every answer it gives carries a Deprecation header (RFC 9745), a Sunset header with the last day (RFC 8594) and a Link to this policy and to what replaces it.
Listed here and in the changelog
Every deprecation is listed below with its dates and its replacement, and announced in the changelog the day it is made.
No /api/v1 door is deprecated today.

Use GRAJ from Claude or ChatGPT

Add GRAJ to your own AI assistant and ask it about your orders, leads, day plan, customers and what you are owed. Paste this address where your assistant adds a custom server (Claude calls it a custom connector), then sign in with your GRAJ account: https://www.getreadyandjump.com/api/v1/mcp

No account? The public directory and the published catalog answer without a key or a sign-in, read-only, a few results at a time: https://www.getreadyandjump.com/api/v1/mcp/public

What it can see
Your own account only — the one you choose when you sign in — read the way your own screens read it: orders and their status, your catalog with prices and minimums, leads, customers, day plan, receivables, and the public directory.
What it can do
Nothing you did not allow. If you tick drafts, it can save a draft order for one of your customers, marked “drafted by your assistant”. It never places an order, messages anybody or moves money; you place the draft yourself.
Who pays
Your own AI plan pays for the thinking. GRAJ calls no AI model for this and charges nothing for it.
Taking it back
Settings → API keys lists every assistant with access, when it last asked, and its history. REVOKE stops it on its next request. Only an owner or admin of the account can allow one.
GRAJ

READY TO
RUN YOUR GAME ON GRAJ.

Free to join. Participants keep 95% of every transaction; GRAJ takes 5%. Built for 195 countries — payments live in the United States.

GET STARTED →SEE HOW IT WORKSEXPLORE GRAJ