Programmable infrastructure
for agent-native systems.
Karvhood is a settlement and coordination layer for autonomous agents. Open standards, verifiable workflows, and a deflationary fee market — built for the post-API economy.
Three layers. One protocol.
Onion-routed mesh for private, verifiable agent transactions across L1, L2, and rollups.
Karvhood Pay, MultiClaw, and the Validator — first-party tooling for humans and agents.
TypeScript, Python, and CLI clients with batteries-included primitives.
Your agents don't need an audience.
Standard machine payments leave a trail — merchants see who paid, and the chain records the transfer. Karvhood breaks that link through onion-routed requests and pooled settlement.
- → Entry knows who
- → Exit knows what
- → Neither knows both
- → Pool settles to merchant
Five primitives. Composed end-to-end.
Privacy routing is opt-in per request. Merchants receive a standard settlement — no integration required to support privacy clients.
Three-hop onion routing through KARV-staked relays. Entry knows who, exit knows what, neither knows both. Sentinels monitor for misbehavior.
Independent operators correlate session tokens, validate the pooled balance, and construct signed payment authorizations.
Staked operators emit cover traffic through the mesh, inflating the anonymity set even at low real volume.
The facilitator submits Pool → Merchant. The chain shows Pool → Merchant, never Agent → Merchant. Auditability is preserved against the pool.
Composers post bonded attestations. A configurable window lets any party challenge with a counter-attestation before final settlement.
Settlement for the agentic economy.
No signup. No API keys. Point your server at the facilitator endpoint below for verification and settlement of Karvhood-compatible payments on Base and supported rollups. All schemes supported: exact, upto, and batch.
v1 and v2 capable. ERC-20 support. Fully compatible with smart wallets.
$KARV — operational, not ornamental.
$KARV secures relays and pays for cover traffic. Network fees route through a deflationary hook contract — as usage grows, supply contracts. There is no governance theater attached.
→ read the protocol briefSmall, opinionated, paired.
Self-custodial browser wallet for human-initiated and agent-delegated payments.
Desktop control plane for fleets of agents. Batch authorization and audit export.
Inspect and replay Karvhood payloads against deterministic mock relays. CI-ready.
We build the ground agents stand on.
The next decade of compute belongs to software that acts on its own behalf — researching, transacting, coordinating with peers. The infrastructure to support this does not exist by default. It has to be built.
Karvhood is that infrastructure. A neutral, open mesh that lets any agent transact with any service without leaking identity, without depending on a custodian, and without giving up auditability.
We do not build the agents. We build the ground they stand on.
- 26.06.2026Mesh Router v2.1 →
Improved relay discovery and resilience under adversarial load. Adds adaptive backoff for sentinel nodes.
- 18.06.2026SDK v1.2.0 →
First-class TypeScript and Python clients with smart-wallet support and unified error envelope.
- 11.06.2026Karvhood Pay v0.5 →
Browser extension wallet adds session signing, hardware key pairing, and per-agent spend caps.
- 02.06.2026Partnership: Lattice OS →
Integration of Karvhood settlement into Lattice's agent runtime for verifiable M2M transactions.
- 21.05.2026Validator Tool v1.0 →
Inspect and replay Karvhood payloads with deterministic mock relays. Suitable for CI pipelines.
- 09.05.2026Protocol RFC-014 →
Batch-settlement scheme finalized. Channel close semantics aligned with on-chain dispute window.
- 27.04.2026Karvhood CLI v0.9 →
Headless ops mode, structured logs, and a built-in REPL for protocol exploration.
- 13.04.2026Adaptive Burns Live →
Network fees route through a deflationary hook contract. Supply becomes a function of throughput.
Used in production by teams building agent-first software.
Questions we keep getting.
Is Karvhood permissioned?+
No. Anyone can run a relay, operate a composer, or call the facilitator. Staking $KARV is required to earn from the mesh, not to participate.
What chains are supported today?+
Base and SKALE are first-class. Arbitrum, Optimism, zkSync, and Linea adapters are stable. New chains land via the adapter package.
Do I need to integrate the privacy layer?+
No. Privacy routing is agent-side. Merchants receive a normal settlement and need no special handling.
Is there a custodial fallback?+
No. Karvhood is non-custodial end-to-end. The pool is a smart contract, not a company balance sheet.
How do I run a relay?+
Stake $KARV, run the open-source relay binary, and register with the sentinel set. Full operator docs live in the docs section.
What's the fee model?+
A small per-request fee in $KARV, routed through the burn hook. There are no monthly minimums and no rate cards.
Ship the agent. We'll handle the rails.
Install the SDK, point at the facilitator, and ship. Karvhood stays out of your way until you need it.