Skip to content
For individuals

Your own verified network — solve it once, reuse it everywhere.

Every solution you verify becomes a personal capsule you can reuse across every repo you work in. Your agent stops re-deriving the same patterns, and you stop paying tokens for work you have already done. Local-first and private by default — source code never leaves your machine for a search.

Private by default

Searches run locally. Nothing is uploaded and nothing is published unless you explicitly choose to.

Reuse across repos

A capsule you verify in one project is available in the next — your personal cache travels with you.

See every saving

Each reuse comes with a receipt: tokens saved, the reduction, and the estimated value for your billing.

What a reuse looks like

An exact personal-capsule hit on a 60k-token task, priced on direct-API billing:

PatchMesh savings receiptEstimated cashMeasured usage

PatchMesh saved an estimated 46,700 tokens and $0.147 on this request.

46,700
Tokens avoided
71.85%
Reduction
$0.147
Estimated direct cost avoided
PatchMesh · work avoided

46,700 tokens avoided

Never sent or generated — a reused solution removed the work.

Provider cache · input discounted

10,000 input tokens discounted · 7,000 at full rate

Still sent, billed at the cheaper cached rate (~$0.027 off) · 59% cache-hit.

SourcePersonal capsule
Match typeexact
Modelclaude-sonnet-4-6
Billing modeDirect API (pay-per-token)
Baseline tokens (counterfactual)65,000
Actual tokens18,300
Monetary classificationEstimated direct cost avoided
Estimated value$0.147 USD
Methodrepository_context_estimate v1.0
ConfidenceMeasured (provider-reported usage)
Actual usage sourceprovider reported
Pricing snapshotsonnet-2026-01
Baseline assumptions
  • Repository context ~60,000 tokens (40% cacheable)
  • Expected from-scratch output ~5,000 tokens
  • Counterfactual, not a second paid request

Personal capsule result (exact). Estimated usage fell from 65,000 to 18,300 tokens — a 71.85% reduction.

Every capsule is more than a snippet

Personal capsules carry the same structure as the rest of the network, so reuse is a decision, not a copy-paste gamble.

anatomy of a capsulecontent-addressed · signed provenance · trust-rated

Identity

  • Canonical task
    The normalised problem the capsule solves.
  • Language & runtime
    Where it applies — versions and ecosystem.
  • Dependencies
    What it needs to compile and run.

Code

  • Reusable artifacts
    The implementation, ready to adapt.
  • Tests
    Executable proof of behaviour.
  • Content hashes
    Content-addressed so reuse is verifiable.

Evidence

  • Validation results
    Did the tests actually pass?
  • Security scan
    Known-issue check before reuse.
  • Reuse outcomes
    How it performed for others — ranking signal.

Trust

  • Licence (SPDX)
    Clear, preserved licensing.
  • Provenance
    Where it came from, pinned to a commit.
  • Trust level
    Verified, approved, or unverified candidate.

A snippet search returns text. A capsule returns a decision: reuse this, adapt that, or generate because nothing here fits.

Start your personal network.

Free to begin. Local-first. Private by default.