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

PROTOCOL
STATUS.

Whether the site answers right now, and what the protocol's own hourly checks found.

SERVICES

ALL SYSTEMS
CHECKING.

API
Checking — The programmatic surface every integration and agent calls.
Checking
AUTHENTICATION
Checking — Sign-in, sign-up, and session security for every participant.
Checking
CATALOG & DISCOVERY
Checking — Catalogs, listings, and discovery across the protocol.
Checking
PAYMENTS
Checking — Checkout and the flat 5% settlement on every transaction.
Checking
AI AGENTS
Checking — The 12 GRAJ role agents answering and acting in real time.
Checking
NOTIFICATIONS
Checking — Alerts, messages, and event delivery to operators.
Checking
MEDIA UPLOAD
Checking — Product images and files stored and served.
Checking
SEARCH
Checking — Indexing and lookup across catalogs and operators.
Checking
Incidents

What has gone wrong, and where it stands

Read from /api/status/incidents — declared by the GRAJ admin under the incident response playbook, updated as it is worked, closed when it is fixed.
Reading the protocol…
Something wrong?
Report a problem
It goes straight to the GRAJ admins as a notification. It does not appear on this page by itself — an admin reads it and, if it is an incident, declares it here with every update after it.
From the protocol

The health index, as the protocol computes it

Read from /api/analytics/protocol-health — real participants only, over thirty days, scored and graded by the door. Trade figures appear once five sellers and five buyers stand behind them.
Reading the protocol…
From the protocol

What the protocol's own checks found

Read from /api/status — the money rules the protocol checks against itself every hour, and the latest batch of end-to-end checks driven against this site. Times are UTC.
Reading the protocol…
From the protocol

The deployment you are reading

Read from /api/version — the commit the production deployment was built from, published by the build itself, the same door the ship script checks after every deploy.
Reading the protocol…
Subscribe

Hear when an incident opens

Every incident above, and every update to it, as an RSS feed — paste the address into any feed reader (Feedly, Inoreader, Outlook, Thunderbird, or an RSS app in Slack or Teams). It keeps no list and sends nothing; your reader asks.
Reading the protocol…