Developer Platform
This section is the main path for developers building with Aionis. It explains what to install, how to run the local Runtime, and which integration path to choose before you read the deeper product pages.
Start with npx aionis setup. From there, connect the surface that matches your
host: TypeScript SDK, raw HTTP, MCP bridge, AIFS, Substrate, native plugins,
multi-agent host contracts, or Memory Firewall for external memory backends.
Recommended Path
| Step | Page | Result |
|---|---|---|
| 1 | Quickstart | Install a local Runtime with npx aionis setup. |
| 2 | Concepts | Understand state, admission, feedback, and memory types. |
| 3 | Guides | Wire the Runtime loop into your Agent host. |
| 4 | Integrations | Connect SDK, HTTP, MCP, AIFS, or external memory. |
| 5 | Product Reference | Deep-dive each product surface. |
| 6 | Operations | Configure embeddings, storage, and security. |
What To Read Next
- Use Execution Memory if Aionis will record and adjudicate task history.
- Use Memory Firewall if you already have Mem0, Zep, a vector DB, markdown notes, or another memory backend.
- Use Substrate if you want durable evidence, stronger ordinary-memory recall, backup, migration, or preview context.
- Use Task Context Profiles when one Runtime serves different host tasks such as coding verification, long QA, multi-agent handoff, loop engineering, or document integrity.
- Use Migration if you are adopting Aionis over an existing memory backend.
- Use Guides when you are wiring the Runtime loop into an Agent host.
For HTTP endpoint details, see API Reference.
Last updated on