Security
Risks
User, protocol, market, and regulatory risks.
Where availability depends
Payment
Chain + oracle + identity
Credit
Worker + database
Security
User, protocol, market, and regulatory risks.
Where availability depends
Payment
Chain + oracle + identity
Credit
Worker + database
Inference
Gateway + model provider
Payments purchase AI usage, not a cash balance. Credit cannot be withdrawn or transferred through the app. Transactions cost gas and successful payments are final.
RPC outages, finality delays, indexer downtime, or database failures can delay credit. Provider outages and model changes can affect inference. A successful on-chain receipt does not mean settlement has already completed.
USDT is treated as $1 by the contract even if its market price changes. BNB conversion depends on an oracle. A compromised admin can replace that oracle or pause payments. A missing or unavailable Agent ID blocks topups and AI access.
Losing wallet access can prevent access to its credit. Protect API keys because they can spend the wallet's balance within their configured limits. The service depends on durable off-chain credit records and accurate usage accounting.
Local Chat history can be lost by clearing browser data and is not a cross-device backup. Deleting a conversation does not cancel billing for a request already accepted by the server. Reasoning tokens can increase charges even though the interface only shows the answer.
An API key with no explicit model restriction can access future enabled models. A lifetime budget can limit that key's spending, but it does not isolate or reserve a separate wallet balance. See API keys.
Topups create no rewards, yield, or airdrop rights. Existing historical claims retain their original contract risks. New topup credit does not expire, but service availability is not guaranteed forever.