Status API
Every service on the status page is also a raw JSON endpoint on our own servers. The API mirrors the status files in the World GitHub repos. Same source of truth, machine-readable, CORS open to any origin.
https://useworld.xyz/endpoint/status-{service}Try it live
Pick an endpoint and fire a real request from your browser.
Collections
Test scores
Core Software
Internal Injection
External Injection
Platforms
Community & Web
https://useworld.xyz/endpoint/status-allResponse will appear here
Endpoints
One path per service, plus three collections. GET only.
Collections
/endpoint/status-summaryJust the verdict: operational or not, the worst status, and what is affected.
Test scores
/endpoint/status-scoressUNC and UNC for every injection module, with the row counts behind each number.
Core Software
Internal Injection
Platforms
Community & Web
Accepted aliases
Shorthands resolve to the canonical id, and a .json suffix is ignored. /endpoint/status-external and /endpoint/status-external-build.json both return the External build.
Response shape
A service object; collections wrap those objects in a summary.
GET /endpoint/status-executor
{ "service": "executor", "name": "Executor Status", "about": "The Windows executor itself.", "endpoint": "/endpoint/status-executor", "source": "https://raw.githubusercontent.com/...", "checked_at": "2026-08-14T12:00:00.000Z", "status": "up", "label": "Operational", "healthy": true, "severity": 0, "raw": "up", "latency_ms": 84 }
GET /endpoint/status-summary
{ "checked_at": "2026-08-14T12:00:00.000Z", "summary": { "operational": false, "worst_status": "updating", "reason": "updating", "total": 20, "healthy": 19, "degraded": 1, "unreachable": 0, "affected": [ { "service": "executor", "name": "Executor Status", "status": "updating" } ] } }
Service fields
| Field | Type | Description |
|---|---|---|
| service | string | Canonical service id, e.g. "executor". |
| name | string | Display name as shown on the status page. |
| about | string | One-line description of what the service covers. |
| status | string | Normalised status key, one of the values in the table below. |
| label | string | Human-readable label, e.g. "Operational". |
| healthy | boolean | True when the status counts as working (up, undetected). |
| severity | number | 0 (fine) to 5 (down); -1 when the status is unknown. |
| raw | string | Untouched contents of the GitHub status file, before normalising. |
| source | string | The raw.githubusercontent.com URL this status was mirrored from. |
| endpoint | string | Path this service is served at. |
| latency_ms | number | How long the upstream read took, in milliseconds. |
| checked_at | string | ISO-8601 UTC timestamp of the read. |
| error | string | Only present when the upstream file could not be read. |
Summary fields
| Field | Type | Description |
|---|---|---|
| summary.operational | boolean | True when nothing is down, patched, fixing, updating or discontinued. |
| summary.worst_status | string | Highest-severity status currently affecting a service, or null. |
| summary.reason | string | Wording for that worst status, e.g. "getting fixed". |
| summary.total | number | Number of services in the response. |
| summary.healthy | number | How many of them are healthy. |
| summary.degraded | number | How many are in a state users would notice. |
| summary.unreachable | number | How many status files could not be read. |
| summary.affected | array | The degraded services: { service, name, status }. |
Status values
Exactly the vocabulary the status files use; anything unrecognised is reported as up.
| Status | Label | Healthy | Severity |
|---|---|---|---|
| up | Operational | true | 0 |
| down | Down | false | 5 |
| patched | Patched | false | 4 |
| updating | Updating | false | 2 |
| discontinued | Discontinued | false | 1 |
| fixing | Fixing | false | 3 |
| undetected | Undetected | true | 0 |
| development | In Development | false | 1 |
| error | Unavailable | false | -1 |
error is never written to a status file. It means this API could not read the file from GitHub, and it comes back with HTTP 502.
Parameters
| Query | Values | Effect |
|---|---|---|
| ?format= | json | text | text returns the bare status word, the same shape as the GitHub file itself. |
| ?pretty= | 1 | 0 | JSON is indented by default; pretty=0 minifies it. |
| ?service= | <id> | Alternative to the path, e.g. /endpoint/status-all?service=executor. |
Errors
| Code | Body | When |
|---|---|---|
| 404 | unknown_service | No endpoint by that name. The body lists every valid one. |
| 405 | method_not_allowed | Only GET, HEAD and OPTIONS are accepted. |
| 502 | status: "error" | The GitHub status file could not be read. The body still carries the payload with an error field. |
Samples
Same endpoint, four runtimes.
# One service curl -s https://useworld.xyz/endpoint/status-executor # Everything, minified curl -s "https://useworld.xyz/endpoint/status-all?pretty=0" # Just the word, like the raw GitHub file curl -s "https://useworld.xyz/endpoint/status-executor?format=text" # sUNC percentage for one module, as a bare number curl -s "https://useworld.xyz/endpoint/status-sunc-velocity?format=text"
No key, no limits
The endpoints are public and unauthenticated, and send Access-Control-Allow-Origin: *. Use them from a browser, a bot or a script.
Cached 15 seconds
Responses carry a 15s cache with a 60s stale-while-revalidate window, so hammering the API will not hammer GitHub. Poll at 30s like the status page does.
Mirrors GitHub
Each status is read from the same raw.githubusercontent.com file the status page uses, and the source URL travels in the response so you can verify it yourself.