inndx/
GitHub

How it works

The conceptual model behind inndx Cloud and how a request flows from call to response.

Every inndx Cloud API follows the same pattern: send an HTTP request, the API fetches and processes the target resource, payment is settled, and you get back structured data. There is no account to create and no API key to manage. Payment is attached to the request itself.

The payment model

inndx Cloud uses MPP, the machine payments protocol. The flow looks like this:

  1. You send a request to the API without payment.
  2. The API responds with 402 Payment Required and a payment challenge stating the price.
  3. Your client signs an authorization from your Tempo wallet and retries the request.
  4. The API verifies the payment and returns the result.

The SDKs and tempo request handle steps 2 through 4 automatically. From your code's perspective you make one call and get one response.

Per-request vs sessions

By default each request is its own payment. For high-volume work the SDKs support payment sessions: you open a channel that pre-authorizes a batch of calls, make as many requests as you need against it, then settle once on-chain. Sessions reduce the overhead of per-call signing and are the right choice for pipelines that scrape many pages in a short window.

If a process crashes with a session open, the deposit is not lost. See Reclaiming channels for how to recover it.

Pricing

Calls are priced in units. The base price is $0.002 per page. Some options multiply the unit count:

OptionUnits
Base request1
Proxy2
JavaScript rendering6

A request with a proxy enabled costs 2 units ($0.004). A request with JavaScript rendering costs 6 units ($0.012).

What comes back

The API returns the page's content in the format you requested: markdown, HTML, JSON, or binary. Navigation, ads, and boilerplate are stripped. The result is ready to feed into a model, a vector store, or any downstream system that consumes text or structured data.

See Output formats for a full breakdown of what each format contains.

Funding a wallet

You need a funded wallet on the Tempo network to pay for calls. See the Tempo funding guide for options including the web wallet, the CLI, and the bridge from other chains.

If you are setting this up inside an AI agent, point it at https://tempo.xyz/SKILL.md and ask it to fund a wallet. The SKILL.md instructions automate the entire process.

Search docs

Search the Cloud documentation