References & scope
Primary documentation and comparison sources, plus the limits of this handbook.
Primary references#
Message fields and sign-in semantics; not a payment authorization.
The signature-verification library interface used by the account foundation.
Authoritative network details and RPC guidance.
Asset verification source, not an IdleAI deposit instruction.
Candidate initial supply setup; deployment requires account access and spending approval.
Runtime, startup, idle, and storage costs.
Protocol semantics; concrete network/facilitator support must be checked separately.
Check the current supported matrix rather than assuming all EVM chains work.
Product and research references#
A reference for a direct multi-model, crypto-funded workspace—not proof of IdleAI functionality.
Review detailed data handling rather than relying only on homepage wording.
A reference for explicit privacy tiers; vendor statements are not an independent audit.
A research starting point; verify each provider's terms, quotas, privacy, and resale rights.
A context/retrieval tool to evaluate for relevant workloads, not a universal cost-reduction guarantee.
Scope of the handbook#
This handbook is grounded in the current implementation and the agreed product direction. Time-sensitive network, vendor, quota, pricing, and policy details can change. Recheck primary sources before making a deployment, spending, or compliance decision.
It is not a service-level agreement, a finalized privacy notice, a financial promise, an investment thesis about a token, or a substitute for legal/security review. No partnership, endorsement, confidential-execution guarantee, or production readiness should be inferred from a reference link.
Maintain this book with the product: update the capability matrix after verified releases, keep examples honest about disabled endpoints, and never replace evidence with a screenshot or a successful build log.