Browse documentation
Funding and accounting
Creator fees are a funding source
A community can be funded with collected creator or LP fees, voluntary contributions or an operator subsidy. The source of a contribution is not inferred from its sender alone. A public transfer from a creator wallet is not proof that it consists entirely of trading fees.
The build does not promise a percentage of volume, automatic revenue routing, yield, dividend, token buyback or cash redemption. It has no staking or tradable-credit contract. If an operator advertises a fee commitment, it must implement, evidence and maintain that commitment separately.
Deposit lifecycle
- Prepare a native SOL or ETH contribution. The app displays the treasury, amount, conservative USD estimate and expiry.
- Sign in the funding wallet. The server verifies the exact prepared chain transaction and prevents reusing its receipt for another credit.
- The deposit appears as awaiting provider funding. The community balance is unchanged.
- The operator converts funds if needed and purchases provider credit outside this app.
- A local administrative allocation checks the provider management endpoint and outstanding obligations before activating credit.
The funding estimate includes the configured FX buffer. It is an upper allocation limit for that recorded deposit, not a guarantee of what an exchange will deliver after gas, slippage, taxes or provider fees. Unallocated proceeds require documented operator treatment and disclosure.
Conservative capacity control
Money is stored in integer USD millionths. A $1 budget is 1,000,000 accounting units. The gateway observes OpenRouter account credit using a server-side management key and checks shared reservations across communities before admitting requests.
New allocations also consider existing community balances, personal-service balances and pending obligations. Use a dedicated provider account. External spending, concurrent operator changes, provider reporting delays and billing adjustments can still reduce available capacity; the application does not control OpenRouter’s ledger.
A cached capacity observation expires quickly. Unknown requests stay reserved. If the provider reports a cost beyond the community’s remaining funds, the real cost is recorded, the visible balance cannot go negative and the community is paused with an operator-shortfall audit record.
Request accounting
A request reserves a conservative byte-based input estimate, the requested output limit and published request-level pricing. Provider routing is constrained by the current published prompt/completion price ceilings. This is not a mathematical guarantee about every provider’s billing rules.
Actual reported cost replaces the reservation. The remainder returns to the community, not to an individual holder. Known request rejection releases its reservation. Unknown cost is not silently treated as zero.
Provider reports can arrive after interruption. The operator reconciles a recorded generation ID to its provider record, checks the model and records the confirmed charge. A manual refund requires an investigation reason and creates an audit record.
Public and private records
Public community records include total activated funding, available budget, recorded usage and transaction-linked deposits. Personal API secrets, request contents and management credentials are not published. The public funding response omits internal provider-allocation references.
The funding chart uses actual settled costs by UTC date. Missing historical days are not invented. A zero available balance does not mean trading failed; it means no service budget remains available to reserve.
Service interruption and refunds
Exhausted funding pauses access; it does not destroy the token. User-facing promises must distinguish donations, paid service and conditional access accurately. A token purchase on an unrelated market is not automatically a purchase of a fixed API balance from the operator.
The service has no cash-withdrawal interface. This does not exclude statutory refund or compensation rights. Investigate an unavailable paid service, misdirected deposit, duplicated charge or mistaken allocation using the complaints process. Never describe every payment as unconditionally non-refundable.
Exact receipt verified. No API credit yet.
Funds converted and OpenRouter credit purchased.
Credit allocated against provider capacity and obligations.
Known cost settles. Uncertain cost stays held.