Launched on BNKR • Built on Base

x8004

The intelligence layer for agent payments.

x402 handles payment execution. x8004 adds the decision layer: negotiation, reputation, budgets, escrow. Agents stop paying blindly.

Read the docs Whitepaper

agent.ts

1import { x8004 } from '@x8004/sdk';
2
3const agent = x8004.createAgent({
4  wallet: '0x...',
5  policies: {
6    dailyBudget: 100,
7    maxPerCall: 10,
8    minReputation: 80
9  }
10});
11
12// Negotiate → verify reputation → enforce budget → escrow → pay
13const data = await agent.request('api.example.com/data');

One line. Negotiates price, checks reputation, enforces your budget, escrows funds, settles via x402.

$X8004 Token

Fair launched on BNKR

X8004 is the governance and utility token powering the protocol. Fair launched via Bankr/Clanker on Base with locked liquidity.

Contract Address

0x5703838C2b10AC10d4F0160ea49E3B50c7b48B07

Chart Buy Clanker

Fair Launch

No presale, no VC

Locked LP

2100 years via Clanker

Base Native

Superchain compatible

Overview

What is x8004

x8004 sits between your agent and x402. When your agent needs to pay for something, x8004 checks policies, queries reputation, negotiates price, and locks escrow. Then it calls x402 to move money.

x402 is the payment rails. x8004 is the decision logic. Use them together or x402 alone. Your call.

Think of it as:x402 = execution | x8004 = intelligence

How it works

Transaction flow

Eight steps. Request to release.

Request

Agent initiates payment

Policy

Check spending rules

Reputation

Verify provider trust

Negotiate

Agree on price

Escrow

Lock funds

Execute

x402 payment

Deliver

Service provided

Release

Complete transaction

Features

What you get

Zero blind spending

Every transaction hits policy checks first. Agents can't exceed budgets or pay endpoints you haven't approved.

Zero trust required

Reputation scores are onchain. Check provider history before any money moves.

Zero budget blowouts

Daily caps. Per-transaction limits. Time restrictions. Set them once, enforce forever.

Zero lock-in

Open protocol. Fork it, run your own, swap providers. Your keys, your agents.

Comparison

Before and after

Agent runs up $500 overnight on bad API calls

Daily budget capped at $50, per-call max at $2

No idea if provider is legit until money is gone

Reputation score checked before payment

Pay upfront, hope service delivers

Escrow holds funds until delivery confirmed

Fixed prices, take it or leave it

Agents negotiate rates automatically

Manual review of every transaction

Policy engine handles it

Protocol

x402 vs x8004

x8004 extends x402. Use both.

Capability	x402	x8004
Payment Execution USDC transfers on Base
HTTP 402 Support Native web payment protocol
Price Negotiation Agents negotiate rates
Budget Policies Spending limits and rules
Reputation Scores Onchain trust data
Escrow Hold funds until delivery
Service Discovery Find x8004 endpoints
Dispute Resolution Handle failed deliveries

Architecture

Core components

Policy Engine

Spending rules. Budget limits.

Reputation Oracle

Onchain trust scores.

Negotiation Layer

Price discovery.

Escrow Primitive

Conditional release.

Questions

FAQ

x8004 is a protocol layer built on top of x402. While x402 handles the actual payment execution (HTTP 402 responses, USDC transfers on Base), x8004 adds the intelligence layer that makes AI agents smarter about how they spend. Think of x402 as the payment rails and x8004 as the conductor.

No. The x8004 SDK includes full x402 support. When you integrate x8004, you automatically get x402 payment capabilities. x8004 calls x402 under the hood when it's time to execute the actual transaction.

Minimal. For simple transactions where negotiation isn't needed, x8004 falls through to direct x402 execution in <50ms. When negotiation happens, typical roundtrips complete in 200-500ms depending on policy complexity. All reputation queries are cached.

The reputation oracle aggregates on-chain transaction history from x8004 escrows. It tracks completion rates, dispute frequency, and response times for both agents and service providers. Scores are computed using a time-weighted algorithm that emphasizes recent behavior.

Yes. The Policy Engine allows granular control per agent, including: daily/weekly/monthly spending limits, per-transaction caps, endpoint whitelists/blacklists, time-of-day restrictions, and required approval thresholds for high-value transactions.

x8004 escrow contracts hold funds until service delivery is confirmed. If delivery fails or is disputed, funds can be released back to the agent (or split) based on the dispute resolution outcome. The protocol supports both automated and manual dispute resolution.

While designed for autonomous AI agents, x8004 works for any programmatic payment scenario. Microservices, IoT devices, and automated systems can all benefit from the negotiation, reputation, and escrow primitives.

x8004 currently operates on Base (Coinbase's L2). USDC is the native settlement currency. Cross-chain support via bridge integrations is on the roadmap for 2025.

Start building

npm install @x8004/sdk

Documentation Whitepaper