Surfil
// By problem

Cut token spend, and sign the number you cut

Surfil trims the context agents never needed, measures the cache premium you are paying, and names the writes that are never read back - then signs the measured saving.

surfil verify rcpt_8f2a
Signed savings receiptVALID
receiptrcpt_8f2a
typeprefix-cache + prune
saved48,200 tokens
measuredbefore / after
signatureed25519:… (epoch 7)
verifiedoffline · no account
Run surfil verify on any receipt - the signature is the proof.
How it works

The chain that removes it

Agents re-send the same context, re-read files they have already seen, and the bill creeps up with nobody able to point to exactly why.

1

Core consolidates

Scattered MCP servers collapse into one endpoint, so less repeated context ships on every operation.

2

Cap trims and routes

Redundant context is pruned before it is sent and heavy tasks route to the cheapest capable model.

3

Bench proves it

The measured before/after saving is signed into a receipt you can verify offline, with no account.

First signed receipt: A signed recoverable-tokens receipt per repo, measured before and after.
What holds

How the number stays honest

Measured, never invented

We publish no savings percentage. Cost is always measured on your own traffic and reported in tokens.

Byte-exact underneath

Cache tuning preserves the provider prefix hash exactly, so the savings never cost you your prefix cache.

Unmetered execution

The Core consolidation and the Cap ledger run on every plan; the signed savings receipt is the metered output.

By problem

More in this view

Same spine, a neighbouring starting point.

Not the right lens? The same eleven paths are also organized by team size, by problem, and by persona on the solutions overview - pick whichever matches how you think.

Turn on the first stage today

The install is reversible byte-for-byte, and the first signed receipt arrives after one normal week of traffic.