Developers

API keys, REST gateway, MCP

Connect your own tools and AI assistants to moveos. Every request is scoped to your organisation.

API keys

An API key per organisation, sent as a Bearer token or an x-api-key header. Each key has scopes and reads only what they allow. Keys are made and turned off in Settings.

REST gateway

PostgREST-style reads per table, with select, filters and limit. Answers come back as JSON.

/api/rest/v1

MCP

An MCP endpoint for AI assistants, with tools such as search_leads. tools/list returns only the tools for the modules your organisation uses.

/api/mcp

Sample request · first five leads

GET /api/rest/v1/leads?select=id,name&limit=5
Host: moveos.co
Authorization: Bearer YOUR_API_KEY

# response
200 OK
[
  { "id": "…", "name": "…" }
]

MCP client configuration

{
  "mcpServers": {
    "moveos": {
      "url": "https://app.moveos.co/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

List the tools for your organisation

curl https://app.moveos.co/api/mcp \
  -H "Authorization: Bearer $MOVEOS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

No real key on this page. You get yours once access is granted.

Specs and discovery

The machine-readable descriptions agents and tools read.

Writes made with an API key wait as approvals in moveos until someone in the office approves them. How the platform is built

Agents as a product

moveos ships its own AI employees; connect them to the MCP surface above to extend them with your own tooling.

Meet the AI employees