Developers
Build on the platform that runs AIQuity Life.
Developer access is not open yet.
This is what building on it will mean, and what already runs in private use.
Examples are invented. Every part named is the product’s own.
Chakras
From a sentence to your own code.
A chakra starts as a description of what it keeps, with no code, and climbs only as far as it needs.
When it needs its own screen and logic, it is a small app the platform loads for you, with your data and tools handed to it.
- Keep recordsIn testing
- Keep records, with skillsBeing built
- Give it a faceBeing built
- Make it yoursBeing built
Agent tooling
Agents you can see inside.
Pattern Studio
Compose an agent from a palette of nodes, inspect each one, start from a template, or bring in an existing graph.
Registries
One place for every part an agent is made of: tools, skills, hooks, rules, commands and workflows.
Observability
Traces, sessions and prompts for every run, so a result can be explained, not just trusted.
The CLI
The platform, from your terminal.
Work offline
A local copy of a space, reconciled when you are back, with conflicts caught rather than overwritten.
Send work to AI workers
Coding jobs dispatched to the workers you use, from one queue, with a person holding the trigger.
Sync with your repository
Canvas and a git checkout kept in step, plus your commands, skills and rules synced to the tools you use.
Connections
Connect the tools you already use.
Connectors
Tool servers over the Model Context Protocol: pick one, authorise it once, and the companion can use it.
Chakra tools
Every declared chakra adds its own record tools to the same catalogue. Calling them from a conversation is being built.
What exists today
Full docs| Surface | What it does | State |
|---|---|---|
| Chakras (declared) | Describe what to keep; the records appear in five views, with no code. | Private beta |
| Chakras (built-in) | Micro-apps such as Timer Plus and Goals Lite mounted in the canvas. | Private beta |
| Chakras Pro | Build a chakra in the browser: editor, files, git, preview. | Private beta |
| Pattern Studio | Visual agent builder with a node palette, inspector and templates. | Private beta |
| Agent registries | Tools, nodes, patterns, skills, hooks, slash commands, rules, workflows. | Private beta |
| Observability | Traces, sessions, prompts and datasets for agent runs. | Private beta |
| MCP connectors in Juggernaut | Connect and authorise MCP tool servers from the chat input. | Private beta |
| The aiquity CLI | Terminal client and control plane; installs from a private registry today. | Private beta |
| Chakra Store | Browse and publish chakras. Not finished. | Coming |
| Public API keys and SDK | Not available. The REST API is not public. | Coming |
States follow production. Private beta means built and in internal use, not reachable by production users yet; coming means not built yet.
Be first to build on it.
Developer access opens after the dimensions. The waitlist hears first.