# Billateral

> Billateral is the receipt layer for the agent economy. Every AI-agent payment is turned into a structured, bilaterally-signed receipt — co-signed by the buyer's business entity and the vendor, encrypted to both parties, and anchored on Base via EAS (Ethereum Attestation Service). The chain stores only a Merkle root; the parties hold offline-verifiable inclusion proofs.

Billateral is a project of SKRRT LLC and is in active pre-launch development. There is no live paid service yet — the website serves the protocol spec and a waitlist for operators, vendors, and partners.

## What Billateral does, in product terms

Billateral is an **x402 facilitator gateway**. It sits on the x402 payment path on both ends and ships a pair of plugins:

- **`@billateral/x402`** — vendor-side facilitator plugin. Drops into x402 server middleware (Express, Hono, FastAPI). Attaches the vendor attestation (line items, tax ID, business purpose) to every paid request.
- **`@billateral/agent`** — agent-side client wrapper. Carries a verifiable delegation from the buyer's business entity and co-signs the vendor attestation. First-class adapters for OpenClaw, AgentKit, Crewly, Loomkit, AutoForge, Northwind AI SDK, MCP tool servers, and raw HTTP clients.

Together they produce a bilaterally-signed receipt for every agent payment. Billateral never custodies funds; the agent pays the vendor directly via x402. SaaS billing is debited from a prepaid USD balance the customer tops up by card or ACH. Not a money transmitter, not an MSB.

## Status

- Stage: pre-launch / development
- Live service: not yet (waitlist only)
- General partner: Alien
- Network: Base (Ethereum L2)
- Anchor: EAS (Ethereum Attestation Service)
- Payment rail: x402 over USDC
- Role on the x402 path: facilitator gateway (plugin for vendors and agents)

## Primary documents

- [Home page](https://billateral.io/): product narrative — problem, how it works, the receipt, security, swarm/delegation, FAQ.
- [llms-full.txt](https://billateral.io/llms-full.txt): full site content as a single markdown document.
- [Privacy policy](https://billateral.io/privacy): what we collect, how it is processed, GDPR/CCPA rights. Markdown alternate at https://billateral.io/privacy.md.
- [Terms of use](https://billateral.io/terms): pre-launch terms covering the waitlist. Markdown alternate at https://billateral.io/terms.md.

## Discovery

- [Sitemap](https://billateral.io/sitemap.xml)
- [Robots](https://billateral.io/robots.txt) — includes AI bot rules and Cloudflare Content-Signal directives.
- [Web app manifest](https://billateral.io/manifest.webmanifest)
- [Agent discovery manifest](https://billateral.io/.well-known/agents.json)

## Sections of the homepage

- Why now — convergence of x402 payments, agent-to-agent delegation, 1099-DA / Form 8300 enforcement, and CFO scrutiny.
- The problem — agent payments today produce only a tx hash with no vendor identity, tax category, business purpose, or counterparty signature.
- How it works — five stages: agent initiates payment over x402, vendor signs line items, buyer co-signs via delegated key, receipt is encrypted and Merkle-batched, root is anchored on Base via EAS.
- The receipt — structured object with buyer/vendor entities, agent DID, authority, category, line items, both signatures, on-chain proof. JSON-readable, PDF-renderable, audit-defensible.
- Security and privacy — HPKE (RFC 9180) for end-to-end encryption to an explicit reader list; Ed25519 / secp256k1 signatures; content-hiding Merkle commitments on-chain; trust scores enforced pre-commit; SNARK-compatible commitments for stage-2 zero-knowledge aggregation.
- Swarms and delegation — when agent A delegates to agent B which hires agent C, every hop is attested; receipts carry the full dependency path.
- FAQ — accountant workflow, vendor refusal of co-signing, who can read a receipt, money-handling boundary (Billateral is not a money transmitter; agents pay vendors directly via x402; SaaS fees are debited from a prepaid USD balance), offline verifiability if the hosted service goes down.
- CTA — operator/vendor waitlist and partner/investor list.

## Contact

Direct contact addresses are not published in this document to limit harvesting. The site exposes them through the live pages below; the postal address routes to the same Skrrt LLC entity for any channel that needs paper.

- Privacy and data-subject requests: https://billateral.io/privacy (Contact section)
- Security disclosures: https://billateral.io/privacy (Security section)
- Legal: https://billateral.io/terms (Contact section)
- Postal: c/o Northwest Registered Agent Service Inc, 30 N Gould St, Ste N, Sheridan, WY 82801, United States
- GitHub: https://github.com/skrrt-sh

## Optional

- [Manifest (PWA)](https://billateral.io/manifest.webmanifest)
- [Open Graph image](https://billateral.io/opengraph-image)