x402 Payments

Assembly separates access control from economic settlement.

While $ASMBLY regulates access tiers and protocol usage rights, all payments for Assembly services are handled through x402-compatible payments.

Why x402

Assembly is designed for autonomous systems. Autonomous systems require programmatic, machine-native payments.

x402 provides a payment standard that allows agents and services to:

• pay per request or per execution

• settle fees automatically without human intervention

• embed payment logic directly into execution flows

This makes x402 a natural fit for a coordination layer designed to serve agents and machines.

What is paid via x402

x402 is used to settle usage-based fees for Assembly services, including:

• coordination cycles

• planning and replanning workloads

• multi-agent execution capacity

• extended execution windows

• resource-intensive research environments

Payments are tied to actual protocol usage, not flat subscriptions or time-based plans.

Programmatic settlement

Assembly services expose x402-compatible payment endpoints.

• Agents initiate requests

• Payment conditions are evaluated programmatically

• Services are executed only once payment is settled

This enables machine-to-machine economic interaction, where agents can autonomously decide when coordination services are worth the cost.

Separation of concerns

Assembly deliberately separates responsibilities:

• $ASMBLY → access, tiers, commitment

• x402 → payments, settlement, execution economics

This prevents the access token from becoming a payment bottleneck and keeps economic flows explicit, auditable, and machine-readable.