Status

Service status

A live check of the Regulation to Control API, run from your browser when this page loaded. Nothing here is cached, and nothing here is set by hand.

What this page does and does not claim

It performs one request to the API's own health endpoint, on this same domain, at the moment you loaded the page, and reports what came back. That is the whole of it.

• There is no uptime percentage here, and there will not be one until there is enough operating history to compute one honestly. The same reason the home page publishes no uptime figure applies here.
• There is no incident history. This page keeps no record — not of your check, not of anyone else's.
• A result of Unreachable means this browser could not complete the request. That is a real signal, but it cannot distinguish the service being down from the network between you and it being down.
• A result of Operational means the API answered a health check. It is not a claim about every endpoint, and it is not a promise about the next minute.

Monitoring it yourself

Point your own monitoring at https://controlgraph-api.com/health rather than at this page. It answers for the API, returns JSON, needs no API key and is not rate limited — a 200 with {"ok":true} is healthy. This page is a human's view of that same endpoint and adds nothing to it.

The full contract is at openapi.json, and every published change to it is in the changelog.

Something looks wrong

Email contact@nerveplusinc.com. Two things make it answerable quickly: the time of the check shown above, and the requestId from the response you are asking about — it is on every response, success or failure, and in the x-request-id header.

If you are being refused with quota_exceeded rather than an outage, GET /v1/usage will tell you the ceiling being enforced against your key and when it resets. It costs no quota, so it answers even then.