Skip to content
A

Agentcover

Warranty protection for AI coding agents.

Created on 15th March 2026

A

Agentcover

Warranty protection for AI coding agents.

The problem Agentcover solves

AI coding agents (Claude Code, Codex) can now autonomously write code, modify files, and interact with databases. When they go wrong, the damage is severe — a agent once wiped an entire production database and generated fake records to hide it. The worse part? No existing coverage protects you. Employee liability only cover humans, cyber insurance only covers external hackers and external software.
AgentCover fills that gap. A lightweight CLI silently logs your AI agent sessions, strips sensitive data, and anchors a cryptographic fingerprint to the Base blockchain for fractions of a cent. If an agent causes a production incident, you file a claim — an AI engine cross-checks your session log against the immutable on-chain record and either auto-approves a payout or escalates to human review.
The result: unpredictable AI behavior becomes a quantifiable, warrantied risk rather than an open-ended liability — giving solo developers, startups, and engineering teams a financial safety net that simply didn't exist before.

Challenges we ran into

  1. Log Normalization Across Different Tools
    Claude Code and Codex, both produce slightly different log formats. Building one pipeline to extract the right data from all two was messy..
  2. Hashing Without Exposing Source Code
    Developers won't accept any tool that sends their raw code to an external server. So the entire redaction, cleanup, and fingerprinting process had to happen locally on the developer's machine before anything was transmitted. Getting that order of operations airtight — so the hash was always consistent and the sensitive data never left the machine unprotected — took a lot of careful engineering.
  3. Making On-Chain Anchoring Cheap Enough to Actually Work
    The whole business model only works if anchoring a session to the blockchain costs almost nothing. Early versions of our attestation schema were too bloated, making each transaction more expensive than it needed to be. We stripped the on-chain payload down to just three fields — session ID, agent identity, and the hash — which brought costs down to under $0.05 per session on Base, making the micro-warranty pricing viable.

Tracks Applied (5)

Best creative use of ENS

We make use of ENS for creating ens names and also we use ENSIP-25 to associate a registered agent with an ens name.
Ethereum Name Service

Ethereum Name Service

Pool prize

We make use of ENS for creating ens names and also we use ENSIP-25 to associate a registered agent with an ens name.
Ethereum Name Service

Ethereum Name Service

Build What Big Tech Won't

Store agent logs securely via d.docs.
Fileverse

Fileverse

AI × Onchain

AgentCover is an AI-native insurance and verification layer built on Base, where autonomous agents are registered and th...Read More
Base

Base

BEST Overall Project

Cheer Project

Cheering for a project means supporting a project you like with as little as 0.0025 ETH. Right now, you can Cheer using ETH on Arbitrum, Optimism and Base.

Discussion

Builders also viewed

See more projects on Devfolio