One AI business. The right add-ons. Behind the scenes: AIMs.
AI Markets is a buyer's storefront for prepackaged AI businesses. The technical complexity — AIM registries, nodes, deployment, routing — is hidden. Customers see capabilities; providers earn in the background.
From customer click to provider earning
Pick an AI business
Browse prepackaged AI businesses (Auto Dealer, Clinic Phone, Delivery Support, etc.). Each one is a complete product with included capabilities.
Choose only relevant add-ons
On each business page we show ONLY the add-ons that fit. The clinic never sees music generation. The content studio never sees medical OCR.
AI Markets routes the work
When the AI business runs, AI Markets routes calls to the right backing engine — a HyperCycle AIM, a deployable node, or an external API — so the customer never has to think about plumbing.
Customer ships, providers earn
The customer gets enhanced capability inside their packaged AI business. The HyperCycle node / AIM provider / API provider behind each call earns automatically.
Behind a single add-on call
Customers see a single "Voice Transcription Add-on" toggle. AI Markets handles the rest.
Four kinds of backing engines
Customers don't see this — but every add-on tells you honestly (via a small badge) what it's running on today.
Listed in the HyperCycle AIM registry as *-aim-gen images. Examples: voice transcription (whisper-aim-gen), sentiment (sentiment-aim-gen), image generation (diffusionxlbase-aim-gen). Deployable to a node.
Existing third-party HTTP APIs. Useful when a SaaS provider offers a capability not yet covered by an AIM.
Workloads running directly on a node binary. Used for capabilities that aren't a single model, like long-running pipelines.
Workflow-shaped add-ons (Lead Qualification Agent, Appointment Booking Assistant) that are honest UI placeholders today and will be wired to AIMs/nodes in production.
Honest prototype note
Some add-ons are currently registry-listed or UI-only in this prototype. AIM-backed add-ons (whisper, sentiment, OCR, image-gen, etc.) are listed in the HyperCycle registry — production will deploy them to a node and switch their status from Registry Available to Deployed / Callable.