Pact Network

Abstract

AI agents are paying for API calls autonomously via x402. When those APIs fail, there is no refund mechanism. The payment settles instantly and irreversibly. Pact Network introduces a parametric insurance layer on top of x402 that gives agents automatic refunds when APIs violate measurable SLA thresholds. Underwriters provide capital to coverage pools and earn yield from premiums. The insurance premium for each API becomes a market-derived reliability score, creating a quality signal with no governance token, no committee, and no reputation system. Just capital at risk.

1. The Problem

x402 is the HTTP-native payment protocol backed by Coinbase, Cloudflare, Google, Visa, AWS, Circle, Anthropic, and Vercel. It allows AI agents to pay for API calls with a single HTTP header. As of April 2026, there are 75M+ cumulative x402 transactions and 15M daily on-chain agent payments on Solana alone.

The problem: x402 has zero buyer protection. When an agent sends payment and the API returns an error, times out, or serves corrupted data, the money is gone. There is no chargeback, no dispute process, no refund mechanism. In human commerce, Visa and Mastercard protect buyers. In the agent economy, nobody does.

This isn't theoretical. On April 1, 2026, Drift Protocol was exploited for $285M. Every agent that paid for a Drift API call during the attack received compromised data and had zero recourse. In October 2025, a major AWS outage took down thousands of API endpoints globally. Every agent making x402 payments to AWS-hosted APIs during that window paid for calls that timed out or returned 500 errors. Zero refunds.

The agent economy needs buyer protection infrastructure. Not a customer support team. Not a dispute resolution process. Infrastructure that detects failures programmatically and pays refunds automatically.

2. Pact Network

Pact is a parametric insurance protocol built on Solana. It wraps x402 API calls with SLA monitoring and automatic refund logic. The protocol operates a three-sided market:

3. Protocol Mechanics

3.1 Premium Pricing

Premiums are calculated as a percentage of the API call cost, dynamically adjusted based on the API's observed failure rate.

Formula: Premium = CallCost × BaseRate × ReliabilityMultiplier × CoverageTier

Rates recalculate every 10,000 calls or 24 hours. A smoothing function (0.7 × previous rate + 0.3 × new rate) prevents wild swings from temporary outages.

3.2 Parametric Triggers

Claims fire automatically based on measurable conditions. No human review.

Refunds settle in the same Solana slot as the failed call. If congestion prevents same-slot settlement, claims batch and settle within 60 seconds.

3.3 Coverage Tiers

3.4 Pool Economics

Coverage pools are per-API. Underwriters choose which APIs to back. Pool size is capped at 20× monthly premium volume to maintain healthy utilization and competitive yields.

Revenue split on premiums: 45-55% goes to claims (target loss ratio), 10% protocol fee, 2% reserve fund, remainder to underwriter yield. At 5% monthly utilization, underwriters earn approximately 21% APY.

Per-event aggregate cap: maximum payout per correlated event is 30% of pool capital. This protects against catastrophic correlated failures like cloud provider outages.

4. The Insurance Rate as Quality Score

The insurance premium is the most honest reliability signal in the ecosystem. If it costs 0.12% to insure calls to Helius and 7.8% to insure calls to an unknown API, that price spread tells you everything. No reputation token. No committee vote. Just underwriters putting capital where they believe APIs will perform.

This creates a flywheel: agents prefer lower-premium APIs because they're cheaper to insure. This drives traffic to reliable providers. Reliable providers attract more underwriter capital, further lowering their rates. Unreliable providers see rates rise, lose agent traffic, and either improve or get priced out. The market self-corrects through insurance pricing.

5. Anti-Abuse Mechanisms

Parametric insurance is vulnerable to moral hazard and claim farming. Pact implements layered defenses:

• •Circuit breaker: When an API's error rate exceeds 50% in a 5-minute window, new insured calls are halted. Prevents pile-on during known outages.
• •Volume caps: Per-agent insured call volume capped at 2× trailing 7-day average per API.
• •Claim frequency limits: Maximum 10 claims per agent per API per hour. 50 per day.
• •Payment verification: Claims require proof of x402 payment settlement. No payment proof, no refund.
• •Multi-observer validation: Independent verifier nodes cross-check agent-reported failures against their own measurements.

6. Risk Management

The top risks, scored by severity × likelihood:

7. Target Verticals

Not all API verticals are equally insurable. We're prioritizing by pain intensity, measurability, volume, and willingness to pay:

Launch sequence: RPC first (highest measurability, binary SLA), then price feeds (highest pain intensity), then DEX aggregators, then MCP tools.

8. Architecture

Pact runs on Solana with the following on-chain components:

• •Coverage Pool Program (Anchor): Manages underwriter deposits, premium collection, and refund payouts via PDAs.
• •Policy Registry: On-chain record of active coverage policies with SLA parameters.
• •Pact SDK: Client-side library that wraps x402 calls with SLA monitoring, premium deduction, and automatic claim submission.
• •Verifier Network: Independent nodes that cross-check agent-reported measurements for anti-abuse.

Settlement tokens use Token-2022 with transfer hooks for compliance enforcement and interest-bearing extensions for time-value signaling.

9. Roadmap

10. Key Parameters