Enterprise & API

Overview

Beyond the sign-in wizard, Belong AI Deploy offers a REST API and a local MCP server for teams that want to provision agents programmatically instead of clicking through the wizard — for example, deploying from CI, managing a fleet from your editor, or batch-launching an agent per customer.

Deployment API

Create, monitor, and tear down agent deployments with a single request:

curl -X POST https://aideploy.co/api/enterprise/v1/deployments \
  -H "Authorization: Bearer $AIDEPLOY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "externalId": "acme-prod",
    "cloudProvider": "digitalocean",
    "cloudToken": "dop_v1_...",
    "region": "nyc3",
    "serverSize": "starter",
    "agentCount": 1,
    "tailscaleAuthKey": "tskey-auth-...",
    "selectedAIProviders": ["openai"],
    "agents": [{
      "name": "Acme assistant",
      "modelProvider": "openai",
      "authMethod": "consumer",
      "model": "gpt-5.5",
      "template": "general"
    }],
    "billingAcknowledged": true
  }'

Capabilities:

• Create single or batch deployments
• Real-time status polling and refresh
• Idempotent deployments via your own externalId
• Scoped API keys, stored as SHA-256 hashes
• Cloud tokens and other secrets are stripped before storage — never persisted in plaintext

MCP server

A local MCP server wraps the deployment API so AI coding assistants (Claude Code, Cursor, and other MCP-capable clients) can provision infrastructure through tool calls instead of raw HTTP.

• Transport: stdio — works with any MCP client
• Tools: capabilities, list, get, create, batch, destroy (6 total)
• Pre-flight capability validation before a deployment is submitted
• Same authentication and access control as the REST API

Batch and fleet deployment

Batch requests can deploy up to 25 agents in a single call, with per-deployment status tracking. Batch deployment, white-label, and SLA options are available on higher-volume plans — see aideploy.co/enterprise or talk to sales for access and pricing.

Security

• API keys are stored as SHA-256 hashes, not plaintext
• Cloud provider tokens are stripped from stored configuration after use
• Row-level security is enforced on enterprise data
• Keys are revocable and scope-enforced

Getting access

Programmatic/enterprise access is separate from the self-serve wizard. See aideploy.co/enterprise for current plans, or contact join@belong.net.

Related

• Quick Start — the self-serve wizard flow
• Cloud Providers