Introduction

Xenarch is a non-custodial payment layer that lets publishers charge AI agents for content and services using the x402 protocol. Agents pay USDC on Base L2 through a splitter smart contract. Publishers receive funds directly — Xenarch never holds anyone’s money.

What Xenarch does

For publishers: Gate content behind HTTP 402 responses. Bots pay USDC, humans pass through unaffected.
For agents: Discover pricing via pay.json or HTTP 402, pay on-chain, receive time-limited access tokens.
For platforms: Integrate via Python/TypeScript SDKs, MCP server, or CMS plugins.

How payments work

Agent requests content → Server returns HTTP 402 with gate details
Agent sends USDC to splitter contract → Contract splits to publisher + treasury
Agent submits tx hash to verify endpoint → Server returns access token
Agent re-requests content with Bearer token → Server returns content

Every payment is a single on-chain USDC transfer. No deposits, no balances, no custody. The splitter contract has an immutable fee cap of 0.99% (currently 0%).

Key properties

Property	Value
Settlement	USDC on Base L2
Max payment	$1.00 per transaction
Fee	0% (capped at 0.99% forever)
Custody	None — permanently non-custodial
Verification	On-chain, auditable on Basescan
Protocol	x402 (HTTP 402 Payment Required)

Next steps

Agent quickstart

Start paying for gated content in 5 minutes.

Publisher quickstart

Start charging AI agents for your content.

API reference

Full REST API documentation.

Examples

Working code for Python, LangChain, CrewAI, and MCP.

Getting Started

MCP Server

Smart Contract

Integrations

Examples

What Xenarch does

How payments work

Key properties

Next steps

Agent quickstart

Publisher quickstart

API reference

Examples

​What Xenarch does

​How payments work

​Key properties

​Next steps

Agent quickstart

Publisher quickstart

API reference

Examples

What Xenarch does

How payments work

Key properties

Next steps