Skip to content
IdleAI/Docs
Workspace
Handbook/Start here
Implemented

Start here

What you can safely do now as a buyer, developer, or prospective supplier.

Reviewed 20 September 20264 sectionsUnderstand the status labels

Choose your path#

If you want to…Start with…Available today
Follow the launchThe public waitlistRegister interest and use a referral link.
Use AI modelsWallet sign-in and ChatSign in, fund with USDG, pick a model, send.
Integrate an applicationDevelopersCreate and revoke credentials, inspect the API contract.
Offer inferenceSupplySubmit an application for review.

Buyer setup#

  1. Open the workspace from the canonical IdleAI site.
  2. Use a compatible EVM browser wallet or a wallet's built-in browser.
  3. Connect the account you intend to use and approve the Robinhood Chain network selection if needed.
  4. Read and sign the sign-in message. It does not authorize a payment or token approval.
  5. Explore the workspace. Browse the live model catalog, create an API key, or add funds.
  6. To fund: send USDG on Robinhood Chain from your connected wallet to the treasury address shown in Usage & balance, then claim the transaction hash. Never send other assets or funds from a different wallet.

If no wallet provider is available, the application should explain that requirement. It must never invent an address to make the interface appear connected.

A safe API check#

bash
curl --fail-with-body https://idleai.xyz/api/v1/models
Read-only request. No inference or blockchain transaction is performed.
json
{
  "object": "list",
  "data": [{ "id": "openai/gpt-4o-mini", "object": "model" }]
}
Abbreviated. The response lists every published model with an active offer — currently the OpenRouter catalog at cost +5%.

Model ids follow the upstream author/slug convention (variants use :, e.g. openai/gpt-5-nano:batch). If the catalog is ever empty it means no offer is currently active — not that keys are broken.

Supplier setup#

Sign in, open Supply, and submit your name, HTTPS base endpoint, exact model identifier, operations contact, serving-rights confirmation, and retention description. Do not put API keys in the URL or application text. An application is an intake record, not activation.