Quickstart
Hosted aeqi, from account to first Company loop. MCP is a developer integration path after your Company exists.
The hosted quickstart uses four surfaces:
| Surface | Entry |
|---|---|
| App | Hosted dashboard at https://app.aeqi.ai |
| API | REST API mounted by the hosted platform |
| MCP | aeqi mcp against the selected Company runtime |
| CLI | aeqi chat, aeqi mcp, and related hosted-client commands |
1. Create a Company
Start from the hosted app:
https://app.aeqi.ai/signup
Hosted access is currently waitlist-gated: without an invite, the signup page adds you to the waitlist; with an invite you sign up directly.
See Getting started for the full app walkthrough.
2. Configure
Create API keys from the dashboard when you want to connect MCP or CLI clients:
- Account key (
ak_...) from Account -> API. Sent asX-Api-Key; it identifies which account you are. - Secret key (
sk_...) from the Company API keys page. Sent as the Bearer token; it selects which Company runtime to drive.
Hosted plans include monthly runtime credits for normal agent execution.
3. Connect
AEQI_SECRET_KEY=sk_... AEQI_API_KEY=ak_... aeqi mcp
AEQI_API_URL defaults to https://app.aeqi.ai, so you can omit it against hosted
aeqi. Set it only to point at a different deployment:
AEQI_SECRET_KEY=sk_... AEQI_API_KEY=ak_... AEQI_API_URL=https://app.aeqi.ai aeqi mcp
The CLI authenticates with the platform and routes tool calls into your managed Company runtime.
4. Open the dashboard
https://app.aeqi.ai
Sign in, open your Company, and run the first Quest.
Next Steps
- Concepts: Agents — the agent tree and identity model
- Concepts: Quests — how work gets dispatched
- CLI — terminal chat, local runtime, and MCP bridge
- REST API — hosted HTTP surfaces
- MCP Integration — drive your hosted Company from Codex, Claude Code, or another MCP client
- Claude Code + aeqi — Claude-specific setup and hooks