Pay per use: the end of API subscriptions

RelAI Team
Feb 10, 2026 · 2 min read

Imagine you need a weather forecast for your app. Today, you'd sign up for a weather API, enter your credit card, pick a pricing plan, and hope you don't exceed the limit. With RelAI, you just… use it. And pay a fraction of a cent per request. No account needed.

How it works - the simple version

  1. You visit a service - could be a weather API, an AI tool, a data feed, anything
  2. The service tells your wallet the price - for example, $0.001
  3. You approve - one click in your wallet, like signing a message
  4. You get access - instantly, the data or service is delivered
  5. The payment settles - USDC moves from your wallet to the service provider
That's it. No usernames, no passwords, no subscriptions.

Why this matters

For users:
  • No monthly subscriptions for services you barely use
  • No sharing your credit card or personal data
  • Pay only for what you actually consume
  • Works with your existing crypto wallet
For service providers:
  • No payment infrastructure to build
  • No chargebacks or fraud
  • Get paid instantly in USDC
  • Set your own price per request - even fractions of a cent

What does it cost?

You decide. As a service provider, you set the price - it can be as low as $0.001 per request (one tenth of a cent). Users pay exactly that amount, nothing more.

RelAI covers all the blockchain transaction fees, so neither the user nor the provider pays any gas.

Which wallets work?

Any wallet that supports USDC on these networks:

  • Base - popular Ethereum layer 2
  • Avalanche - fast and reliable
  • SKALE - zero gas fees
  • Solana - fast transactions
MetaMask, Coinbase Wallet, Phantom, and many others all work out of the box.

Getting started

If you're a service provider, head to the RelAI Dashboard to create your first paid API. You'll have a payment-protected endpoint in minutes.

If you're a user, just connect your wallet and start using services. No sign-up required.


The internet was always meant to have a built-in payment layer. We're finally building it.