Solutions · By use case

Commerce

Commerce infrastructure for machines: the rails software uses to buy services from other software — discover, pay, call, and settle — without a checkout or a human.

Talk to Satelink Start building

The problem

What's hard today

Humans buy products at a checkout. Software increasingly buys services — an RPC call, a data query — thousands of times an hour, with no way to pay for them.

How Satelink works

The flow

01
A service publishes a machine-readable catalog and price.
02
A machine buyer pays with x402, USDT, or a prepaid balance.
03
Revenue settles on-chain per epoch.

Two sides

Machine buyers and sellers

Machine buyers

Machine buyers discover and pay for services programmatically.

Machine sellers

Machine sellers expose a priced endpoint and get paid per call.

Capabilities

What you get

Public discovery

HTTP 402 pricing

Three payment rails

On-chain settlement

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

Data marketplaces
API monetization
Agent-to-service payments

Frequently asked

About the offering

Is this a marketplace?

It is the payment and discovery rail underneath one. Services list a priced endpoint; buyers pay per call.

Trust and safety

What stops an agent from paying a price that isn't real?

Prices are quoted in signed 402 requirements, per-key limits apply, and receipts are on-chain.

Products behind this solution

Machine Commerce

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

x402 Machine Payments

HTTP-native, keyless payments in USDC on Base.

API Metering

Credits and per-call usage metering you can audit.

See Satelink for commerce

Talk to Satelink See pricing