Utviklerportal
Tema
Introduction
Overview
Agent Payments Protocol
Core Concept
Supported Networks
Quickstart
Introduction
I want to sell DApp/MCP services
I want to sell Agent services
My Agent buys services
Payment Methods
Introduction
One-time Payment
Batch Payment
Pay-as-you-go Payment (Coming soon)
Escrow Payment (Coming soon)
SDK reference
Introduction
Rust
Node.js
Go
Java
API reference
Introduction
HTTP API
Agent API
Payment Methods

Payment Methods#

Onchain OS Payment offers four payment methods, each tailored to a different business shape. This page gives you a decision matrix to choose; click into a specific method for the full integration guide.

If you're not yet familiar with these payment methods conceptually, start with Core Concepts. This section is just about "how to integrate".

Step 1: Identify your Seller form#

Different Seller forms support different payment methods — filter by this table first.

Seller formOne-timeBatchPay-as-you-goEscrow
HTTP Seller✅✅Coming soon❌
Agent Seller✅Coming soonComing soonComing soon

Haven't decided your Seller form yet? Go back to Seller Entry to compare the two forms.

Step 2: Among available methods, pick by business characteristics#

Choose by your business's per-call price and consumption predictability.

Your businessRecommended payment methodSDK (HTTP Seller)Skill (Agent Seller)
Per-call amount is fixed (a report / one inference / one query)One-time payment✅✅
Very small per-call amount (under 1 cent) + very high frequency (tens to hundreds per minute)Batch payment✅Coming soon
Per-call consumption unpredictable (LLM per token / streaming data per byte)Pay-as-you-goComing soonComing soon
Two parties don't trust each other, need escrow release (Agent outsourcing tasks)Escrow payment—Coming soon

✅ Available ｜ Coming soon ｜ — Not applicable. HTTP Sellers use the SDK; Agent Sellers use the Skill.

Fixed price but small amount — One-time or Batch?

Look at call frequency and Buyer form:

  • High frequency (tens of calls per minute or more) + Buyer is an Agent → use Batch payment to avoid waiting for on-chain confirmation per call.
  • Low frequency → One-time payment is enough. With X Layer's USD₮0/USDG gas subsidy, zero gas keeps small payments economically viable.

Two confusable pairs#

One-time vs. Batch#

Both can handle small, high-frequency calls, but the underlying paths differ:

DimensionOne-timeBatch
On-chain timingEach call awaits on-chain confirmation (or async)Deliver first, aggregate on-chain in the background
Throughput bottleneckLimited by block timeNot limited by block time
Wallet requirementAny EIP-3009 walletMust be Agentic Wallet (depends on Session Key)

Batch vs. Pay-as-you-go#

Both "accumulate, then settle on-chain", but the signature forms and fund paths are completely different:

DimensionBatchPay-as-you-go
Signature formSign each call (amount + recipient)Open a channel once, then only sign the cumulative amount (Voucher)
Use casePer-call amount is the samePer-call amount is different (metered)
Fund pathBuyer → Seller (single transfer at aggregation)Buyer → Escrow → Seller (paid per Voucher on close, residual refunded to Buyer)

Drill into a specific payment method#

One-time paymentFixed price, instant settlement, instant delivery. Supported by both HTTP and Agent Sellers.Batch paymentTiny per-call amounts and very high frequency. Session Key + TEE compression on-chain.Pay-as-you-goMetered billing — pay for what you use. On-chain custody + off-chain cumulative Vouchers.Escrow paymentTwo parties don't trust each other. On-chain escrow + arbitration. Coming soon.

Next#

QuickstartGet a minimal demo running, then come back for integration detailsCore ConceptsTerminology, protocols, underlying mechanisms — shared foundation for all payment methodsAPI ReferenceDetailed fields, error codes, and signing specs for every endpoint
Innhold