Judge0 CE API

Name: Judge0 CE API
Brand: Judge0 CE API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsTesting QaapiKey20 EndpointsREST

For Agents

Submit code in 60+ languages to Judge0's sandboxed execution engine, configure resource limits, poll for results, and inspect supported languages and runtime statuses for coding-interview or education workflows.

Install Jentic One Beta

Connect the Judge0 CE API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Judge0 CE API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Judge0 CE API.

Submit source code with stdin and resource limits for sandboxed execution

Create batch submissions to run a suite of test cases in one request

Poll a submission token for stdout, stderr, and runtime metrics

GET STARTED

Start building with Judge0 CE API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Judge0 CE API for, with concrete tasks.

★ Coding-interview platform back-end

Coding-interview products that present candidates with problems can use Judge0 to safely execute and grade submissions. POST /submissions takes the candidate's source plus the test stdin and expected stdout, and the response token can be polled with GET /submissions/{token} for the verdict. Resource limits prevent runaway code from impacting other tenants. Batch submissions handle full test suites in a single round-trip.

Call POST /submissions/batch with the candidate's solution against 10 test cases, then poll GET /submissions/batch with the returned tokens until each has a status

Education platform code runner

Online learning platforms can embed a code-runner widget that calls Judge0 each time a student clicks 'Run'. The submission specifies language, source, and stdin; the response captures stdout, stderr, and exit metrics. GET /languages drives the language picker so the widget always shows the currently active runtime versions. Per-student submission rates are kept low by debouncing the run button.

On the student's Run click, call POST /submissions with language_id=71 (Python), the editor source, and the lesson's stdin; poll the token for stdout

AI assistant code execution

AI coding assistants that draft code can verify their output by executing it in Judge0 before returning to the user. The assistant generates a snippet, submits it to Judge0, captures the runtime result, and self-corrects if the output diverges from the expected stdout. This converts a static suggestion into a verified, executable answer.

After generating a Python solution, call POST /submissions with the source and expected stdin, poll for stdout, and re-prompt if stdout does not match

Sandboxed execution via Jentic

When an agent needs sandboxed execution as a tool, Jentic exposes Judge0 without leaking its API key into the prompt. The agent calls Jentic with a 'run code' intent, Jentic resolves to POST /submissions, injects the X-Auth-Token and X-Auth-User headers, and returns the submission token. The agent then asks Jentic for the result — keeping the credential entirely outside the agent's reasoning context.

Use Jentic to search 'submit code to Judge0', load POST /submissions, execute with the snippet, then call GET /submissions/{token} for the result

Key Endpoints

20 endpoints — judge0 ce is an open-source online code execution system that compiles and runs source code in over 60 programming languages inside resource-limited sandboxes.

METHOD

PATH

DESCRIPTION

POST

/submissions

Create a single code submission

GET

/submissions/{token}

Get a single submission's result

POST

/submissions/batch

Create a batch of submissions

GET

/submissions/batch

Get batch submission results

DELETE

/submissions/{token}

Delete a submission

GET

/languages

List active languages

GET

/statuses

List submission statuses

GET

/system_info

Get system info

POST

/submissions

Create a single code submission

GET

/submissions/{token}

Get a single submission's result

POST

/submissions/batch

Create a batch of submissions

GET

/submissions/batch

Get batch submission results

DELETE

/submissions/{token}

Delete a submission

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Judge0 X-Auth-Token and X-Auth-User keys are stored encrypted in the Jentic vault. Jentic injects both headers at execution time, so the credentials never appear in the agent's prompt or chat transcript.

Intent-based discovery

Agents search Jentic with intents like 'run code in a sandbox' or 'submit a Judge0 batch' and Jentic returns the matching Judge0 operation with its input schema, replacing manual reading of the Judge0 docs.

Time to first call

Direct Judge0 integration: 1-2 days to handle auth, submission polling, batch handling, and status interpretation. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Judge0 CE API through Jentic.

What authentication does the Judge0 CE API use?

Public Judge0 CE instances may accept anonymous calls, but production hosts use X-Auth-Token and optionally X-Auth-User headers as API keys. Jentic stores both keys encrypted and injects the headers at request time so the credentials never enter the agent's prompt.

How many programming languages does Judge0 support?

Judge0 CE supports 60+ programming languages and runtimes — call GET /languages to retrieve the active set with their version metadata, or GET /languages/all to include historical entries that may be archived.

What are the rate limits for Judge0?

ce.judge0.com is the public community instance and applies per-IP throttling that is not documented as a fixed number. For predictable throughput, self-host Judge0 or use the RapidAPI tier which publishes explicit per-second and per-day limits.

How do I run a code snippet through Jentic?

Search Jentic for 'submit code to Judge0', load POST /submissions, and execute with language_id and source_code. Jentic injects the X-Auth-Token. Then load GET /submissions/{token} to poll the result. Sign up at https://app.jentic.com/sign-up.

Can I run multiple test cases in one request?

Yes. POST /submissions/batch accepts an array of submissions and returns an array of tokens. Use GET /submissions/batch with a comma-separated token list to fetch the results in one request — this is the right shape for grading a candidate against a full test suite.

How do I configure resource limits on a submission?

POST /submissions accepts cpu_time_limit, wall_time_limit, memory_limit, stack_limit, and max_file_size fields per submission. Set conservative limits (e.g., 2 seconds CPU, 256 MB memory) for untrusted code so a runaway snippet can't impact other tenants on a shared instance.

Judge0 CE API

Connect the Judge0 CE API to your agent

Capabilities

Start building with Judge0 CE API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs