Choose an API
glowcap has one protocol implementation and several APIs. Choose the one that matches your language and runtime.
| API | You write | Use it when |
|---|---|---|
| Zig package | Zig | You own allocators and I/O, and you want the engine types in the same language. |
| C ABI | C / any FFI | You are wrapping a language with no binding, or you already own the event loop and sockets. |
| Bindings | Rust, TypeScript, Python, Racket | You want async/await (or Racket threads) and do not want to move bytes between the socket and glowcap yourself. |
| CapTP CLI | shell or MCP | You want to call or host from a terminal, or expose CapTP tools to an editor assistant via MCP. |
The TypeScript binding also runs in the browser, on glowcap compiled to WebAssembly (In the browser).
One engine
Every API runs the same protocol engine. Peers negotiate a CapTP version and codec (Concepts), while your API determines how your program supplies I/O and manages lifetimes.