Welcome to IdleAI
The product thesis, who it serves, and why the marketplace belongs behind a simple AI workspace.
In this chapter
What is IdleAI?#
IdleAI is being built as a marketplace for AI inference: the computing work that turns a prompt into a model response. Buyers should be able to access supported models through one workspace and one API. Qualified suppliers should be able to offer inference capacity, compete on service quality and price, and earn from actual demand.
In everyday terms, the goal is to connect people who need AI work done with operators who can perform that work. Buyers purchase a service, not ownership of a GPU. Suppliers sell completed inference, not an automatic entitlement to revenue merely for being online.
Who it is for#
| Audience | What they need | Intended IdleAI experience |
|---|---|---|
| AI users | An understandable way to use models | Choose a model, write a prompt, understand the price, receive an answer. |
| Developers | A consistent API and manageable credentials | Use scoped access and observable usage without integrating every supplier separately. |
| Agent builders | Programmatic access and bounded spending | Use API credentials initially; x402 payment support is a planned additional path. |
| Inference operators | Demand for legitimate serving capacity | Apply, complete verification, publish eligible supply, and receive reconciled earnings. |
Why the default experience is not an exchange terminal#
The original exchange metaphor led to order books, limit-order tickets, positions, and P&L. Those concepts introduced friction before a buyer could receive an AI answer. They also suggested financial trading and interchangeable credits that the service had not established.
The agreed direction is workspace first, marketplace underneath. A person should not have to understand a bid/ask spread to ask a model a question. The marketplace remains relevant to supplier selection, pricing, availability, and settlement; it does not need to dominate the buyer interface.
- Keep model choice, price transparency, and privacy requirements visible.
- Keep provider routing, capacity management, and accounting behind the workflow.
- Revisit reservations or advanced procurement only if real customers need them and the service contracts support them.
What we are combining#
Askr provides a useful reference for direct, crypto-funded access to multiple models. Venice provides a useful reference for distinguishing privacy levels rather than treating privacy as a single vague promise. IdleAI's intended addition is a qualified supply marketplace with transparent service conditions.
These are design influences, not claims that IdleAI currently outperforms those products. Better value must be demonstrated with equivalent workloads, reliable execution, enforceable privacy boundaries, and sustainable unit economics.