Docs / Customer guide

Coffer customer guide

Use this page as the manual. Use the dashboard app to do the work: create a workspace, produce one Spend Decision Record, connect one external agent, then decide whether the repeated workflow deserves a paid pilot.

Open customer launcherOpen dashboard app

Direct paths: Create workspace / Read-only product view.

Recommended first runFollow this order in the dashboard, then use the sections below when you need detail.
  1. Create workspaceOwner creates the control-only workspace.
    Dashboard targetCreate workspace
  2. Create starter proofDashboard adds the starter agent, vendor, policy, and approval-required request.
    Dashboard targetOpen Control Room
  3. Approve or rejectApprover reviews the request before any paid action runs.
    Dashboard targetOpen Approvals
  4. Connect agentDeveloper sends one external agent request through Coffer before cost.
    Dashboard targetOpen Agent API
  5. Request paid pilotBuyer asks for paid usage only after approved external-agent proof.
    Dashboard targetOpen Paid Pilot
01

Choose the right entry path

The customer workspace starts with one owner. Everyone else should use an invite.

Create a workspace

Use this path when you are the customer-side owner. Create the control-only workspace, then invite named teammates.

Create workspace

Accept an invite

Use the exact invite link from the workspace owner. Set a password, or use your current password if you already have a Coffer account.

Use invite link

Return to work

After your account exists, sign in with email/password or a configured OAuth provider.

Sign in

Invite links expire after 7 days. Creating a new invite for the same email replaces the old pending link.

02

Get to first proof

This is the product path that matters before any buying conversation.

  1. Create starter setup

    Adds the Research Ops Agent, Exa Starter API vendor, a policy, and one approval-required $120 request.

  2. Decide the request

    An approver approves or rejects the request before any real paid action runs.

  3. Inspect the SDR

    Open the Spend Decision Record and verify policy decision, approval evidence, ledger state, audit trail, and API payload.

  4. Connect a real agent

    Create a scoped key and send one external agent request so Coffer sees the workflow before cost.

  5. Use proof to decide

    Request a paid pilot only after an approved external-agent proof exists and the workflow will repeat.

03

Use the dashboard as a control room

The app is for doing work. Long explanations live here in the guide.

Control RoomCurrent status, control loop, proof rail, and metrics.
Spend RequestsSubmit or inspect spend intents and Spend Decision Records.
ApprovalReview approval-required requests with budget, vendor, duplicate, and history context.
Agent APICreate a scoped developer handoff and run an external agent request before paid cost.
Paid PilotUse approved external-agent proof to request a paid pilot, buyer brief, or success plan.
Workflow ReadinessCheck repeated-workflow, approval, finance-evidence, and rollout signals.
Ledger & AuditReview control-state ledger rows, audit events, evidence artifacts, and export batches.
SettingsManage workspace mode, roles, API keys, passkeys, MFA, Slack, and webhooks.
04

Connect one real agent

The strongest proof is not a dashboard-only review record. It is an agent asking Coffer before a paid call.

Developer handoff

Create a starter-scoped API key, run the stored-key request template, check the decision response, and route approval-required or blocked outcomes back through the dashboard before retrying.

Open Agent API
06

Invite the first roles

Start with the smallest team that can prove the operating loop.

OwnerCreates the workspace, manages settings and roles, and decides whether proof is worth a paid pilot.
DeveloperConnects the agent/API workflow after the first dashboard proof exists.
ApproverApproves or rejects approval-required spend from the dashboard.
Finance viewerReviews ledger evidence, audit trail, evidence packet, and exports.
07

Keep the boundary clear

These constraints keep the first customer experience safe and honest.

  • Control-only mode is the default; starter proof does not move customer funds.
  • Creating a workspace, starter setup, or paid-pilot request does not charge a card.
  • Customer proof, revenue claims, public release, hosted production access, real-spend rails, and paid infrastructure need separate explicit approval.
  • Coffer controls the decision and evidence around spend; it is not the wallet, custodian, facilitator, settlement provider, or accounting system of record.