An org is the fundamental unit of collaboration and billing in Axis. Members of an org share its projects — which means they share the same job board, file locks, codebase index, and live notepad. When two developers commit to the same repo and both have agents running, those agents automatically see each other’s claimed jobs and file locks, so they coordinate instead of colliding. Every account starts as a one-person org, which means single users are completely unaffected until they invite someone.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/virsanghavi/axis/llms.txt
Use this file to discover all available pages before exploring further.
What an Org Provides
Every project inside an org is shared across all members. When you’re working solo, your personal org behaves exactly the same as it always has. The moment a second person joins, every tool call any agent makes —claim_next_job, propose_file_access, update_shared_context — operates against the same board. No per-machine setup, no sync step: the data lives in the org, not on any single machine.
The things members share:
- Job board — one atomic queue; two agents racing for the same job cannot both win
- File locks — an agent in your teammate’s clone sees locks set by an agent on your machine
- Codebase index —
search_codebasequeries the same up-to-date index for everyone - Live notepad —
update_shared_contextappends to a single shared scratchpad all agents read
Creating an Org
Open the org switcher
Go to useaxis.dev and click the org switcher in the dashboard header.
Create a new org
Select + new org, enter a name, and confirm. The account that creates the org becomes its admin automatically.
Inviting Teammates
Go to the /team page
Navigate to useaxis.dev/team while the org is active in the switcher.
Enter an email and choose a role
Type the teammate’s email address. Choose either member (can view and act on the board) or admin (can also manage members and billing).
Share the invite link
Axis generates a shareable invite link at
/invite/<token>. Send it to your teammate — they join by opening the link and logging in. No email delivery required; the link is the invite.Role Management
Roles are managed from the team table on the/team page. Admins can:
- Change roles — promote a member to admin or demote an admin to member
- Remove members — removing a member frees their seat immediately (prorated in Stripe)
Billing
Axis orgs are billed at $20 per seat per month, where the seat count equals the number of active members. Seats are added when a member joins and freed when they are removed, with Stripe handling proration automatically. Admins manage the subscription from useaxis.dev/billing. What’s free, and what’s paid:| Layer | Cost | What’s Included |
|---|---|---|
| Orchestration | Free for everyone | Job board, file locks, live notepad, sessions |
| Intelligence | Paid (Pro) | search_codebase (hosted), deep_search, index_codebase |
The X-Axis-Org Header
Agents may passX-Axis-Org: <orgId> as an HTTP header to explicitly select which org their calls act under. Without it, the hosted API resolves every call to the authenticated user’s personal org. This header is useful when an agent needs to act on behalf of a specific team org in a context where it is authenticated as an individual user.
.axis/axis.json (see Project Config) so agents resolve the correct org automatically without any per-call header.
Related
Project Config
Commit
.axis/axis.json to pin your repo to a shared org board so every teammate’s agents coordinate automatically.Connect Agents
Point Claude Code, Cursor, Codex, Windsurf, and other MCP clients at the hosted Axis server.