Skip to content

Install

Provisioning the CRED Agent Platform for a workspace is a single API call. No CLI, no infrastructure to stand up, no per-agent setup. The provisioning job returns in 120 seconds or less and leaves the workspace with all 14 agents registered, a default workspace config seeded, and billing attached.

Prerequisites

  • An active CRED workspace (team_id). If you do not have one, sign up at cred.co or ask your CRED contact to invite you.
  • An auth token with one of the following scopes:
    • agents.ops.override — platform-level provisioning.
    • team-admin on the target workspace — self-service provisioning.
  • A selected pricing tier (Starter, Growth, or Enterprise).

Provision in one call

curl -X POST "https://api.cred.co/api/v1/workspaces/{team_id}/agents/provision" \
  -H "Authorization: Bearer $CRED_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "tier": "growth"
  }'

Replace {team_id} with your workspace id. Replace growth with starter or enterprise as appropriate.

Response

{
  "status": "ready",
  "team_id": "ws_01HZY...",
  "tier": "growth",
  "agents_registered": 14,
  "provisioned_at": "2026-04-22T14:03:11Z",
  "ready_in_seconds": 78
}

Provisioning is idempotent. Calling it again on a ready workspace is a no-op.

What gets seeded

The first successful provisioning call writes a default workspace config. These values can be changed later via the workspace settings API or UI.

Setting Default
default_model claude-sonnet-4.5
default_budget_usd_per_plan 5.00
notification_channels.slack null (connect in workspace settings)
notification_channels.email null (connect in workspace settings)
notification_channels.mobile_push true
data_residency inherits workspace.data_residency

After provisioning, all 14 agents appear in the workspace catalog, scoped to the permissions of the tier you chose.

Timing

Provisioning completes in 120 seconds or less. If the API returns "status": "pending", poll the same endpoint until "status": "ready".

Next steps

  • Connect Slack and email in Workspace Settings → Notifications so the Intervention Hub can reach your team.
  • Review per-agent costs on the pricing page before pointing production traffic at the platform.
  • For enterprise-only controls (SSO, data residency, SLA) reach out to your CRED contact after provisioning your workspace under any tier.

Troubleshooting

Symptom Cause Fix
403 insufficient_scope Token is missing team-admin or agents.ops.override. Re-issue the token with the right scope.
409 already_provisioned Workspace is already set up. Safe to ignore; check the workspace catalog.
status remains pending after 120s Gateway job stalled. Page on-call for cred-mcp.