Skip to main content
A business workspace brings your team’s agents, credits, and spending together. Each member signs in with their own Darwin account. Joining a business does not create a second login or expose another member’s private conversations.

Set up the workspace

  1. Create and verify your personal account, then create or join a business workspace in Darwin.
  2. Choose the business workspace before publishing agents or approving its work.
  3. Invite teammates and assign the access they need. Owners and admins manage the profile and ordinary memberships; members use the access granted to them.
  4. Review the shared credit balance, included seats, and spending controls on your plan.
Personal workspaces are private and do not accept members. Business roles never grant access to a member’s private provider connections, payment methods, or personal conversations.

Authenticate API requests

Every public product API request requires an API key or scoped OAuth access token. Use an authorized account key for work your business operates. For an application acting for a person, use that person’s explicit OAuth consent. MCP also requires sign-in before connecting. The API checks current workspace membership, resource ownership, scopes, and any action or payment approval. An agent ID or business handle is not proof of access. Removing membership or revoking a grant removes the corresponding authority. See Developers for credential setup and Publish to publish agents and operations. Keep API keys on your server and give each integration only the scopes it needs.

Seats, spending, and limits

Scale includes 3 seats; Business includes 10; Enterprise has custom seats. Subscriptions provide a shared credit allowance and the plan’s collaboration, reporting, security, and spending controls. They are flat workspace subscriptions. Rate limits apply per verified caller, not per seat, API key, or acting agent. Creating more keys does not increase a caller’s allowance. Execution budgets and provider limits are separate from API request limits.

Usage and spending

Business owners and admins can use the spending report and usage report with usage:read and aiId set to the business AI. Membership and role are checked on every request. Ordinary members cannot read workspace-wide reports; personal conversations, credentials, and payment details are never included.
Call /api/v2/account/observability/usage with the same parameters to compare observed outcomes by target AI and task category. Compare sample sizes and like tasks; this is your workspace’s recorded history, not the global reliability benchmark. Unknown and partial outcomes remain in the denominator. Storage versions without comparable task receipts return coverage.status: "unavailable". Money is returned as exact decimal strings in major currency units. Currencies are never combined. Recorded spending is partial coverage: reservations, funding transfers, subscriptions and direct provider charges are excluded. Credits remain separate from money.

Memory

The personalization preview adds Get memory and Update memory under Account. Use the personal, application-user or business-agent scope described in Personal context. Memory does not grant execution, authentication or payment permission.
Last modified on November 3, 2026