Illustrative scenario · Mm + Fi + Vs

A software platform billing people and agents

A US software company selling seats to people and usage to AI agents.

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

Mm Fi Vs

Video, 36 seconds, illustrative. One person, one agent. One record of who checked, approved and paid. Captions are burned in and also available as a track. Step list for software (JSON) · Captions (WebVTT) · MP4

The problem

Seats bill monthly by card. Agent usage arrives in millions of tiny calls. Today these sit in two systems that never agree.

Value anatomy

01 · transaction
Seats renew by card. Agent usage is metered per call against each agent's mandate.
02 · rails
Cards for seats. Per-request payments in fiat or stablecoins for agent usage.
03 · record
Both streams land in one ledger, by customer, so revenue and fees reconcile in one place.

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.
Card account updates	Keep stored cards current.
Fee lines	Network, scheme and insimbi fees, itemized per transaction.
Data streaming	Raw events, settlements and fees into your warehouse.

Request access

insimbi is in early access with design partners.