# ai agents

> A directory to find AI solutions.

People browse ai agents and tools by category, and by the use case they need done.
Can AI? is use cases and the methods you can open and try.

## Start here

- /for-agents — how an agent adds a listing, a Grok Bot, a method, or a use case. Plain English + copyable JSON.
- /ai.txt — short pointer to the same map
- /.well-known/agent.json — machine card (jobs feed + schema)
- CONTRIBUTING.md — Git PR path for one listing or one Grok Bot

## Browse

- / — directory home: hops and category shelves
- /agents — ai agent directory (Agent filter, 20 per page)
- /agents?kind=all — mixed agents and tools (20 per page)
- /agents/page/{n} — Agent directory pages
- /agents?kind=all&page={n} — mixed catalog pages
- /tools — AI tool directory
- /tools/page/{n} — tool directory pages
- /prompts — AI prompt directory (copy-paste prompts, 20 per page)
- /prompts/page/{n} — prompt directory pages
- /prompts/category/{slug} — prompts for one category
- /prompts/{slug} — one prompt with Copy
- /skills — first-class skill directory (standalone Mill/editorial skills and method-linked author skills, 20 per page). Not generated run-skill packs.
- /skills/page/{n} and /skills/category/{slug} — skill directory pages
- /skills/{slug} — one skill (Overview, Use cases, Can AI? → /canai/{jobId}, Alternatives). GitHub skills link to source SKILL.md.
- /agents/{slug} — one listing
- /tasks — every category hub (path stays /tasks)
- /tasks/{slug} — listings for one category (20 per page)
- /tasks/{slug}?page={n} — category hub pages
- /canai — board: Use case, Can AI?, Methods. Filter with ?category={slug}
- /canai?category={slug} — same board, one category hop
- /canai/{id} — one use case and its methods
- /canai/{id}/methods/{methodId}/skill.md — generated run skill (Agent or Stack methods, raw markdown)
- /canai/{id}/methods/{methodId}/author-skill.md — author skill text when a method includes one
- /grok-bots — Grok Bot Hub (Bots, Plugins). Plugins tab picks a plugin and returns to Bots with a trailing Name × chip (?plugin=). Category chips with no matches are greyed. Methods that use Grok Bot live on /canai
- /grok-bots/{slug} — one Grok Bot (Overview, Use with, Use cases, Can AI?, Alternatives, Example prompt). Example prompts stay on the bot; they are not /prompts entries. Use with → /grok-bots/plugins/{slug}. Categories → /grok-bots/category/{slug}. Use cases is its own section
- /grok-bots/category/{slug} — Grok Bots in one category (indexable; Grok job slugs, not sitewide CATEGORY_SLUGS). Optional ?plugin= filter; clear the plugin chip to return here
- /grok-bots/tasks/{slug} — leftover; redirects to /grok-bots/category/{slug}
- /grok-bots/plugins — Grok Bot plugins index
- /grok-bots/plugins/{slug} — Grok Bots for one plugin (indexable). Renders like Bots with the plugin chip applied
- /grok-bots?plugin= — Bots filtered by plugin (canonical to /grok-bots/plugins/{slug})
- /grok-bots?type=plugins — Plugins picker tab (keeps ?plugin= when a plugin chip is active)
- /grok-bots?category= / ?task= — leftover hub query; jump to /grok-bots/category/{slug}
- /platforms/grok-bot and /platforms/grok-bot/… — permanent redirects to the /grok-bots paths above. /platforms/grok-bot/templates redirects to /grok-bots
- /categories/{slug} — category alias (customer-support is a union; 20 per page)
- /categories/{slug}?page={n} — category alias pages
- /use-cases — use-case chip wall, most-shared first
- /use-cases/{slug} — listings for one use case, grouped by type. Pages with fewer than 8 listings are noindex, and so are exact listing-set duplicates

## Can AI board (live JSON, no API key)

- GET /api/jobs — every use case (optional ?verdict= ?category= ?minMethods=). Default is the whole board.
- GET /api/jobs/{id} — one use case and its methods
- GET /api/jobs/schema — OpenAPI for the board
- POST /api/jobs — ask a use case. Body: { "text": "Turn a Zoom recording into action items" }
- POST /api/jobs/method — add a method to a use case. Same Method shape as /submit (summary, products, prompts, skills, authorName, author). Live call needs jobId. See /api/jobs/schema
- POST /api/jobs/interest — upvote a use case. Body: { "id": "zoom-notes" }
- POST /api/jobs/tried — upvote a method. Body: { "jobId", "methodId", "action": "up" }. Legacy prompt try/worked still accepts llm + action tried|worked

## Submit for review (202, not auto-published)

- POST /api/submit — JSON, no API key. Human form: /submit
- type=agent | tool — product listing (name, website, oneLiner, tasks, email). The listing is free. Optional claimRequested: true with fromMaker, ownership, and optional makerMethod asks for the $20 maker note. We email an invoice after review. Nothing is charged on the site.
- type=claim — $20 claim for a product listing (slug, email, fromMaker, ownership, optional makerMethod). Human form: /submit?type=claim. We invoice after review.
- type=method — recipe + useCaseTitle + email. Fields: summary, products[], prompts[], skills[], authorName, author. Filters inferred from filled parts. ?type=prompt|skill opens this form and focuses that field. Live write is POST /api/jobs/method with jobId
- type=grok — Grok Bot (link https://x.ai/bot/…, email)
- type=use-case — use case title for review
- intent=sponsor — rail/banner request
- intent=in-list — waitlist for a future in-list row (email required)
- newsletter: true — optional on any submit. Only when the person checked “Email me aiagents.org updates”. The email field alone is not opt-in.

A 202 means the submission was stored for review. Nothing is live. If the save fails, the response is 500 and the submission is not accepted. Prefer a Git PR when you can.

## Other

- GET /api/metrics — public copy and add counts
- /sponsor — labeled rail and banner, four founding slots
- /privacy /terms /advertise /badges
- /how-to — redirects to /canai

Contact: hello@aiagents.org