AILANG Docs

List all AILANG versions the server can answer for.

One run's full result (code, compile_ok, runtime_ok, stdout_ok, cost, tokens).

Pairwise model comparison. Output: {a_only_passes, b_only_passes, both, neither}

Where does a given model pass/fail? Optional version filter. Output: {passes: [...], fails_by_category: {...}, total_cost}

List benchmark suites and runs, optionally filtered to a since_version cutoff.

What changed in a given release (added/changed/fixed/breaking).

Full design doc by slug (e.g. "m-agent-mcp-website").

List planned/implemented/rejected design docs, optionally filtered by version. state = "planned" | "implemented" | "rejected" | ""; empty = all.

Sidebar tree as JSON. Replaces scraping the Docusaurus sidebar. Version-scoped: snapshot of that release's docs site nav.

Full-text search across doc Markdown for the given version. Filters server-side on lowercased body + title; returns the top 10 matches, docs pages before archived teaching prompts (prompts/v*.md match almost any query), each as path, title, its first 10 headings and an excerpt around the match: the full page is a docs_nav / example_get away. Whole bodies made one search ~30 KB, too much for a tool result in a listed connector.

All declared effects with capability mapping and the version they appeared in.

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.

Full source + metadata for one example by path.

Filter examples that pass under for_version, optionally by features/status. features = comma-separated tags ("effects,records"); empty = no filter. status = "passing" | "failing" | ""; empty = passing only.

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.

Known limitations (Y-combinator, etc.) optionally filtered by category.

Stepwise onboarding flow for using AILANG. role: "agent" (AI coding agent flow, default) | "developer" (human dev flow) | "" (returns both) For v1 returns the full guide; client picks the relevant role. v2 may filter on AILANG side once we have proper record-projection helpers.

Fetch the canonical teaching prompt for a version. kind = "agent" | "devtools" | "compact" (full prompt = empty).

What's shipping next, what's been rejected and why.

Full module: exports + signatures + docstrings.

List stdlib modules available in this AILANG version with one-line summaries.

Find stdlib functions by name, signature, or keyword. Filters the pre-built search index server-side; returns top 20 matches.

Anonymous bug report / feature request / docs gap, queued for human review. Default routing: `public-feedback` inbox (general AILANG). Pass `package="vendor/name"` (e.g. "sunholo/auth") to route to that package's `pkg:vendor/name` inbox where its autonomous agent watches. Categories: bug, feature, docs, limitation. Body limit 10KB, snippet limit 4KB. Optional contact field for follow-up; opaque to the server. Set `auto_dispatch=true` to authorize the package agent to act on your submission immediately (default false — files for human triage; pkg-feedback agent template lands in a separate sprint).