Platform
How to connect to Axisdream and what the public platform surface provides.
This page explains the public platform surface, not the internal implementation.
REST, SDK, and local MCP connections use an API key. Hosted MCP connections use OAuth when the chatbot signs in.
Authentication
Use bearer-token authentication for REST, SDK, and local MCP requests. Hosted MCP connections use the Axisdream OAuth sign-in flow instead of an API key.
Headers
Authorization: Bearer cs-YOUR_API_KEYEnvironment variables
export AXISDREAM_API_KEY="cs-YOUR_KEY"
export AXISDREAM_BASE_URL="https://api.axisdream.xyz"Spaces
- A space is the isolated home for one project, team, subject, or ongoing workflow.
- Each space keeps its own Markdown context, files, and public state.
- Space names and UUIDs both work in the public API.
- Fresh spaces start with a short setup flow before normal work begins.
Fresh spaces
- A fresh space starts with a short setup flow instead of normal retrieval.
- The connected AI asks one setup question first, then writes the initial context for the space.
- Templates provide a ready-made starting context, while blank spaces begin with this setup flow.
Connection surfaces
SurfaceUse it forConnection
REST API and SDKs
Build an application or automation
https://api.axisdream.xyz
Hosted MCP
Connect a web chatbot
https://axisdream.xyz/mcp
Local MCP
Connect a desktop or CLI host
npx -y axisdream-mcp@1.0.0
How to think about the app
- Use Integrations for the quickest first connection.
- Choose hosted MCP for a web chatbot, local MCP for a desktop or CLI host, and REST or an SDK for application code.
- Use one space for one project, subject, team, or area of responsibility.
- Think of Axisdream as the place where the context behind the work lives, while the connected AI does the task itself.