Ironflow is pre-1.0: APIs can change between releases. Pin a version. What is ready →
SDKs & APIs Overview
Use this page to find the reference that you need. Each Ironflow SDK wraps the same server API. If your language has no SDK, you can call the API directly.
Pick by language
Section titled “Pick by language”| Language | Package | Reference |
|---|---|---|
| Go | github.com/sahina/ironflow-go/ironflow | Go SDK |
| Node.js | @ironflow/node | @ironflow/node |
| Browser | @ironflow/browser | @ironflow/browser |
| Python | ironflow (PyPI: ironflow-py) | Python SDK |
| Other | none | Use Ironflow from any language |
The Node and browser packages share types from @ironflow/core. The JavaScript SDK page shows how the three packages fit together.
Pick by task
Section titled “Pick by task”| You want to | Read |
|---|---|
| Know what each SDK can do | SDK Comparison |
| Check one capability across SDKs and transports | SDK Parity Matrix |
| Match user-function logs to a run and step across SDKs | SDK log correlation |
| Call the server over HTTP | REST API |
| See every server endpoint and service | API Reference |
| Serve push-mode functions from your own HTTP endpoint | Push Protocol |
| Check a push-mode handler against the protocol | Push Conformance |
| Let an AI agent inspect and operate a running server | MCP tools |
Run or script the ironflow binary | CLI Reference |
| Look up environment variables and defaults | Configuration |
| Publish events to NATS directly, and know what the server accepts and keeps | NATS trigger acceptance and retention |
| Find the names that Ironflow owns and your code cannot use | Reserved Names |