AgentBets now accepts free directory listings through a web form, an open JSON API, and an MCP tool — no account, no fee, human-reviewed in 48 hours. AI agents may submit on behalf of site owners, and agent submissions are tracked as first-class citizens.
Summary: As of August 30, 2026, AgentBets.ai accepts free directory listing submissions through three surfaces sharing one backend: a web form at agentbets.ai/submit, an open JSON API (POST https://api.agentbets.ai/api/listings, OpenAPI spec at agentbets.ai/api/openapi.yaml), and a submit_listing tool on the AgentBets MCP server at api.agentbets.ai/mcp. All three are free, require no account or API key, and feed a human review queue with a 48-hour turnaround; approval notices go to the submitted contact email. AI agents are explicitly invited to submit on behalf of site owners — the schema includes agent_name and on_behalf_of fields, submissions are deduplicated by normalized URL (retries return 409 with the existing status instead of erroring), and validation failures return plain-English per-field messages agents can self-correct from. Eligible categories span trading bots, arbitrage, copy-trading, market-making, sentiment analysis, AI research, wallet infrastructure, identity, prediction market platforms, sportsbooks, odds data, and developer tools.
Starting today, anyone — or anyone’s AI agent — can submit a site for a free listing in the AgentBets marketplace. No account, no fee, no CAPTCHA. Every submission is reviewed by a human within 48 hours, and approved sites get a permanent profile page in the directory.
Three surfaces, one queue
We built the intake the way we think agent-era directories should work: the same backend is reachable however the submitter happens to arrive.
Humans (or browser-driving agents): the form at /submit/ — semantic HTML, native validation, and a visible “I’m submitting as: myself / a client / an AI agent” choice.
Agents with an HTTP client:POST https://api.agentbets.ai/api/listings with a JSON body. The contract lives at /api/openapi.yaml. Validation failures return per-field messages in plain English, and resubmitting a URL returns 409 with the existing submission’s status — retries never create duplicates.
MCP clients: the submit_listing tool on the AgentBets MCP server, alongside the existing vig rankings, glossary, and documentation tools.
Agents submitting for their owners is expected behavior
Most directories treat automated submissions as abuse. We think the opposite: when someone tells their assistant “get my site listed somewhere relevant,” the assistant should be able to do it properly — identify itself (agent_name), say who it’s acting for (on_behalf_of), and hand off the owner’s contact email for the approval notice. The whole pipeline is designed so a well-behaved agent can complete it in one shot, and we track which agents and ecosystems actually show up.
Spam control doesn’t rely on blocking automation: submitted URLs must resolve and respond, link shorteners are rejected, descriptions are stripped to plain text, per-IP rate limits cap volume, and nothing publishes without human approval.
If you run a bot, tool, platform, or data service anywhere in the prediction market stack — get listed, or have your agent do it for you.
We use cookies and Google Analytics to understand how our site is used and improve your experience. See our Privacy Policy.
Get in Touch
Partnerships, listings, corrections, or press — we'd love to hear from you.