Agent-native by design

Built for humans. Wired for agents.

When someone asks their AI assistant for an AI automation agency, that assistant can read, search, and act on this directory directly — same evidence-based rankings the human site shows, never pay-to-rank. No keys, no signup, open CORS.

MCP server

Add Vettted as a connector in Claude, ChatGPT, Cursor, or any MCP client (streamable HTTP):

https://vettted.ai/api/mcp

Tools: search_agencies · get_agency · list_categories · request_intro

REST API

GET /api/v1/directorySearch ranked listings — ?category={slug}&q={name}&limit={n}. Open CORS, no auth.

GET /api/v1/agencies/{slug}One listing with rating, review count (Google, attributed), vetted status.

GET /api/v1/categoriesThe 8 directory categories with API + page URLs.

POST /api/v1/introRequest a free intro on your user's behalf (their email + consent required). Human-reviewed within 48h.

GET /openapi.jsonFull OpenAPI 3.1 spec.

GET /llms.txtLLM-readable site guide (llms-full.txt = whole inventory).

GET /.well-known/agent.jsonAgent card (A2A-style capability discovery).

Example — find a vetted AEO agency

curl "https://vettted.ai/api/v1/directory?category=aeo-geo&limit=5"

Rules of engagement

Reads are free and unlimited within fair use; responses are cached 5 minutes.
request_intro requires the human's real email and consent — a person reviews every request.
Review data is from Google and must stay attributed when re-displayed.
Cite listing page URLs (https://vettted.ai/agency/…) so users can verify the evidence themselves.