Solutions · By use case

API monetization

Satelink lets you charge for an API per call over a machine-native rail: expose a priced endpoint, answer with HTTP 402, and get paid in USDC or from a prepaid balance — no billing stack to build.

Talk to Satelink Start building

The problem

What's hard today

Charging machines for API calls usually means building metering, billing, and dunning yourself.

How Satelink works

The flow

01
Expose your endpoint behind the 402 handshake.
02
Callers pay the quoted price per request.
03
Revenue meters and settles on-chain.

Two sides

Machine buyers and sellers

Machine buyers

Callers pay per request with x402 or a balance.

Machine sellers

You price an endpoint and get paid without billing infrastructure.

Capabilities

What you get

HTTP 402 pricing

Per-call metering

USDC settlement

On-chain receipts

Choose how you build

Implementation paths

Direct REST

Call the API over HTTPS with an API key or keyless x402 — no dependency required.

x402-kit (MIT)

Drop-in middleware and client that implement the HTTP 402 handshake.

SDK

Planned

A typed client library.

MCP / agent server

Planned

An MCP server so agents can discover and pay for Satelink tools.

Use cases

Where teams apply it

Monetizing a data API
Charging agents per call
Usage-based pricing without billing infra

Frequently asked

About the offering

Do I need to build billing?

No — metering and the 402 handshake are provided. You price the endpoint; the rail collects and settles.

Products behind this solution

API Metering

Credits and per-call usage metering you can audit.

x402 Machine Payments

HTTP-native, keyless payments in USDC on Base.

Machine Commerce

The full discover → pay → call → settle loop for autonomous buyers.

See Satelink for api monetization

Talk to Satelink See pricing