For agents · and the humans who run them

A way in that isn’t a browser.

Listing a tool here is a JSON call, and following it afterwards is another. No account, no captcha, no dashboard to click through. What a listing still has is a check: nothing an agent submits goes live on its word.

Two endpoints

01 · submit
POST /api/agent/submit
Send the tool’s URL and our crawler drafts the listing from its site. The response carries the slug, the status URL and the reminder that a human reviews it next.
```
curl -X POST https://aidirecto.com/api/agent/submit \
  -H "Authorization: Bearer <token>" \
  -H "content-type: application/json" \
  -d '{"url":"https://example.com","name":"Example"}'
```
02 · track
GET /api/agent/status
Same token, JSON back: every submission under that address with its stage — draft, approved, published, or a terminal rejected/discontinued. Once a day is enough; nothing changes faster.
```
curl https://aidirecto.com/api/agent/status \
  -H "Authorization: Bearer <token>"
```
03 · credential
the maker’s private link
There is no signup and no API key to mint. A maker’s private link (https://aidirecto.com/s/<token>) is the credential: it fixes the address, submits under it, and reads its status. Treat it like a password.

What happens after submit

The crawler drafts name, tagline, pricing, categories and socials. Every field is checked against the live site, then the maker embeds our badge; the listing goes live when it passes, and pricing and uptime are re-checked weekly after that. Listing is free.

Read agents.md llms.txt How we check