Surfil

Quickstart

From nothing to a verified, signed receipt in four steps: install the runtime, link your device, run a normal session, then verify the result offline. No agent workflow changes - you keep invoking Claude Code, Cursor, Codex, or Copilot exactly as before.

1. Install and consolidate

curl -fsSL https://surfil.com/install.sh | sh detects the agents on your machine, wires an adapter beside each one, and backs up every original config byte-for-byte before touching it. surfil consolidate then merges scattered MCP endpoints into the single interception point and bootstraps Weave.

$ curl -fsSL https://surfil.com/install.sh | sh
✓ Claude Code    adapter wired
✓ Cursor         adapter wired
✓ originals backed up byte-for-byte (uninstall restores exactly)
$ surfil consolidate
✓ 6 MCP servers → 1 endpoint · Weave bootstrapped

Per-agent detail - what changes on disk and how restore works - is on the Install page.

surfil login starts a device flow (RFC 8628): the CLI shows a short code, you confirm it in the browser, and the device receives an Ed25519 device token. No API key ever lives in a dotfile.

$ surfil login

3. Run a session, get your first receipt

  1. Use your agent normally - Surfil measures real traffic, so a real session is the input.
  2. Run surfil audit. It measures token usage before/after on your own traffic and produces a signed savings receipt.
$ surfil audit
✓ measured before/after on your traffic
✓ receipt signed (Ed25519)

4. Verify it

Every paid operation ends in a server-signed output. Check the signature yourself - it works offline, without an account:

$ surfil verify <receipt-id>
✓ VALID (offline · public key · no account)

How you know it worked

  • Your agent behaves exactly as before - same commands, same output. Interception is byte-exact, so provider prefix caching keeps working.
  • surfil mind stats shows facts being written for your sessions.
  • surfil verify reports VALID on your first receipt.
If anything looks wrong, surfil uninstall restores every agent config byte-for-byte and leaves zero residue - that is verified behavior, not a promise.

Next

  • Weave - what gets recorded and how staleness is caught.
  • Credits - what is metered (the signed output; execution is unmetered).
  • Cut costs with Cap - the first guide most people want.