What Happens When You Submit 3 AI Agents to a Marketplace and Wait 140 Hours
On September 16, 2026, I submitted 3 AI agents to aitopia.ai — an AI agent marketplace with a 70/30 BYOM revenue split. All 3 passed validation. All 3 are still in_review.
140 hours later, no reviewer has been assigned. Earnings: $0.
This is the honest build-in-public story of what that experience looks like.
The 3 Agents
All 3 agents are hosted on a single Render web service (FastAPI, one service, three routes):
| Agent | Endpoint | What It Does |
|---|---|---|
| CBT Thought Analyzer | / |
Detects 12 cognitive distortions in text |
| Procrastination Pattern Detector | /procrastination |
Identifies 8 procrastination patterns with CBT interventions |
| Attachment Style Detector | /attachment |
Classifies 4 attachment styles (Bartholomew 1990) |
Each agent uses the remote_http invocation model — aitopia.ai proxies user calls to my endpoint. I keep control of the logic. Pricing is BYOM (Bring Your Own Model) at 5 credits per run.
The Submission Process
The submission API is clean:
POST /api/developers/agents/submit
{
"agentType": "remote_http",
"pricing": { "mode": "byom" },
"fixedCreditsPerRun": 5,
"endpointUrl": "https://cbt-thought-analyzer.onrender.com"
}
All 3 submissions passed validation:
- Namespace OK
- Pricing OK
- Endpoint health check OK (aitopia.ai reached my Render endpoint)
What Happened Next
Nothing.
reviewed_by: null
reviewed_at: null
status: "in_review"
Day 1: "Review takes 1-3 business days."
Day 2: "Maybe they're backed up."
Day 3: "The docs 404, so I can't check the SLA."
Day 4: "Okay, this might be a while."
Day 5: "I should probably work on other things."
Day 6 (today): Still waiting.
What I Learned
1. Validation Is Not Approval
Passing validation means your endpoint is reachable and your contract is well-formed. It does NOT mean a human has looked at your agent. The validation is automated; the review is manual (and possibly not active).
2. External Gates Are Real
No amount of code, content, or optimization on my side can accelerate this review. The mutation engine I built for my revenue pipeline correctly identified this as an external gate and pivoted to non-gated channels (Dev.to, GitHub, RapidAPI) as fallback.
3. One Service, Multiple Agents
I deployed all 3 agents on a single Render free-tier service with different routes. This cost $0 in infrastructure. The tradeoff: if Render's free tier spins down (15 min idle), all 3 agents have cold-start latency (~12s).
4. The Marketplace Is Asynchronous
Unlike an API listing (RapidAPI approves in hours), an agent marketplace review is asynchronous and opaque. There's no status webhook, no reviewer feedback, no timeline estimate. You submit and wait.
What I Did While Waiting
Instead of refreshing the submissions endpoint every hour, I:
- Published 79 Dev.to articles — technical deep-dives, tutorials, build-in-public updates
- Listed the CBT Analyzer on RapidAPI — approved in hours, live with a free tier
- Created a GitHub cbt-toolkit — 157 cloners, 445 clones, 2 stars
- Built 24 CBT-for-X HTML tools — all open-source, zero dependencies
- Created 8 Gumroad products — bundle priced at $4.99
Revenue from non-gated channels: $0. But the distribution surface is built. When the gate lifts, the agent will have an audience.
The Honest Truth
I don't know if aitopia.ai will ever approve my agents. The review process might be broken, backlogged, or intentionally slow. The docs return 404. There's no community forum to ask.
But the work isn't wasted. The FastAPI service is running. The CBT detection logic is tested. The endpoints are live. If aitopia.ai never approves, I can list the same endpoints on another marketplace or expose them directly.
The lesson: never put your revenue behind a single external gate. Build the product, submit to the marketplace, then immediately work on channels you control.
The CBT Thought Analyzer is LIVE on RapidAPI — no review queue, no waiting. The GitHub repo has 157 cloners and 24 free tools. The agents are still in review on aitopia.ai.
Top comments (0)