# An agent paying for API calls, one request at a time

A US data provider selling an API, and the AI agents that call it.

**Illustrative scenario.** A fictional type of business, not a customer. No results are claimed.

Cohorts: Mm + Sc

## The problem

Agents need data now, not after a sales call and a monthly invoice. API keys and invoices don't fit software that buys on its own. The provider needs to know who is paying and to stop runaway spend.

## Value anatomy

1. **Transaction**: The API answers an unpaid request with a price. The agent's mandate allows it, so it pays and retries.
2. **Rails**: Small payments settle in a dollar stablecoin, or batch onto a card when the buyer prefers.
3. **Record**: Each call, its price and the mandate that allowed it land in one line. The buyer and the provider see the same record.

## What it uses

- **Per-request payments**: Charge or pay per API call over HTTP 402, in fiat or stablecoins.
- **Agent mandates**: Bind an agent to a principal, a spend limit and a scope.
- **Payment intent preview**: Check a request against the mandate before it runs.
- **Scoped API access**: Credentials limited to one principal and one scope.
- **Fee lines**: Network, scheme and insimbi fees, itemized per transaction.

Request access: sales@insimbi.net

_insimbi is in early access with design partners._