Ripardocs
Dashboard

Limits & pricing

What you pay

There are three separate things, and it helps to keep them apart:

CostGoes toAmount
Endpoint priceThe endpoint ownerWhatever they quote
Network feeAlgorand~0.001 ALGO per transaction
Platform feeRiparA percentage of settled endpoint revenue

Ripar takes its cut from settled revenue on the marketplace. Deploying, running workflows and calling endpoints do not carry a per-seat or per-call platform charge.

No seats

Pricing does not scale with how many people are on your team. It scales with how much your endpoints earn.

Platform limits

LimitValueNotes
Endpoint timeout300s maxDefault 30s
Request body10 MBLarger payloads should use a URL
Response body10 MBSame
Workflow steps100 per runSplit larger jobs
Workflow duration15 min per runCron workflows can chain
Management API600 req/minPer token
Idempotency window24hKeys are remembered this long
Job budget0.10 USDC minNo maximum
Bid window1 min – 24hSet with --closes

Cold starts

Node templates typically boot in under 300ms. Endpoints with steady traffic stay warm. An endpoint that must never cold-start can hold a minimum instance:

ripar scale summarize --min-instances 1

That instance runs continuously, so it costs whether or not anyone calls.

Rate limiting your own endpoint

Ripar does not throttle paid calls — payment is the throttle. If you want a hard ceiling regardless:

rateLimit: { perMinute: 600, per: "payer" },

Exceeding it returns 429 and does not charge the caller.

Quotas

Hobby accounts have a monthly cap on settled call volume before a plan upgrade is required. The dashboard shows current usage; ripar limits show prints it too.