Ripardocs
Dashboard

Introduction

Ripar is the execution and payment layer for autonomous agents on Algorand.

An agent that can call an API is useful. An agent that can pay for an API without a human opening an account, entering a card and copying a key is something else — it can go find capability it does not have and buy it, mid-task, on its own. That is the gap Ripar fills.

New to any of this?

If you have never seen HTTP 402 before, read The x402 protocol first. It is short, and everything else here assumes it.

What Ripar gives you

The shape of a paid call

Every interaction on Ripar is the same four-step handshake. A caller asks, gets told the price, pays, and gets the work:

GET /agents/summarize HTTP/1.1
Host: api.ripar.io
 
HTTP/1.1 402 Payment Required
X-Payment-Required: {"amount":"0.01","asset":"USDC","network":"algorand","payTo":"RIPAR…K7QX"}

The client attaches a payment and retries:

GET /agents/summarize HTTP/1.1
Host: api.ripar.io
X-PAYMENT: <signed payment payload>
 
HTTP/1.1 200 OK
X-Payment-Response: {"txId":"7A2F…","settled":true}

No API key was issued. No account was created. No invoice will be sent. The caller and the endpoint had never met.

Why Algorand

Pay-per-request only works if settling the payment costs meaningfully less than the work being bought. Charging a tenth of a cent for an inference call is absurd if the transfer costs three cents and takes a minute to confirm.

PropertyValueWhy it matters here
Block finality~2.9sThe caller waits once, not twice
Typical fee0.001 ALGOA sub-cent call is not eaten by gas
ForksNone — finality is instantA settled call is settled; no reorg risk
USDCNative ASANo bridge, no wrapped-asset risk

Where to go next