List all Judge0 submission status codes via pay-per-call MPP endpoint
What it does
This endpoint returns the list of possible submission statuses used by the Judge0 online code execution service. It is part of a broader Judge0 API suite exposed through the Locus MPP (Micropayment Protocol) gateway, which includes endpoints for executing code, submitting code asynchronously, retrieving submission results, and listing supported languages. The list-statuses endpoint is a simple reference call that returns status IDs and their descriptions (e.g., "In Queue", "Processing", "Accepted", "Wrong Answer", "Time Limit Exceeded", etc.), which are needed to interpret results from code execution submissions.
Payment is settled via the Tempo L2 method using pathUSD (6 decimals). The listed amount for this endpoint is 5000 base units, which equals $0.005 per call. The endpoint is a POST request with no required request body. Note that the probe returned 404 on HEAD and GET methods, which is expected since the OpenAPI spec defines this as a POST-only route.
The Judge0 service supports 60+ programming languages with sandboxed isolation. This particular endpoint is a utility/reference call rather than a compute-heavy operation. Other endpoints in the same service handle actual code execution at $0.006 per call.
Capabilities
Use cases
- —Look up all possible submission status codes before interpreting code execution results
- —Build a UI that maps Judge0 status IDs to human-readable labels
- —Validate expected status values in automated testing pipelines
Fit
Best for
- —Agents that need to interpret Judge0 submission results
- —Developers integrating Judge0 code execution into workflows
- —Reference lookups before or after submitting code for execution
Not for
- —Actually executing or compiling code (use execute-code or submit-code endpoints instead)
- —Use cases requiring free/unauthenticated access to Judge0 status metadata
Quick start
curl -X POST https://judge0.mpp.paywithlocus.com/judge0/list-statuses \
-H "Content-Type: application/json"Endpoint
Quality
The OpenAPI spec provides clear endpoint definitions, pricing, and service context, but there is no response schema, no example responses, and the probe returned 404 (expected for POST-only route probed with HEAD/GET). No crawled documentation was available beyond error messages.
Warnings
- —Probe returned 404 on HEAD and GET — endpoint is POST-only; liveness via POST was not confirmed in the probe
- —No response schema defined in the OpenAPI spec for any endpoint
- —No example responses available; actual status list contents are inferred from Judge0 documentation
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo/Locus conventions
Citations
- —Judge0 supports 60+ programming languages with sandboxed isolationhttps://judge0.com
- —The list-statuses endpoint costs 5000 base units via Tempo methodhttps://judge0.mpp.paywithlocus.com
- —API reference and LLM docs available at linked URLshttps://beta.paywithlocus.com/mpp/judge0.md