The words this system uses, and what each one names.

VALUE, ACCESS, AND EXECUTION

The core objects

A key is access. The bearer token balance is value. The native provider supplies inference. None of these objects silently performs another object's role.

Provider token

A provider-denominated unit of premetered inference. DeepSeek, Kimi, and Qwen tokens are distinct denominations. The working denomination is provider-wide: model selection and metering can occur at native execution rather than making every model version a separate currency.

Bearer-secret token balance

The transferable value recorded to a holder on the Foinse ledger and backed by accepted provider-capacity value. It is the object held, paid, transferred, listed, or spent. It is not the payer's native API key and not a Foinse-issued asset. Compute credit or compute claim may describe its ledger/accounting form, but neither names a second asset.

Native provider key

Provider-issued access to a provider account. A payer may present a capped native key to authorize a toll. The recipient never receives that key. A subscription, identity, and provider account are not the bearer value being traded.

FK1: Foinse Key 1 / Foreign Key 1

A Foinse-issued bearer access credential bound to one Foinse account. It gives the holder access to that account's bearer token balances for permitted transfers and for inference through Foinse's spend path. It is not the rail itself, the money, a native provider key, or a container of somebody else's provider key. Foreign describes access foreign to the native provider while the value remains native to that provider.

Quota key

A capped authorization created around a native provider key. Use issue or create for that operation. It is not a third account-key family beside the native provider key and FK1.

Native provider / mint

The provider that denominates and meters the token and supplies native inference. Mint is the fiscal metaphor for that monetary role, not a competing technical primitive or a Foinse action.

Execution

The technical model call. Consume inference names the actual usage metered by the native provider. Payment, receipt, and ledger transfer are not inference consumption.

Foinse ledger

The ownership and settlement record for bearer token balances. A ledger-local transfer can change the holder without a provider call; native inference execution still involves the native provider.

Reserve lot

The backing and provenance record beneath a recorded balance. Pooling available inventory does not erase lot-level backing or make unlike provider denominations fungible.

COMPUTE PROCESSING

The toll, and the two retained doors

Compute processing

Accepting, recording, and settling payments denominated in provider tokens. Foinse is a compute processor, not merely a conventional fiat payment processor. The recipient's full listed amount and the processing toll are separate lines: payer debit = recipient credit + protocol fee.

Toll

A creator's price for access to a paid route or resource, or the disclosed Foinse processing charge, according to context. Public receipts should make the actor and movement explicit rather than relying on the bare word.

Paid route / resource

The creator's route or resource to which a visitor purchases access. It is distinct from the underlying compute resource of silicon, energy, time, and model inference.

Door 1: historic working proof

Verify before charging. Foinse probes capped provider-key balance or custody first, then accepts the toll. The visitor receives a signed, short-lived, single-use, resource-bound qtt1 access ticket. That ticket authorizes the creator's paid route; it is not FK1, a receipt, or raw compute.

Door 2: improved charge-first path

Verify by charging. The exact charge is the measurement, so no advance balance read is required. A decline produces no accepted toll. The committed payment movement's event_id is the access grant; this path does not need a separate qtt1 ticket.

Backing and custody

The accepted value and its access instrument or capacity record support the recipient's balance one to one. Door 1 and Door 2 change the verification method, not the requirement for backed value and exact accounting. No advance balance read in Door 2 does not mean no backing after acceptance.

Settlement finality

Once Foinse accepts and records settlement, later revocation of the original provider key does not unpay the recipient. External card disputes remain separate external processes rather than an implied rewrite of the Foinse ledger history.

CIRCULATION

Two loops, one wider economy

Pay and be paid

The earning loop. A visitor pays provider compute for access and the creator earns that provider-denominated value. Earning is as fundamental as funding: participation does not require topping up another prepaid wallet first.

Sell and buy

The market loop. A holder supplies a provider-denominated balance and a buyer acquires from pooled available inventory in that denomination. The buyer need not select a named seller; reserve lots retain provenance beneath the pool.

Transfer

A same-denomination change of holder. Transfer is not exchange and is not inference consumption.

Spend / redeem for inference

Use a bearer token balance through Foinse's spend path, with FK1 supplying account access, to obtain inference from that balance's native provider. Redeem is the formal economic synonym for spend; it does not mean cashing out, converting denominations, or presenting FK1 as a native provider key.

Exchange

The separate vertical rail for crossing between distinct token denominations or into fiat or crypto. Spending DeepSeek value for DeepSeek inference is not exchange. Obtaining another provider's inference first requires that provider's denomination or an exchange.

Pooled available inventory

An aggregation of available units within a provider denomination from which a buyer purchases. It is not a house asset, a named-seller requirement, or cross-provider netting.

Listing

An offer to supply a stated quantity at a stated price. Listing alone does not move the bearer balance.

Order reservation

Fixing or locking exact order terms while payment completes. It is unrelated to reserve backing, reserve lots, or capacity custody.

Fiat and crypto rails

Entry, conversion, and exit boundaries into the wider human economy. Provider-denominated compute is the asset inside the compute market; fiat and crypto are boundary denominations, not additional Foinse-native trading markets. Legal identity checks may apply at external regulated payout or provider rails and are distinct from ordinary account authentication.

ACCOUNTS AND ECONOMIC AGENCY

The current shared-wallet arrangement

STATUS AND EVIDENCE

Name the state of each surface

Current

A presently implemented or evidenced mechanism. A proof of one route does not make every product surface generally available.

Historic

A retained earlier implementation or proof, such as Door 1. Historic does not mean fake or discarded; it must not be presented as the universal current flow.

Planned

An intended future service or surface, such as OTC block negotiation before that service is available. Planned capabilities must not carry live operational language.

Unverified

A claim whose required evidence has not been inspected or supplied. It must remain labeled rather than being promoted by logical expectation.

Live proof versus live product

A live evidence record establishes the route it actually exercised. Operational availability, independent-party attestation, fixtures, and future surfaces require their own explicit labels.

BOUNDARIES

What Foinse does not do

No house asset.

Foinse issues no Foinse currency, crypto token, unbacked credit, or balance whose value rests on a Foinse promise. It does record and credit ledger positions after accepting backed value; that accounting action is not native-asset issuance.

No AI model supply.

Foinse does not provide the AI or execute inference merely because it records economic settlement. The native provider executes and meters its own inference.

No payer-key transfer.

The recipient does not receive the payer's native API key, subscription, or identity. Credentials are not resold as the product.

Not a fiat bank.

Foinse does not offer a fiat bank account, take insured cash deposits, engage in fractional-reserve lending, or create a promise to repay dollars. Technical custody of provider-compute backing is a separate, affirmative mechanism.

Not a crypto-token exchange.

The market exchanges provider inference tokens, not blockchain assets. Crypto remains one possible exit denomination.

Not merely a router.

FK1 performs a router-like account-access function, but Foinse also supplies toll acceptance, backing records, custody, ledger ownership, settlement, exchange, and receipts. It does not sell pooled inference or make unlike token denominations fungible.

Analogies stay bounded.

Central-bank-like settlement discipline and cryptographic-hawala-like transfer patterns can explain the monetary mechanics. They do not assert sovereign authority, legal status, cryptocurrency, decentralization, anonymity, or a new institutional identity.