Spend what you have.
Authorize an eligible metered compute right for access to value. The source and instrument are verified at the crossing.
Loop 01 / toll
A way to pay. A way to be paid.
Humans and agents already exchange value. Foinse lets metered compute settle the crossing and remain usable after it moves.
Pay and earn are positions in a transaction. They are not permanent participant classes.
VALUEPAYCOMPUTEEARN
The loop belongs to every participant.
A human can pay an agent. An agent can pay a human. Humans can pay humans. Agents can pay agents. The direction changes; the settlement grammar holds.
H → HPay for human value
H → APay for agent value
A → HPay for human value
A → APay for agent value
The payment does not end at payment.
The recipient gets title to a metered compute right. That right can remain in the toll loop, enter the market loop, or return to the underlying resource.
Receive something usable.
Hold it. Transfer it. Sell it. Use it. Settlement creates a route forward, not a dead-end receipt.
Gas Toll is the first route through this loop.
Middleware quotes access, the visiting agent authorizes payment from prepaid provider quota, and settlement issues the recipient a computable right. API credentials are the first instrument, not the limit of the protocol.
- 01 / METER
Name the value.
The supplier sets the toll for access to a page, endpoint, file, action, or other bounded value.
- 02 / QUOTE
Name the right.
The response states the accepted denomination and amount in machine-readable form.
- 03 / AUTHORIZE
Prove the payer.
The payer authorizes an eligible source and instrument for the exact quote.
- 04 / SETTLE
Move title.
The toll settles and the recipient holds the resulting compute right.
Processing is the product.
Price one resource, install the canonical integration, and let arriving agents pay from capacity they already hold. Your share lands as provider compute of the denomination they paid.
| Line | Amount | Lands where |
|---|---|---|
| Toll | You set it | Authorized by the agent for one request |
| Processing fee | 5% | One declared rate, taken in the toll denomination |
| Your share | 95% | Your account, as provider compute |
The payer needs no Foinse account. Foinse issues nothing, and the asset you receive is the provider's.
Then the second loop opens.
What is earned can move directly into sell ↔ buy without becoming a different resource.
The words this page uses
One object, one name. The full published vocabulary is on the terminology page. Terminology.
Status is stated at the surface it describes. Each market row says whether it can clear and why; live, preview, unavailable, and independently verified are not treated as interchangeable claims.
- Provider asset
- The provider's own metered unit of compute. It is the provider's, and it is not fungible across providers or models. Foinse does not issue it.
- Compute claim
- The ledger claim a holder has against provider capacity in measured custody, one to one and hard-capped at the verified deposit. It is what is listed, bought, and redeemed.
- Access authority
- The scoped, metered right to be served, held by whoever holds the claim. It is what a toll charges for.
- Execution
- Metered inference actually delivered against a claim and measured as it is delivered.
- Listing
- An offer of a held compute claim at a stated price in a stated denomination. Listing moves no claim on its own.
- Payment
- A settled crossing, carrying one declared fee that is identical for everyone.
- Payout
- Settled proceeds moving to the holder's own destination at the exit boundary.
Foinse issues nothing: providers issue the compute, custody is one to one with what was measured, and a human and its agents share the one wallet value moves through.
The two loops
Pay & earn: visitors pay a toll in compute to reach what a site runs; operators earn compute for what they serve. Sell & buy: holders list compute credits and buyers take them at the listed price, each provider credit clearing as its own asset.