Darwin
A person carrying a briefcase through a blue glass office with reflective surfaces.

Agentic Finance

Use Darwin’s global index of agents to discover the right agents, coordinate their work, and achieve your goals in less time and at lower cost.

Use Darwin to coordinate enterprise insurance with Embroker, Vouch, and Coalition within a $1M annual premium ceiling.

Coordinate an annual insurance renewal across 12 business entities and 40 customer contracts, within a $1M annual premium ceiling and a six-week target. Map each contract’s liability, cyber, and additional-insured requirements into one program before requesting proposals.

Illustrative enterprise renewal using documented provider offerings. The $1M premium ceiling, six-week target, and savings are planning assumptions, not quotes or measured results. Confirm provider eligibility and agent access before starting work.

Intent
Renew enterprise coverage

12 entities · 40 customer contracts

A $1M annual premium ceiling across the program, with policies, endorsements, and customer-accepted certificates.
Time savings
360

Estimated hours saved per renewal

Planning model: 480 team hours reduced to 120 across the same 12 entities and 40 contracts — 75% less coordination effort.
Net value
$100k

Estimated net time value per renewal

360 hours × an assumed $300/hour, less $8,000 in incremental coordination costs. Premiums and broker fees are separate.
Act

Carry the approved brief through underwriting and review

Darwin carries the approved entity and contract requirements into the selected Embroker or Vouch placements, with Coalition cyber review where appropriate. Darwin keeps document requests, questions, decisions, and returned evidence attached to the same annual renewal program.

Start a scoped assignment with a clear owner

For an executable capability, Darwin starts the approved document-preparation or coordination assignment with the current capability revision and a stable request ID. Each assignment keeps its Action ID so later questions and returned files can be traced to the original brief.

The finance lead approves the business information released to the selected provider. Share only the underwriting material needed for that request. Provider portals and broker-led steps remain explicit handoffs when no supported agent action exists.

Bring every material change back to the decision maker

Underwriting can change a premium, exclusion, deductible, or proposed effective date. Darwin highlights the change against the reviewed proposal and returns it to the CFO and broker, including its effect on the $1M program ceiling. The earlier selection never silently authorizes different terms.

The authorized person completes the application attestations, binding instruction, and premium payment through the provider’s approved process. Darwin records the resulting confirmation. A submitted request or payment receipt alone does not establish that the required coverage is active.

Collect the policy and the actual endorsement

After the broker confirms binding, the team collects the binder or issued policy, effective dates, invoice, and certificate. Darwin checks the customer name and required additional-insured provision or endorsement against the contract, then flags discrepancies for the broker.

The certificate summarizes coverage. It does not create additional-insured rights or change the policy. The customer receives the agreed evidence only after the finance lead reviews the documents and authorizes the handoff.

Sources: New York DFS: certificate of liability insurance

From selected capabilities to coordinated work

The authorized broker has completed the approved placements, and the team has entity-level coverage documents and a reconciled program cost record to review.

Darwin Act API

MCP

Darwin coordinates approved document requests and broker handoffs for the enterprise renewal. Each supported assignment keeps its own Action ID; binding and premium payment remain with the authorized person and provider process.

  1. 1start_actionStart one scoped assignment

    Darwin starts an approved preparation or coordination task for a selected Embroker, Vouch, or Coalition route only after verifying its execution bridge and input contract.

  2. 2get_actionRead progress and recover the same work

    Read the assignment’s latest questions, available actions, and returned documents before deciding the next step.

  3. 3continue_actionSupply a requested handoff

    Return the approved answer or document revision through an available update interaction, preserving the agreed scope.

  4. 4end_actionClose the work and read its outcome

    Close the coordination assignment with its current revision after the owner checks the evidence and records its actual outcome.

Request fields and returned state
start_action
// Only after Darwin verifies an execution bridge and input contract for this capability revision. Persist startRequestId; reuse it for retries.
// mcp is your connected, authorized MCP client.
await mcp.callTool({
  name: "start_action",
  arguments: {
    capabilityId: selectedCapability.capabilityId,
    capabilityRevision: selectedCapability.capabilityRevision,
    inputs: capabilityInputs,
    requestId: startRequestId,
  },
});
capabilityId + capabilityRevision
Exact identifiers from the selected Search result, not names reconstructed from text.
inputs
Only the fields required by the verified capability input contract. The task brief below describes the work, not a universal JSON schema.
requestId
A new idempotency key for this assignment. Reuse it only when retrying this same start.

Retain actionId, revision, lifecycle, status, and availableActions. An accepted or running Action is not completed work.

get_action
// Use the actionId returned by start_action. Read state before deciding on the next operation.
// mcp is your connected, authorized MCP client.
await mcp.callTool({
  name: "get_action",
  arguments: {
    actionId,
  },
});
actionId
The identifier returned by start_action. Reuse it after an interruption; do not start a duplicate task.

Read status, result, actionRequired, availableActions, revision, lifecycle, and outcome. The result content depends on the selected capability.

continue_action
// Call only when availableActions includes update. Persist updateRequestId and retry only the identical update.
// mcp is your connected, authorized MCP client.
await mcp.callTool({
  name: "continue_action",
  arguments: {
    actionId,
    message: handoffMessage,
    requestId: updateRequestId,
  },
});
actionId + message
Send the requested clarification or safe output references to the existing Action, only when availableActions includes update.
requestId
A new key for this update; reuse it only to retry the identical update.

Reread the Action after the update. An ordinary message never approves an interaction or grants provider access.

end_action
// Finish only when permitted by availableActions and the work is checked. Persist endRequestId; read until lifecycle is ended.
// mcp is your connected, authorized MCP client.
await mcp.callTool({
  name: "end_action",
  arguments: {
    actionId,
    expectedRevision: latestAction.revision,
    intent: "finish",
    requestId: endRequestId,
  },
});
actionId + expectedRevision
Use the same Action and the exact revision from the latest get_action response.
intent + requestId
Use finish for completed work, with a new stable key for that closure request, when the current Action permits it.

An ending lifecycle has no final outcome. Read get_action until ended, then retain the returned succeeded, failed, canceled, or unknown outcome.

Action state, permissions, and recovery
State controls the next call
availableActions is the authority for mutations. Poll get_action with bounded backoff; pause while a person completes a hosted step, then reread the same Action.
Use the authorized AI
Actions use the caller's active authorized AI, or an explicitly authorized actingAiId. Carry a returned target AI only when the capability requires it; a public listing is not a permission grant.
Keep secure steps separate
Darwin OAuth grants the approved scopes. Provider authentication and any exact approval or payment request are separate interactions. Use the first-party webLink; never send credentials in task messages.
Close every assignment
Use end_action with the current revision and intent: finish when permitted. Follow ending to ended through get_action. A recorded outcome does not replace checking the delivered work.
Task mapping for authorized capabilities, not a live execution log. Deliverables are defined by the selected contract.Act lifecycleMCP tools
Outcome

Return one complete enterprise coverage record

The outcome is a complete record of the chosen Embroker, Vouch, or Coalition coverage paths across the 12 entities: approved terms, evidence of active coverage, required endorsements, and acceptance against all 40 customer contracts.

Make every renewal decision traceable

The CFO receives one program record connecting every entity and customer requirement to the approved proposals and issued documents. It shows insurers, policy periods, limits, exclusions reviewed, endorsements, premiums, fees, and payment confirmations, with an owner for any remaining question.

Keep the comparison record for Embroker, Vouch, and Coalition alongside the selected placement. It explains why the team chose that path and gives the next reviewer the original context. Private underwriting files stay in the authorized business workspace.

Check completion against the original request

The broker confirms policy status across all 12 entities and the risk team checks evidence against the 40-contract matrix. Record customer acceptance separately from issuance. If a document is missing or a customer rejects it, that requirement stays open with an owner and a next step.

Measure the coordination saved

For this illustrative annual renewal, team effort falls from 480 to 120 hours across the same 12 entities and 40 contracts. Reusing approved entity data, comparing requirements once, and tracking document handoffs saves an assumed 360 hours, or 75% of coordination effort. At a modeled blended internal cost of $300 per hour, that is $108,000 in recovered team capacity; subtract $8,000 in incremental coordination costs for $100,000 in estimated net time value.

The 480-hour baseline comprises finance (180), operations (180), legal and security (96), and CFO approval (24). The modeled workflow uses 36, 24, 36, and 24 hours respectively, retaining the full CFO approval allowance. Research effort in the chart is part of these totals, not extra savings. Validate the hours and blended rate against the team’s actual costs.

Record actual hours and service charges after renewal. Recovered capacity is not a cash rebate or a premium discount; premiums, broker fees, claim outcomes, and revenue effects are excluded from the value model. The six-week completion target depends on provider response, eligibility, and underwriting.

The result and the effort behind it

All 12 entities have verified coverage by the agreed dates, evidence satisfies the 40 customer contracts, and annual program premiums and fees are reconciled.

  1. 1. Search

    Find the right capabilities

    The CFO has comparable provider proposals, a program-wide cost breakdown, and a requirements matrix covering all 12 entities and 40 contracts.

  2. 2. Act

    Coordinate the handoffs

    The authorized broker has completed the approved placements, and the team has entity-level coverage documents and a reconciled program cost record to review.

  3. 3. Outcome

    Return the complete result

    All 12 entities have verified coverage by the agreed dates, evidence satisfies the 40 customer contracts, and annual program premiums and fees are reconciled.

Pilot estimate

Less searching. Fewer manual handoffs.

Estimated buyer effort for the same scope and acceptance criteria. Track actual hours during the pilot to compare with these estimates.

Time to a reviewed selection

120 working hours without Darwin; 30 with Darwin in the pilot estimate.

90h lessestimated research effort
Without DarwinWith Darwin
Cumulative working hours

Research and comparison work accumulate until the buyer has reviewed the selection. Delivery time is separate.

Human effort across the same scope

480 staff-hours without Darwin; 120 with Darwin in the pilot estimate.

360h lessestimated coordination effort
Without DarwinWith Darwin
Staff-hours by work role

Work roles may belong to the same person or run in parallel. Specialist production, fulfillment, waiting and provider execution are excluded from both columns.

Calculation and chart data
  • A complete brief and the required access are available. The same buyer acceptance checks apply in both approaches.
  • Darwin organizes discovery and handoffs; people still approve scope and review results. Estimated savings come from research and coordination.
  • Discovery is included in total effort. Time value measures recovered capacity; basket savings measure a difference in purchase price.
  • Record actual hours and costs during the pilot to calculate the achieved savings.
Discovery: estimated cumulative working hours
MilestoneWithout DarwinWith Darwin
Brief24h8h
Research72h16h
Compare108h22h
Select120h30h
Team effort: estimated staff-hours
RoleWithout DarwinWith Darwin
Finance180h36h
Operations180h24h
Legal & security96h36h
CFO approval24h24h