All docs

Docs · Reference

EXEC schemes and `txco://` builtins

Everything an EXEC can point at, including the complete registry of in-chassis builtins — so you don't have to read server.go to find them.

The schemes

SchemeRunsReference
http(s)://…Your service, over HTTPops.md
op://NAMESandboxed wasm nano-op on the chassisops.md, sdk/op
txco://…A chassis builtin (table below)this page
ai://chatA chat model via the chassis’s AI registryai.md
mcp+http(s)://…A tool on an external MCP servermcp.md
<stack>/<scope>Unschemed stage jump (synthesized into @goto)txcl.md

The builtin registry

BuiltinWhat it does
txco://noopReturns {}. Placeholder / structural.
txco://staticServe static files with layered lookup: the stack’s FILES/ → workspace FILES/ → embedded defaults. Caps: 1 MiB/file, 2048 files, 64 MiB total. See examples/quickstart-hello-world for the rule pattern.
txco://web-renderRead a source path, optionally render Markdown→HTML, set @web.res.*, halt. Pages without a backend.
txco://sendmailRender + submit outbound email from the _sendmail contract — see sendmail.md.
txco://hmac-signCompute an HMAC signature (key via WITH secrets.*).
txco://hmac-verifyVerify an HMAC, constant-time; result lands under @computed.*.
txco://basic-auth-encodeEncode user:pass to a basic-auth header value.
txco://copyPath-to-path copy inside the envelope (what SET can’t do with computed paths).
txco://detect-tenantBoot-pipeline: hostname/listener → tenant resolution. Used by the scaffolded _sys/boot rules; you rarely call it directly.
txco://routeBoot-pipeline: promote a routing proposal (@route.*) into @goto + @tenant. Companion to detect-tenant.
txco://continuation-resultPoll handler behind ?_txc.continuation=<id> (continuations). Wired by the chassis; not called from rules.

Builtins pay normal fuel and appear in traces like any other op. The current registry is assembled in chassis/server/server.go; if this table and the code disagree, the code wins — and this page needs a patch.

Edit this page · View as markdown