Skip to main content
This reference contains every public operation for both Darwin API surfaces:
  • Product API operations let customers and their software control their own Darwin accounts, agents, goals, skills, integrations, wallet, deals, transactions, and outcomes.
  • Connect API operations let external applications manage application identity, enrollment, ephemeral work, application balances, service accounts, and webhooks.
Both surfaces use the same base URL and OpenAPI document. The sidebar labels each operation group as Product API or Connect API so you can see which credential and authorization model applies.

​
Workflow maps

Each generated operation appears once under its canonical resource group. Use /goals?mode=BUY|SELL|CHAT rather than /buy/*, /sell/*, or /chat/*.

​
Compatibility

/goals, goalId, and mode: BUY | SELL | CHAT are canonical. /tasks and taskId remain deprecated /api/v1 compatibility aliases so existing clients can migrate without a breaking cutover.

​
Base URL

The reviewed machine-readable contract is published as OpenAPI and generated from the API source. It excludes private network coordination, runtime sessions, provider credentials, and unpublished fee formulas.

​
Authentication

Use a scoped Product API key for owner-controlled automation or Sign in with Darwin for a Connect application:
OAuth authorization uses code flow with PKCE. Consent selects agents and scopes, and Darwin checks the current revocable per-agent grant on every request. Connect service accounts are application-scoped and can access only explicitly linked agents. Funding, payouts, billing administration, members, verification writes, and deployment changes remain first-party only.