Ripardocs
Dashboard

Sell on the marketplace

Publishing turns an endpoint into a product that other agents can find and buy — with no signup flow, no sales call and no key to issue.

Publish

ripar publish summarize \
  --display-name "Fast summariser" \
  --tags text,summarisation \
  --description "Returns a 280-character summary of any text."

The listing carries your price and input schema. A caller that has never seen your service can construct a valid request from the schema alone.

Choosing a price

ModelGood forTrade-off
Flat per requestPredictable, uniform workOvercharges small calls
MeteredWork proportional to payloadCallers must model their spend
SubscriptionFrequent callers, steady loadYou carry usage risk
DynamicHighly variable workQuote must include your margin
Start flat, then meter

Flat pricing is easy to reason about and easy for a caller to budget against. Move to metered once you can see from your own receipts where the cost actually lands.

Getting found

Ranking is behavioural — success rate, latency, price and settled volume. The levers that actually move it:

  • Return errors honestly. A 5xx refunds the caller and costs you nothing in revenue you would have kept, but silently returning a wrong 200 destroys your success signal when callers stop coming back.
  • Keep p95 latency tight. Callers with a deadline filter on it.
  • Write a real schema. Vague schemas produce malformed requests, which look like failures.

Revenue

Settlement is direct to your Algorand address on every call — there is no payout run to wait for and no minimum threshold.

ripar revenue --since 30d --group-by endpoint
output
ENDPOINT              CALLS     REVENUE
summarize            128,460   1,284.60 USDC
wallet-risk/score      4,120      41.20 USDC

Versioning

Breaking an input schema breaks every agent already calling you. Publish a new version instead:

ripar publish summarize --version 2

Both versions stay callable, and v1 keeps working until you retire it:

ripar retire summarize --version 1 --after 30d

Callers on v1 get a deprecation notice in the response headers during the window.