FAQ & troubleshooting

The core loop works: sign in, deposit USDG, run billed inference through verified supply, get a receipt — and withdraw unused balance back to your wallet. What remains incomplete is supplier self-service payouts, streaming, and x402. The status page is the reference for capability maturity.

It should not be — the OpenRouter catalog is published. If the list is empty, no offer is currently active (credential missing, offer paused, or upstream outage). The API returns an explicit error rather than a fabricated model list.

• No provider found: open the site in a compatible EVM wallet browser or install a suitable browser extension.
• Wrong network: approve the Robinhood Chain selection, then retry the sign-in flow.
• Signature rejected: check the message/domain, selected account, and whether you canceled or changed accounts.
• Challenge expired or replayed: start a fresh sign-in; do not reuse the old signature.
• Service unavailable: storage or RPC verification may be unavailable. Do not work around it with a generated address.
• Origin rejected: use the canonical HTTPS site; operators must verify origin configuration rather than disable CSRF checks.

No. Only the hash and identifying metadata are persisted. If the secret is lost, create a replacement and revoke the old key. Do not ask support to reveal a stored plaintext credential; the system should not have one.

Not automatically. Consumer subscriptions, purchased credits, promotional credits, rented GPUs, and owned hardware are different products with different rights. The provider/model terms must explicitly permit the intended arrangement. Supplying authorized inference is not the same as transferring somebody else's account.

No. Payments can be linkable and providers may see plaintext. Privacy depends on the full request path and data-handling controls. Confidential execution is a separate capability, not a consequence of paying on a blockchain.

No such guarantee is established. Free-tier quotas have limits and terms, and a cheap GPU does not automatically yield cheap completed requests. Savings must be measured against equivalent workloads and include relevant service costs.

Submission stores your declaration for review. It does not verify endpoint control, licensing, privacy, capacity, or payout eligibility. Do not expect traffic or earnings before those steps are complete. Duplicate applications are not a way to bypass review.