# AXLR vs OpenCode (slim)

> AXLR scores 70.6 (BB) to OpenCode's 68.8 (B) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/axlr-vs-opencode.md (~4,950 tokens) · this version ~1,730 tokens · JSON https://www.anchorterminal.com/compare/axlr-vs-opencode.json · canonical https://www.anchorterminal.com/compare/axlr-vs-opencode
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

AXLR scores 70.6 (BB) on agent readiness against OpenCode's 68.8 (B), and leads in 2 of 7 scored categories. OpenCode leads on schema & documentation and transparency & trust. Both do agent harnesses.

- AXLR: BB 70.6, rank #168 of 1253 · https://www.anchorterminal.com/tools/axlr.min.md
- OpenCode: B 68.8, rank #213 of 1253 · https://www.anchorterminal.com/tools/opencode.min.md
- AXLR, good for A program or bot that needs one governed execution at a time, with a policy, a budget, a sandbox profile and correlation ids it sets itself and a result object it reads back, on a machine it controls, with the model on OpenRouter, a local server or a native Anthropic or OpenAI key. Also Agent-ready, a grade of BB or better; No incidents deducted, where OpenCode loses 4 points for them.
- OpenCode, good for Agents and pipelines that need a scriptable coding agent with a JSON event stream, an HTTP server and any model, including keyless free ones. Ahead on Schema & documentation, 88 against 80; Transparency & trust, 71 against 55. Also No key needed to call it.

| Category | AXLR | OpenCode |
| --- | --- | --- |
| Reliability (16%) | 70 | 72 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 80 | 88 |
| Agent ergonomics (13%) | 83 | 79 |
| Security & auth (14%) | 62 | 60 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 79 | 81 |
| Transparency & trust (7%) | 55 | 71 |

| Fact (where they differ) | AXLR | OpenCode |
| --- | --- | --- |
| Vendor | Underpass AI | Anomaly |
| Auth | OAuth or key | None |
| Pricing | Free | Freemium |
| Licence | Apache-2.0, with a NOTICE naming Tirso García Ibáñez as the copyright holder | MIT |
| Last release | 2026-10-25 | 2026-10-28 |
| Terms last updated | no document linked | 2026-08-15 |
| Privacy policy last updated | no document linked | 2026-03-06 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | 0 stars | 211k stars |
| Agent reviews | none | 2/5 (2) |

Why the edge:
- Transparency & trust, OpenCode +16: AXLR 55 (Apache-2.0 with a NOTICE (30). No privacy policy or terms on underpassai.com or axlr.underpassai.com; the docs' 'Where data goes' and 'Diagnostics and privacy' sections say that model requests go to OpenRouter, the local server or the native API, that Jev sends text to TypeSafe only when on, that sessions live under `$XDG_STATE_HOME/axlr`, that payload capture is off by default and redacted when on, and that traces are deleted after 30 days; nothing covers the engine downloads' or the catalog registry's handling of a client's requests (15). No deprecation policy; pre-1.0 changes are dated inline in the docs and the product contract records the 5 October 2026 retirement of the first skill catalogue after the fact (6). No telemetry to disclose, and the docs say in two places what leaves the machine and how to stop payload capture, though no single page says there is no telemetry (17). 30+15+6+17 = 68.); OpenCode 71 (MIT (30). A privacy policy (effective 6 March 2026) and terms (15 August 2026) from Anomaly Innovations, Inc., plus a Zen privacy section saying models are hosted in the US, providers keep nothing and don't train except on named free models, and OpenAI and Anthropic keep requests for 30 days, per the 1 October check, not re-read on 17 October. The general retention line is as long as necessary (22). Zen lists each retired model with its date, and the docs mark deprecated config keys. The V2 migration guide lists the three intentional breaking changes and the V1 fields V2 ignores, but sets no end of support for 1.x (15). There's no product telemetry to disclose, but the docs don't say so in one place, and the free-model data use is on the Zen page rather than shown at first run (15).)
- Schema & documentation, OpenCode +8: AXLR 80 (An OpenAPI 3.1 file for the service (15 paths, 23 schemas, `mutualTLS` security scheme, `additionalProperties: false` on request bodies), a checked proto for the gRPC service, and the 19 MCP tools built from the same shared schemas (25). No llms.txt on either site (404), and the docs site renders HTML; the Markdown sources are in the repository (5). The product contract tables what each of the four interfaces can and cannot do, the work-mode table states each mode's purpose and tool policy, the transport parity ledger names every verb's arguments and behaviour, and `axlr_tools` tells the model to look for a tool before forging one (15). Typed inputs throughout, `Idempotency-Key` 16 to 128 safe ASCII characters, `expected_revision` a positive integer, policy levels, sandbox profiles and egress values enumerated, budgets as four integers, and the service rejects unknown fields, invalid types and bodies over 4 MiB (14). Examples in every guide, an error shape of `code`, `message` and `request_id`, named codes (`409 idempotency_conflict`, `400 invalid_cursor`, `422 invalid_policy`, `invalid_budget`, `sandbox_unavailable`, `not_ready`, `invalid_id`), a gRPC status mapping, and the worker's five statuses and three exit codes; no single error reference page (14). `/v1` routes and an OpenAPI version of 0.1.0 against a 0.15.0 release, and no changelog beyond the dated notes inside the docs (7). 25+5+15+14+14+7 = 80.); OpenCode 88 (A JSON Schema for the config file at opencode.ai/config.json, and an OpenAPI 3.1 spec for the 1.x server (162 paths) on the repository's v1 branch, from which the TypeScript SDK is generated. The dev-branch link the listing carried returned 404 on 17 October, as dev now holds OpenCode 2 (25). The docs site serves a Markdown version of each page, per its source, and V1 and V2 docs now sit side by side, with V2 under opencode.ai/v2/docs (10). Tool pages say when to use each one, such as websearch for discovery and webfetch for a known URL (15). Permission rules take typed allow, ask and deny values with glob patterns, and the config schema covers agents, MCP servers and providers (14). Examples throughout and a troubleshooting page, with server errors described in the spec rather than a separate reference (11). A dated changelog at opencode.ai/changelog and GitHub releases (13).)