Skip to main content
Retempo is an API-first recurring payment and settlement service built for developers who need a reliable, programmable way to collect USDC. API providers use it to monetize endpoints, SaaS developers use it to run subscription businesses, and AI agent builders use it to wire autonomous agent-to-service payment flows — all backed by onchain settlement proof recorded on Arc.

​
What you can build

Retempo is flexible enough to support a wide range of payment architectures. Here are some of the most common use cases:
  • API monetization — Charge consumers a recurring USDC fee for access to your API. Set a fixed monthly or weekly price, attach it to a service, and let Retempo handle invoicing and settlement automatically.
  • SaaS subscriptions — Offer subscribers a predictable billing experience with fixed recurring plans. Retempo manages the checkout flow, subscription lifecycle, and invoice generation.
  • Agent-to-service payments — Enable AI agents to autonomously pay for services they consume. Because Retempo is fully API-driven, agents can initiate checkout sessions and trigger settlements without human intervention.
  • One-time payments — Collect a single USDC charge for a product, access grant, or one-off service using the ONE_TIME pricing type and a NONE billing interval.

​
How Retempo works

Retempo uses a hybrid model that separates billing orchestration from settlement proof. Offchain orchestration handles the business logic: you create services and payment plans, subscribers complete checkout sessions, and Retempo issues and tracks invoices through their lifecycle. This layer is fast and flexible, giving you full programmatic control via the REST API at https://api.retempo.xyz. Onchain settlement proof is the trust anchor. When an invoice is ready to settle, Retempo submits a settlement transaction to Arc (Chain ID 5042002). The resulting transaction hash is stored against the settlement record, and an invoice is only marked PAID after Retempo receives a confirmed Arc receipt — there is no shortcut. This design gives you a verifiable, auditable record of every payment without requiring you to manage wallets or write smart contracts yourself.

​
Key concepts

Before you build, it helps to understand the core entities that make up the Retempo data model:
  • Service — the product or capability you are selling, such as an API or an AI agent tool.
  • Payment Plan — the pricing and billing cadence attached to a service, including amount, interval, and pricing type.
  • Checkout Session — a temporary, shareable session that takes a subscriber through the payment flow and creates a subscription on completion.
  • Subscription — the active billing relationship between a subscriber and your service, created automatically when checkout is completed.
  • Usage Event — a recorded metered action that contributes to a usage-based invoice, carrying an event key and a quantity.
  • Invoice — the billing record for a subscription cycle, tracking status from draft through to paid.
  • Settlement — the onchain proof of payment submitted to Arc, which finalizes an invoice and makes the payment verifiable.

Quickstart

Build your first integration end-to-end in five API calls.

Core Concepts

Dive deeper into services, plans, invoices, and settlements.