MPPtempoquality 0.55

Retrieve the result of an async Judge0 code submission by token, paid per call via MPP/Tempo.

Price
$0.005 / call
Protocol
mpp
Verified
no
Endpoint
https://judge0.mpp.paywithlocus.com/judge0/get-submission

What it does

The Judge0 Get Submission endpoint is part of a Judge0 code-execution service exposed through the Locus MPP (Micropayment Protocol) gateway. It allows callers to poll for the result of a previously submitted asynchronous code execution by providing the submission token returned from the `/judge0/submit-code` endpoint.

The endpoint accepts a POST request with a JSON body containing a single required field — `token` — which is the submission identifier. On success it returns the execution result including stdout, stderr, compilation output, execution time, memory usage, and status. The per-call price is 5 000 base units of pathUSD (currency `0x20c0…b9537d11c60e8b50`), which at 6 decimals equals $0.005 (half a cent), settled on Tempo L2.

This endpoint is one of five Judge0 routes on the same gateway: execute-code (synchronous), submit-code (async), get-submission (this endpoint), list-languages, and list-statuses. The underlying Judge0 engine supports 60+ programming languages with sandboxed isolation. Note that the probe returned 404 on HEAD/GET because the endpoint only accepts POST requests; this does not indicate the service is down.

Capabilities

code-execution-resultasync-submission-pollingsandboxed-executionmulti-languagemicropayment-per-calltempo-settlement

Use cases

  • —Polling for the output of an asynchronously submitted code snippet
  • —Building AI agents that execute and verify code in a sandboxed environment
  • —Automated grading systems that submit student code and retrieve results
  • —CI/CD pipelines that offload compilation and test execution to a remote sandbox

Fit

Best for

  • —AI agents that need to run and retrieve code execution results programmatically
  • —Applications using the async submit-then-poll pattern for code execution
  • —Developers who want pay-per-call sandboxed code execution without managing infrastructure

Not for

  • —Synchronous one-shot code execution (use the /judge0/execute-code endpoint instead)
  • —Long-running or persistent compute workloads that exceed sandbox time limits
  • —Free or bulk code execution without per-call micropayments

Quick start

curl -X POST https://judge0.mpp.paywithlocus.com/judge0/get-submission \
  -H "Content-Type: application/json" \
  -d '{"token": "<submission-token-from-submit-code>"}'

Example

Request

{
  "token": "d85cd024-1548-4165-96c7-7bc88673f5a6"
}

Endpoint

URLhttps://judge0.mpp.paywithlocus.com/judge0/get-submission
Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.55/ 1.00

The OpenAPI spec provides a clear schema for the request body and pricing info, but there is no response schema, no example responses, and the probe returned 404 because it only tried HEAD/GET on a POST-only endpoint. Documentation links point to external sites not included in the crawl. Pricing is clear from the spec.

Warnings

  • —Probe returned 404 on HEAD and GET; the endpoint is POST-only so liveness could not be confirmed via the probe
  • —No response schema is defined in the OpenAPI spec — the shape of a successful response is undocumented
  • —External docs (https://beta.paywithlocus.com/mpp/judge0.md, https://judge0.com) were not crawled so details are inferred from the OpenAPI spec alone
  • —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo convention

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 17:33:08Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/jTNNHA
Retrieve the result of an async Judge0 code submission by token, paid per call via MPP/Tempo. — Clawmart · Clawmart