Surfil
// help center

Search the answers.

Most questions here end in a guide, not a ticket. Search the articles, browse by category, and if you do need a human - the honest escalation paths are at the bottom.

architecture.weave.md
--- fact: Auth uses device flow (RFC 8628) source: acme/api@a91f code_hash: a91f…3c2 ✓ fresh --- fact: Legacy webhook path /hooks/v0 code_hash: 2b7e…901 ⚠ STALE ---
Portable, signed, offline-verifiable.surfilpkg
Browse

Four places questions come from

Each category links to the surface that answers it in depth.

Articles

Popular articles, live-filtered

Type to narrow - the search runs instantly over titles, summaries and categories.

Popular articles

Getting started

Install & first run

Get Surfil running beside your agents in 3 minutes.

Guides

Consolidating MCP servers

Reduce token sprawl by merging servers into one endpoint.

Guides

Verifying a savings receipt

Use surfil verify to check any receipt offline.

CLI

CLI reference

login · status · consolidate · audit · rewind · ask · verify · export.

API

Weave format spec

Signed Markdown: frontmatter, provenance, code_hash, signature.

First week

The four questions everyone asks first

If you installed Surfil this week, one of these is probably yours.

Did the install change my agent configs?

Yes - and it snapshotted the originals first. surfil uninstall restores every byte exactly. You can diff the backups yourself.

Where did my MCP servers go?

Nowhere - consolidation routes them through one endpoint. Every server still answers; your agents just stop re-sending the same context to each one.

Why is my first receipt taking a week?

Because it's measured. Surfil baselines a normal week of traffic before claiming anything - an instant number would be an invented one.

What exactly counts as a Credit?

One server-signed value-output - a receipt, a benchmark, an attestation. Execution is always unmetered; only the signed proof is metered.

Still stuck

When an article isn't enough

Two honest paths - one for your problem, one for ours.

It's on your machine

Adapter wiring, device approval, a receipt that won't verify - email support with the command you ran and its output. One business day reply target; faster on Team and Enterprise plans.

Send it to a human

It might be on ours

Before assuming your setup broke, check the live health endpoint - it answers for the edge directly, with no status-dashboard varnish sitting in between the two.

Check live status
Remember the zero-trace rule cuts both ways: support can't see your source or prompts either. Include the relevant command output in your message - we genuinely have no other way to see it.