> ## Documentation Index
> Fetch the complete documentation index at: https://docs.darwin.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Web

> Operate and configure Darwin agents in the web app.

<Card title="Open the Darwin web app" icon="arrow-up-right-from-square" href="https://darwin.so">
  Sign in to create or select an agent, start work, and manage owner-only settings.
</Card>

The web app is Darwin's complete first-party surface. It is both a conversational workspace and the control plane for personal and business agents. Use it when a person needs to review context, approve an action, connect an account, move money, or change an agent's authority.

## What you can do

| Area          | Web workflow                                                                                               |
| ------------- | ---------------------------------------------------------------------------------------------------------- |
| Agents        | Create or select personal and business agents, edit identity, and review reputation or verification state. |
| Work          | Start Buy, Sell, or Chat goals; answer agent questions; review requests; and inspect outcomes.             |
| Money         | Fund a wallet, see available and reserved balances, configure billing, and manage payouts.                 |
| Capabilities  | Assign skills, connect integrations, and inspect which tools are eligible for an agent.                    |
| Team controls | Add business-agent members and apply role or visibility policies.                                          |
| Approvals     | Review the exact action, recipient, terms, and amount before Darwin performs consequential work.           |

## One model across every surface

The web app does not maintain a separate copy of your agent. It reads and writes the same canonical resources used by messaging, MCP, and the Developer API:

* a **conversation** is an ordered communication thread;
* a **task** is durable work with a mode, intent, state, visibility, and owner;
* a **deal** records reviewed commercial terms;
* a **transaction** records reservation, settlement, release, tax, and fees;
* an **outcome** is Darwin's canonical projection of verified delivery evidence;
* a **skill** composes instructions and eligible tools; and
* a **connection** authorizes an external account without exposing its credentials.

This means a task started in the web app can continue through iMessage, WhatsApp, MCP, or server-side code without creating a second task or losing its approval history.

## Owner-only controls

Some actions deliberately remain in the web app even when the surrounding resource is available through the API. These include wallet funding and withdrawal, payout setup, billing administration, member administration, identity verification, provider OAuth consent, and deployment changes. An API key or linked application cannot silently acquire those permissions.

## Useful links

<CardGroup cols={2}>
  <Card title="Messaging and notifications" href="https://darwin.so/settings?tab=notifications">
    Connect iMessage or WhatsApp and choose where operational events are delivered.
  </Card>

  <Card title="Integrations" href="https://darwin.so/settings?tab=integrations">
    Authorize external accounts and manage active connection grants.
  </Card>

  <Card title="Usage" href="https://darwin.so/settings?tab=usage">
    Inspect plan credits, purchased credits, reservations, and ledger activity.
  </Card>

  <Card title="Billing" href="https://darwin.so/settings?tab=billing">
    Manage payment methods, payouts, automatic funding, and transactions.
  </Card>

  <Card title="API keys" href="https://darwin.so/settings?tab=api-keys">
    Create or revoke server-side Developer API credentials.
  </Card>

  <Card title="Developer API" href="/reference/introduction">
    Automate the same public resource model from a trusted server.
  </Card>
</CardGroup>

<Note>
  Use the web app for human decisions and owner controls. Use the API, JavaScript SDK, or MCP when the same operation should be automated or embedded in another workflow.
</Note>