Skip to main content
The OWS gateway demo is an application-layer example of Agon in production-shape usage: metered Solana RPC access settled through Agon channels.

​
What it demonstrates

The gateway turns a stream of signed RPC requests into off-chain Agon commitments and settles them on-chain periodically. It is a concrete example of:
  • Repeated, high-frequency machine payments between a client and a service.
  • Signed payment updates delivered alongside request traffic.
  • A single service collecting payment from many clients, with settlement compressed via bundle and clearing-round paths.
In Agon’s terms, the gateway is an operator hub — users pay one operator, and that operator coordinates paid access to downstream infrastructure (RPC, in this case) on top of Agon’s clearing substrate.

​
How it relates to the protocol

The gateway is intentionally not part of the core protocol. The protocol guarantees correctness of settlement and custody of funds; the gateway is a higher-layer product that uses those guarantees to offer a paid API. This separation is important:
  • The protocol documentation you are reading does not assume the gateway exists.
  • The gateway is one of many possible operators. Others can and should exist.
  • If you are integrating Agon at the protocol level, the protocol demo is the more direct reference.

​
When to read this

Read this example if you want to understand:
  • How a service might shape its HTTP surface around Agon commitments.
  • How an operator can coordinate many users and one downstream resource.
  • What a production-shape Agon integration looks like end-to-end.
If you are looking for protocol mechanics or benchmark numbers, start from Protocol overview and the protocol demo instead.

​
See also