Skip to content

AILANG Executor status

Answered our latest tool-list check 4 hours ago with 28 tools. It will be marked verified after 3 successful checks in 7 days.

Answered (30 days)
2 of 2 checks
Last seen working
17 Nov, 06:16 UTC
Last commit
—
Licence
Not stated

Live checks

We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.

  • Answered
  • Needs sign-in
  • No answer
Checked (UTC)ResultResponse timeTools
17 Nov, 06:16Answered1.9 s28
16 Nov, 06:15Answered3.6 s29

Tools (28)

Read from the server on 17 Nov 2026.

ailang_builtins
List AILANG builtin functions with documentation, grouped by module. `search` filters lines case-insensitively; empty returns everything.
ailang_check
Type-check AILANG source. `code` is a whole module; the module line may be omitted or be `module main`. Returns the ai-check JSON report on stdout: check.passed and check.errors (with locations and fixes), and verify: each function's requires/ensures proved with Z3 (verify.results: verified, counterexample with a witness, or inconclusive after 5s per function). Only `pure` functions (or `! {}`) ar
ailang_eval
Evaluate one pure AILANG expression and print it with show(). Builtins are in scope; for stdlib functions (map, filter, ...) use ailang_run with explicit imports.
ailang_prompt
Call this FIRST: the AILANG teaching prompt (syntax rules, templates, stdlib map). AILANG is not in your training data the way Python is; code written without this prompt rarely type-checks.
ailang_run
Run AILANG source in the hosted sandbox. Entry point is `main`, with no arguments. Only the IO capability is granted (println works; FS, Net, Process, Env and AI are refused by name before the program starts), and the run is killed at the policy timeout. stdout is the program's output; stderr carries the policy decision JSON.
ailang_versions
List all AILANG versions the server can answer for.
benchmarks_compare
Two models side by side across every banked run: passes, runs, pass rate, cost and failures by category. Model names are as benchmarks_list gives them.
benchmarks_for_model
Where does a given model pass/fail? Optional version filter. Output: {passes: [...], fails_by_category: {...}, total_cost}
benchmarks_list
List benchmark suites and runs, optionally filtered to a since_version cutoff.
changelog_for_version
What changed in a given release (added/changed/fixed/breaking).
design_doc
Full design doc by slug (e.g. "m-agent-mcp-website"), as markdown. Long documents are cut at 30,000 characters and say so; url opens the whole one.
design_docs_list
List planned/implemented/rejected design docs, optionally filtered by version. state = "planned" | "implemented" | "rejected" | ""; empty = all.
docs_nav
The AILANG docs site's navigation tree for a version, as JSON: section and page titles with their paths.
docs_search
Full-text search of the AILANG documentation for a version (case-insensitive, on page titles and text). Returns the top 10 matches, docs pages before archived teaching prompts, each with its path, title, first 10 headings and an excerpt around the match.
effects_catalog
All declared effects with capability mapping and the version they appeared in.
example_for_concept
Best-fit examples for a free-form concept query ("how do I use effects?"). Filters server-side on why + title; returns up to 5 matches.
example_get
Full source of one example by path (as examples_list gives it, e.g. "runnable/hello.ail"; a leading "examples/" is accepted), at the release.
examples_list
Examples in the release's manifest (examples/manifest.json at its tag). features = comma-separated tags ("effects,records"); empty = no filter. status = "working" | "broken" | "aspirational" | "" ("passing" = working, "failing" = the other two); empty = working only. At most 50 are returned; total says how many matched.
executor_whoami
Which account this connection is signed in as (its user ID) and which app connected it (for example claude.ai or chatgpt.com).
install_guide
Harness-aware install instructions for AILANG. harness: "claude-code" | "gemini-cli" | "codex-cli" | "manual" | "build-from-source" | "" platform: only meaningful for "manual" (e.g. "darwin-arm64", "linux-amd64"); ignored otherwise Empty harness returns ALL harnesses + the remote_mcp config block.
limitations_list
Known limitations (Y-combinator, etc.) optionally filtered by category.
onboarding_guide
Step-by-step guide to getting started with AILANG, for an AI coding agent and for a human developer. role: "agent" | "developer" | "" (both). The guide for both roles is returned whatever role says; pick the part you need.
prompt_get
Fetch the canonical teaching prompt for a version. kind = "" (the full prompt) | "agent" | "devtools".
roadmap
What's shipping next, what's been rejected and why: the roadmap page of the AILANG site, generated from the planned design docs, as markdown.
stdlib_module
Full module: exports + signatures + docstrings.
stdlib_modules
List stdlib modules available in this AILANG version with one-line summaries.
stdlib_search
Find stdlib functions by name, signature, or keyword. Filters the pre-built search index server-side; returns top 20 matches.
submit_feedback
Send a bug report, feature request, documentation gap or limitation about AILANG to the AILANG team. Use it only when the user asks to report something, and leave out personal or confidential information. Categories: bug, feature, docs, limitation. Body up to 10 KB, snippet up to 4 KB. `contact` is optional, for a reply. `package` (vendor/name) sends the report to that AILANG package's maintainers