Charge agents for what you run.
Put a price on a page, API, or tool. A person or their AI agent pays in compute they already hold. You get compute and a receipt for every payment.
How getting paid works
- Set your price. Choose what to charge for and which provider compute to accept.
- Let them pay. A person or their agent pays before getting access.
- Get your balance and receipt. The compute is yours, and the protocol fee is shown separately.
See the technical payment flow
- Price: you set the exact access price and provider denomination for your route.
- Present: the visitor submits its capped native provider key to the signed surrender endpoint with the exact challenge descriptor and an idempotency key.
- Verify: Door 1 probes balance or custody before charging. Door 2 makes the exact charge as the measurement, so no advance balance read is required.
- Grant access: Door 1 returns a signed, single-use, resource-bound
qtt1ticket. Door 2 uses the committed payment movementevent_idas the access grant. - Settle: Foinse preserves the accepted backing and records your bearer token balance. Payer debit equals your credit plus the separately disclosed protocol fee.
- Receipt: the accepted settlement posts with its movement, fee, and evidence status. Later revocation of the original provider key does not unpay you.
Use your balance your way
Hold it, transfer it, list it on the exchange, or spend it with its provider. Each provider's compute stays separate; to use another provider, exchange for that provider's compute first.