AI agent marketplace: how they work, which type fits.
An AI agent marketplace is a catalog where you find, compare and buy AI agents or the work they do. In 2026 there are four distinct types, and they serve different buyers: enterprise app stores tied to a platform you already run, public directories that help you discover tools, agent networks that mimic freelancer platforms, and per-run job catalogs where you buy a finished task instead of an agent. Most coverage only describes the enterprise stores, which is useless if you are an ops lead or founder without a ServiceNow contract. This guide maps all four types, explains the pricing models behind them, and shows the fastest low-risk way to test one: pick a single bounded job, pay for one run, and judge the output like you would judge a contractor's first delivery.
Is there a marketplace for AI agents?
Yes, several dozen, and the count grows monthly. The confusion is that "AI agent marketplace" describes four different kinds of shop.
The big software platforms run their own stores, where agents install into their ecosystem. Public directories list hundreds of agents and tools with reviews and categories. A newer wave of agent networks presents agents like professionals for hire, with profiles and specialties. And execution catalogs sell the outcome rather than the agent: you submit input, an operated agent does one fixed-scope job, you pay for that run.
The distinction that matters is what you take home. In the first three, you adopt software you then have to configure, connect and supervise. In the last one, you receive a deliverable. Threads like the r/LangChain discussion on agent marketplaces show even builders disagree on which model wins, which is a good reason to buy by the job before you buy a platform.
What types of AI agent marketplace exist?
| Type | What you actually buy | Pricing model | Lock-in | Fits |
|---|---|---|---|---|
| Enterprise platform store | An agent that installs into a suite you run | Bundled with the platform contract | High: the agent dies with the suite | Companies already deep in one ecosystem |
| Public directory | Discovery: links, categories, reviews | Free to browse, each tool has its own fee | None, but every trial costs setup time | Research phase, tool scouting |
| Agent network | Access to hosted agents with profiles | Subscription or usage credits | Medium: workflows form around it | Teams wanting many light assistants |
| Per-run job catalog | A finished task: extraction, triage, cleanup | Pay per execution, no subscription | Low: stop any time, keep the outputs | Ops teams testing AI on real work |
Pitstop sits in the last row: a catalog of fixed-scope AI jobs, priced per run, where you can browse the catalog and see exactly what each job takes in and returns. The other rows are real options too; the table exists so you stop comparing a platform store to a job catalog as if they were the same purchase.
How much do people pay for AI agents?
Four pricing models cover the market, and each one shifts the risk differently.
- Platform bundling: the agent is "free" inside a contract you already pay; the real cost is the contract
- Subscriptions: a monthly fee per agent or per seat, which bills whether or not the agent worked that month
- Usage credits: prepaid credits burned per action, transparent when actions map to outcomes, opaque when they map to internal steps
- Per-execution pricing: a listed price for a defined job with a defined output, paid when it runs
There is also a hidden line item worth demanding clarity on: model costs. Some services resell model tokens at a markup buried in the price. A cleaner pattern is bring-your-own-key, where model usage bills to your own account at cost and the service charges only for the work. That is the intended Pitstop model, but the public transaction rail is not live: the catalog currently accepts scoped requests and waitlist entries, not purchases.
What is the Google AI agent marketplace?
Google Cloud runs an AI agent marketplace for its cloud customers, where partners publish agents that deploy into a Google Cloud environment. Oracle ships one inside Fusion applications, ServiceNow inside its store, Moveworks inside its assistant. They are genuine marketplaces with real vendors behind them.
Read the fine print of the model, though: these stores exist to deepen the platform relationship. The agents assume the platform's data model, run inside its permissions and billing, and stop existing if you leave. For an enterprise already committed to the ecosystem, that is efficiency. For a small team without the platform, it is a door to a house you do not own. Directories such as AI Agents Directory are the neutral counterpart: wide inventory, no execution, you still do all the integration work yourself.
How do you choose from an AI agent marketplace?
Run five checks before any money moves.
- Scope: is the job defined in writing, with named inputs, outputs and limits, before you pay?
- Unit of billing: do you pay for outcomes (runs, deliverables) or for capacity (seats, credits) you must remember to use?
- Model costs: are tokens resold at an undisclosed markup, or billed to your own key at cost?
- Exit: if you stop next month, what do you keep Outputs only, or configuration you can take elsewhere?
- Proof: can you see a sample output for the exact job before running your own data through it?
A marketplace that survives all five is safe to test with real work. A marketplace that fails on scope or exit is a subscription wearing a catalog costume.
What should your first purchase be?
Start with the most boring job you repeat weekly. Invoice batches into clean rows. An inbox triaged into categories. A spreadsheet deduplicated and normalized. Meeting audio into structured notes. These jobs share three properties: the input is easy to hand over, the output is easy to judge, and a failure costs you nothing but the run.
Buy one run. Compare the output against what your team produces by hand, on the same batch, so the comparison is honest. If it holds, wire it into the weekly routine and only then consider bigger scopes, like the heavy runs tier for larger workloads. If it does not hold, you learned the limit for the price of one execution instead of an annual license.
That sequence, one bounded job then a routine then a bigger scope, is how ops teams adopt AI without a platform decision hanging over every step. It also builds the evidence file you will want later: when someone proposes an agent platform for the whole company, you will know from receipts which jobs AI already does well for your team and which ones still need a human.
FAQ: AI agent marketplaces
What is the difference between an AI agent marketplace and an AI tool directory? A directory lists tools and links out; you still evaluate, buy and integrate each one. A marketplace transacts: the agent or the job is purchased and delivered inside the same surface.
Can I sell my own agent on these marketplaces? On the enterprise stores, only through partner programs. On directories, usually yes via submission. On job catalogs it depends on whether the operator curates the roster; curation is what keeps output quality predictable for buyers.
Are AI agent marketplaces safe for company data? Treat each listing like a vendor: check who processes the data, where it is stored, whether it trains models, and whether you can delete it. A per-run job with a defined input file is the easiest case to review, because the data boundary is one file in, one file out.
Do I need my own API key to use a per-run catalog? On bring-your-own-key services, yes, and it is a feature: model usage bills at cost on your account, and you can see exactly what each job consumed. Services without BYOK are fine too; just ask how model costs enter the price.
Ready to test the model on something real Pick a job from the catalog and run your first AI job this week: one bounded task, one run, judged on the output.