Proves AI-generated Python does what you asked: syntax, lint, types, an AST security policy and a credential scan, then runs the code in a throwaway container against the examples you state and repairs it until they pass — returning a fix only when running it satisfies every one of them. Send what the code was supposed to do in options.examples (assertions or doctest lines): it is the only check that can fail code which parses, lints, types and runs. Validate every edit; run execute_python once a function is finished and again only when its behaviour changed. Repeating a call within ten minutes is answered from the previous answer and costs nothing.
9 verified, 0 failed, 0 observed risk, 1 not checked, on 22 November 2026. No total and no grade: each check says what it found, and one that could not run says why.
Every x402 payment we hold to the address the catalogue lists for this server’s paid tools (0xaa71…7104), payments an address made to itself left out. The same address takes payment for 3 other catalogued services, so these figures are an upper bound for this server.
3 tools on the last day the list was read, fingerprint bda0f630ad034e7a630.
Execute Python
Everything repair does, and then RUNS the code in a throwaway container — no network, read-only filesystem, killed at options.timeout_s — reporting exit code, stdout and stderr. Any '>>>' examples in the code are run too, and one that does not print what it says is an error the other tools cannot see. This is a side effect: do not submit code you do not want executed. Use it when you need proof that the code runs, or that it does what it says. Alternatives: validate_python for the diagnosis and repair_python for the fix, neither of which runs anything. Auth: a key is required. This call needs a paid key and answers HTTP 402 without one. Credits are bought without an account, 10 per call: GET /v1/pricing says where to send the xDAI. Or pay for this one call with no key at all: call it without one and the result carries x402 payment requirements ($0.1 in USD Coin on eip155:8453); sign them and repeat the call with the payment in _meta['x402/payment']. Arguments: code: the whole file, 1..200000 bytes of UTF-8 measured after encoding (empty is refused with 400, larger with 413); a fragment is fine, but line and column numbers in the answer count from 1 in what you sent. language: must be 'python'; anything else is 400, and the field may be omitted. options.max_iterations (1..10, default 3) caps the fix/verify rounds: raise it for a file with several independent faults, leave it for a snippet. options.optimize (default false) additionally folds constants and drops dead code, and …
changes stateadditive onlysafe to repeatclosed worldas the server describes it; we do not call tools
| Name | Type | Required | Description |
|---|---|---|---|
| code | string | yes | The source to check, as a whole file where possible: diagnostics carry the line and column of the text you send, and a fragment hides the imports and definitions the type check needs. A deployment may accept fewer bytes than the 200000 here. |
| language | — | no | The language of the code. A service that does not handle it refuses the request rather than guessing; the enum is shared across services, so it lists more than any one of them accepts. |
| options | — | no | Tuning knobs. Most of them only take effect in the mode that does the corresponding work; see each field. |
No agent registration names this server; we probe it on our own list.
A day counts as answered only when every timed run that day got every request answered; the hourly runs began 5 November 2026. Days before the hourly runs are read from the daily probe, one request a day, so a short outage between probes is not seen; hovering a day says which. Any HTTP response below 500 is an answer, so a server that asks for credentials is answering.
| Day | State | Timed runs | From |
|---|---|---|---|
| 2026-11-22 | Answered | 14 | hourly runs |
| 2026-11-21 | Some runs failed | 23 | hourly runs |
| 2026-11-20 | Answered | 24 | hourly runs |
| 2026-11-19 | Answered | 23 | hourly runs |
| 2026-11-18 | Answered | 24 | hourly runs |
| 2026-11-17 | Answered | 23 | hourly runs |
| 2026-11-16 | Answered | 24 | hourly runs |
| 2026-11-15 | Answered | 23 | hourly runs |
| 2026-11-14 | Answered | 24 | hourly runs |
| 2026-11-13 | Answered | 23 | hourly runs |
| 2026-11-12 | Answered | 23 | hourly runs |
| 2026-11-11 | Answered | 23 | hourly runs |
| 2026-11-10 | Answered | 24 | hourly runs |
| 2026-11-09 | Some runs failed | 23 | hourly runs |
| 2026-11-08 | Answered | 24 | hourly runs |
| 2026-11-07 | Answered | 18 | hourly runs |
| 2026-11-06 | Answered | 23 | hourly runs |
| 2026-11-05 | Answered | 4 | hourly runs |
Each day: the median of that day’s runs’ p50 (the line) and of their p95 (the top of the band), in milliseconds, from our server in Europe to the response headers of an MCP initialize request. An observation, not a threshold.
| Day | p50 ms | p95 ms | Runs |
|---|---|---|---|
| 2026-11-22 | 28 | 111 | 14 |
| 2026-11-21 | 29 | 117 | 22 |
| 2026-11-20 | 28 | 121 | 24 |
| 2026-11-19 | 28 | 134 | 23 |
| 2026-11-18 | 28 | 146 | 24 |
| 2026-11-17 | 28 | 138 | 23 |
| 2026-11-16 | 28 | 141 | 24 |
| 2026-11-15 | 28 | 123 | 23 |
| 2026-11-14 | 29 | 122 | 24 |
| 2026-11-13 | 28 | 133 | 23 |
| 2026-11-12 | 29 | 142 | 23 |
| 2026-11-11 | 28 | 124 | 23 |
| 2026-11-10 | 27 | 122 | 24 |
| 2026-11-09 | 29 | 131 | 22 |
| 2026-11-08 | 27 | 128 | 24 |
| 2026-11-07 | 27 | 113 | 18 |
| 2026-11-06 | 28 | 107 | 23 |
| 2026-11-05 | 27 | 96 | 4 |
Each hour: the median p50 of that hour’s runs, times in UTC; the shaded last hour is not complete. A run with no answer is not on the line: a short red tick under its hour marks it. Latest run 22 November 2026, 13:38 UTC: 5 of 5 requests answered, p50 34 ms, p95 111 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-22 14:00 (now) | — | 0 | 0 |
| 2026-11-22 13:00 | 34 | 1 | 0 |
| 2026-11-22 12:00 | 30 | 1 | 0 |
| 2026-11-22 11:00 | 27 | 1 | 0 |
| 2026-11-22 10:00 | 30 | 1 | 0 |
| 2026-11-22 09:00 | 26 | 1 | 0 |
| 2026-11-22 08:00 | 26 | 1 | 0 |
| 2026-11-22 07:00 | 32 | 1 | 0 |
| 2026-11-22 06:00 | 30 | 1 | 0 |
| 2026-11-22 05:00 | 27 | 1 | 0 |
| 2026-11-22 04:00 | 28 | 1 | 0 |
| 2026-11-22 03:00 | 26 | 1 | 0 |
| 2026-11-22 02:00 | 27 | 1 | 0 |
| 2026-11-22 01:00 | 28 | 1 | 0 |
| 2026-11-22 00:00 | 29 | 1 | 0 |
| 2026-11-21 23:00 | 34 | 1 | 0 |
| 2026-11-21 22:00 | 30 | 1 | 0 |
| 2026-11-21 21:00 | 34 | 1 | 0 |
| 2026-11-21 20:00 | 30 | 1 | 0 |
| 2026-11-21 19:00 | 26 | 1 | 0 |
| 2026-11-21 18:00 | 26 | 1 | 0 |
| 2026-11-21 17:00 | 32 | 1 | 0 |
| 2026-11-21 16:00 | 37 | 1 | 0 |
| 2026-11-21 15:00 | — | 1 | 1 |