verapli
Sign inJoin free
Menu

Guides · ai · Verification-gated

Claude Console - organization, credits, workspaces and keys

Set up a Claude Console organization for the Claude API: buy prepaid credits, create a workspace per project or environment with its own spend and rate limits, and create a personal or service-account API key scoped to that workspace. Optionally an Admin API key for automation.

Researched · not yet run liveLast researched 25 October 2026 · Anthropic · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Who owns what

A Claude Console organization holds billing (prepaid credits) and members with organization roles. Inside it, workspaces separate projects or environments; every request runs in exactly one workspace. Keys act as a person (personal key) or a service account, or belong to a workspace (legacy).

  • Claude Console organization organisation owned by the company or the person
  • Default Workspace project · under Claude Console organizationAlways exists; cannot have its own spend limit.
  • Project workspace (e.g. "Production - <app>") projectoptional · under Claude Console organizationCreated by an org admin; own members, keys, spend and rate limits.
  • Service account otheroptional · under Claude Console organizationIdentity for shared or automated workloads so keys do not break when a person leaves.

Have ready

  • anthropic/api: The basic Console sign-up and first API key; this entry adds workspaces, scoped keys and limits.
  • An email address for the Console login (a company address is best for an organization). Needed for: Create or sign in to the Claude Console
  • Organization name and a short description of your use case. · Setup asks for organization and use-case details before payment. [7]Needed for: Create or sign in to the Claude Console
  • A payment card for prepaid credits. [6]Needed for: Buy prepaid credits

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Create or sign in to the Claude Console

    Sign up at platform.claude.com (you create the account yourself) and fill in organization and use-case details.

    • Guided by hand
    • Human step: You sign in

    Where: https://platform.claude.com/

  2. Buy prepaid credits

    As Admin or Billing role, open Billing and choose Buy credits; enter the amount and card yourself. Credits are available immediately. Optionally set auto-reload.

    • Guided by hand
    • Human step: You add payment details
    • After: Create or sign in to the Claude Console
    The provider says
    Purchased credits are available immediately. [6]

    Where: https://platform.claude.com/settings/billing

  3. Create a workspace for the project

    As an organization admin, go to Workspaces > Create workspace and give it a clear name such as "Production - <app>". Up to 100 workspaces per organization by default.

    • verapli co-pilot
    • Human step: You press submit
    • After: Create or sign in to the Claude Console
    If something goes wrong (1)
    • No Create workspace button.: Only organization admins can create workspaces; ask an admin or have your role changed. [1]

    Where: https://platform.claude.com/settings/workspaces/new

  4. Set the workspace spend and rate limitsoptional

    Select the workspace on the Workspaces page and set Spend limits (monthly cap and alerts); set rate limits on the Rate limits page. Limits can only be lower than the organization's.

    • verapli co-pilot
    • Human step: You press submit
    • After: Create a workspace for the project

    Where: https://platform.claude.com/settings/workspaces

  5. Create a service account for shared workloads (optional)optional

    For CI or production services, have an org admin create a service account and add it to the workspace, so the key does not depend on one person.

    • verapli co-pilot
    • Human step: You press submit
    • After: Create a workspace for the project

    Where: https://platform.claude.com/settings/service-accounts

  6. Create a workspace-scoped API key

    On API keys, choose Create key, name it, pick an expiration, set Linked account (yourself or the service account) and scope it to the workspace. The key is shown once; verapli captures it by selector into your env file.

    • verapli co-pilot
    • Human step: You press submit
    • After: Create a workspace for the project, Buy prepaid credits

    verapli captures ANTHROPIC_API_KEY here by plain code: encrypted in your browser, never shown to AI.

    If something goes wrong (3)
    • Create key button is disabled.: Your workspace role cannot create keys (Workspace User); ask an admin for Workspace Developer, or for a service account key. [3]
    • 400 error saying the key is not scoped to a workspace.: Send the anthropic-workspace-id header with the workspace's wrkspc_ id, or create a key scoped to that workspace. [2]
    • 401 authentication_error after some weeks.: The key expired; expired keys cannot be reactivated - create a new one. [2]

    Where: https://platform.claude.com/settings/keys

  7. Create an Admin API key (optional, for automation)optional

    Org admins can create an Admin key on Admin keys to manage workspaces, members, keys and usage reports by API. It has full admin access and no scopes.

    • verapli co-pilot
    • Human step: You press submit
    • After: Create or sign in to the Claude Console

    verapli captures ANTHROPIC_ADMIN_KEY here by plain code: encrypted in your browser, never shown to AI.

    Where: https://platform.claude.com/settings/admin-keys

  8. Check usage tier and spend cap

    New organizations may start in a lower Evaluation tier. Check the Rate limits page and use Request tier increase before a launch, since usage stops at the monthly cap until the 1st of the next month.

    • Guided by hand
    • After: Buy prepaid credits
    If something goes wrong (1)
    • 429 with error_code enforced_spend_limit_reached and no retry-after.: The monthly tier cap is reached; request a tier increase on the Rate limits page or contact support. [5]

    Where: https://platform.claude.com/usage/limits

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can get you bannedThe rules say

Usage Policy enforcement

Anthropic may warn, throttle, suspend or terminate access for Usage Policy violations, including using extra accounts to evade detection or a ban, or reselling/proxying access without authorisation. Plain-English summary, not legal advice. [8]

Can get you bannedThe rules say

The API is only available in Anthropic's supported countries and regions; giving access elsewhere breaks the Usage Policy. [9]

Can cost moneyThe rules say

Credits expire and are non-refundable

Prepaid credits expire one year after purchase (no extension) and purchases are non-refundable, so buy what you will use. [6]

Can cost moneyThe rules say

Archiving a workspace cannot be undone and archives every key created for it within seconds. [1]

Worth knowingThe rules say

You cannot set a spend limit on the Default Workspace - create a separate workspace if you want a hard cap per project. [1]

What you end up with

Env varSecretFormatWhat it is
ANTHROPIC_API_KEYsecretsk-ant-api03-…Personal or service-account API key scoped to the project workspace.
ANTHROPIC_WORKSPACE_IDnot secretwrkspc_…Workspace id (needed in the anthropic-workspace-id header only for keys not scoped to a workspace).
ANTHROPIC_ADMIN_KEYsecretsk-ant-admin01-…Admin API key for organization automation; keep out of application runtime.

Renewals

  • Prepaid credits expire: every 1 year from each purchase [6]
  • API keys with an expiry must be replaced (warning email 7 days or 1 day before, depending on lifetime): every the expiration chosen at creation [2]

Pricing

  • Costs: Prepaid usage credits charged per successful call at current model pricing; auto-reload optional; monthly invoicing only via Sales.
  • Monthly spend caps by tier - Start $500, Build $1,000, Scale $200,000; Custom has no cap.

Source [6]

For agents

The same entry as JSON: /api/v1/entries/anthropic/console-and-workspaces · requirements /api/v1/requirements/anthropic/console-and-workspaces · terms /api/v1/terms/anthropic/console-and-workspaces.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Claude Console - organization, credits, workspaces and keys, and how long will it take?"
  → tools/call requirements { "provider_id": "anthropic/console-and-workspaces" }

Sources

  1. Workspaces - Claude Platform Docs Default Workspace cannot be renamed/archived/deleted; max 100 workspaces per org by default; only org admins create workspaces; workspace roles; workspace spend limits (not on Default Workspace) and rate limits below org limits; archiving is irreversible and archives the workspace's keys; Claude Code workspace auto-created; Admin API endpoints for workspaces and members. · accessed 25 October 2026 · official
  2. Authentication - Claude Platform Docs Key types (personal, service account, legacy workspace key); create at settings/keys with expiration (3 hours, 1 day, 7 days, 30 days, custom, Never) and Linked account; expiry warning emails; anthropic-workspace-id header required for keys not scoped to a workspace; Disable is reversible, Delete is permanent; Workload Identity Federation as keyless alternative. · accessed 25 October 2026 · official
  3. Get your Claude API key - Claude Platform Docs Create an account at platform.claude.com; key shown once and starts with sk-ant-; Create key disabled means your role lacks permission. · accessed 25 October 2026 · official
  4. Create an Admin API key - Claude Platform Docs Admin keys created at settings/admin-keys by org admins only; prefix sk-ant-admin01-; full access, no scopes; shown once. · accessed 25 October 2026 · official
  5. Rate limits - Claude Platform Docs New orgs may start in the Evaluation tier below standard limits; tiers Start/Build/Scale with monthly spend caps $500/$1,000/$200,000; usage pauses at the cap until the 1st of next month (429 enforced_spend_limit_reached); Request tier increase on the Rate limits page. · accessed 25 October 2026 · official
  6. How do I pay for my Claude API usage? - Claude Help Center Prepaid usage credits bought by Admin or Billing role on the Billing page; available immediately; auto-reload; credits expire one year from purchase and cannot be extended; all credit purchases non-refundable; access stops when credits run out; invoicing via Sales. · accessed 25 October 2026 · official
  7. How can I access the Claude API? - Claude Help Center Setup asks for organization and use-case details before payment details (search excerpt). · accessed 25 October 2026 · official
  8. Anthropic Usage Policy Anthropic may warn, throttle, limit, suspend or terminate access; bans coordinating multiple accounts to evade detection, circumventing a ban via another account, reselling/proxying access without authorisation, and access in violation of the Supported Regions Policy. Page showed an effective date of 2026-11-12 [to verify]. · accessed 25 October 2026 · official
  9. Anthropic supported countries and regions API and developer platform available only in the listed countries and regions (United Kingdom listed). · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Anthropic is not affiliated with verapli.