Overview
Official SDKs for the inndx Cloud API with built-in payment handling.
inndx provides official SDKs for TypeScript and Rust. Both handle the MPP payment flow automatically: the 402 challenge, wallet signing, and retry all happen inside the SDK. Your code makes one call and gets one response.
Choose an SDK
- TypeScript — ESM, Node 20+. Supports server-side private key signing and browser signing via wagmi.
- Rust — async, runtime agnostic. Supports private key signing server-side.
Shared concepts
The signer
Both SDKs require a signer to authorize payments. For server-side use this is a wallet private key. The TypeScript SDK also supports a prebuilt viem account or a wagmi connector for browser use.
Per-request and session endpoints
An endpoint is either per-request or session-based, and this is fixed by the API rather than a choice you make at call time. Per-request endpoints are billed individually with no state to manage. Session endpoints require you to open a payment channel, make calls against it, then close it to settle on-chain. The Scrape API endpoints are session-based. See Per-request and sessions for the billing concepts.
Reclaiming a stranded channel
If a process exits before a session is closed, the escrowed deposit stays on-chain. Both SDKs provide a reclaim flow to recover it using a two-step forced close with a 15-minute grace period. This is covered in each SDK's reference below.