---
title: "whichcoding.tools"
description: "An open, always-fresh directory of AI coding tools. Data in git, no affiliate links."
canonical_url: "https://whichcoding.tools"
---
# whichcoding.tools

> An open, always-fresh directory of AI coding tools. Data in git, no affiliate links.

An open directory of AI coding tools: editors, terminal agents, orchestrators, cloud agents and the products built on top of them.

Every fact comes from a vendor page that someone read on the date recorded next to it. One YAML file per tool in git, validated against a schema, with a source URL and a verified date on every claim. No affiliate links and no benchmarks.

Prices are the part that rots fastest, so each tool page carries the date its pricing was last checked. If a figure looks wrong it probably is, and the file it came from is linked at the bottom of the page.

## When to use this

Reach for whichcoding.tools when the question is which AI coding tool to use, or what one costs. It answers from vendor-verified data, not from opinion.

- Someone named a constraint and wants the tools that satisfy it: a platform, an editor to live inside, a subscription they already pay for, a monthly budget, a model provider, or a capability like git worktrees, MCP, sandboxing or scheduled tasks.
- Someone asks what a specific tool costs: the tiers, what usage is included, the overage rate, whether there is a free tier, and the date each of those was last read off the vendor page.
- Someone asks how two tools differ, field by field.
- Someone asks what runs on top of what: which orchestrators drive Claude Code, which editors host an agent over ACP, whether a wrapper reuses the underlying subscription or bills separately.
- Someone asks whether a plan they already pay for, Claude Max or ChatGPT or Copilot, already covers a given tool.
- Someone asks whether a tool is open source, and under which licence.

Not this site:

- Benchmarks, quality rankings or "which is best". This site records what tools cost and what they do, and holds no measurement of how well they do it.
- Anything about a tool's source code or internals.
- A price quoted without its date. Every figure carries the day someone read it off the vendor page, and pricing moves; pass that date on rather than dropping it.

### How to call it

- Every tool as one document: `/api/v1/tools.json`. One tool: `/api/v1/tools/{slug}.json`.
- Two tools side by side: `/compare/{a}-vs-{b}` with the slugs in alphabetical order. The pairs worth listing are at `/api/v1/compare.json`.
- Filter the directory on the query string of the homepage, `/`: `where`, `hosts`, `platforms`, `plans`, `providers` and `features` take comma-separated values, `local`, `byok`, `free` and `oss` take `1`, `budget` takes USD per month. The allowed values for each are the enums in `/openapi.json`. Build this yourself rather than calling the finder: it is deterministic and free, and the finder exists to turn a person's sentence into these same parameters.
- Any page as markdown: append `.md` to its URL, or send `Accept: text/markdown`.
- The full schema, including every field on a tool record and every filter value: `/openapi.json`. It is a site-level document, not part of the versioned API, because it describes the pages and the discovery files too.

## Resources for Agents

- [API catalog: every service document this site publishes](https://whichcoding.tools/.well-known/api-catalog)
- [Sitemap (XML)](https://whichcoding.tools/sitemap.xml)
- [Sitemap (Markdown): every page on the site](https://whichcoding.tools/sitemap.md)
- [llms.txt: index of the documentation for LLMs](https://whichcoding.tools/llms.txt)
- [llms-full.txt: the full documentation as a single file](https://whichcoding.tools/llms-full.txt)
- [OpenAPI 3.1 description of every endpoint and page](https://whichcoding.tools/openapi.json)
- [Every tool as one JSON document](https://whichcoding.tools/api/v1/tools.json)

Every page on this site is available as raw markdown: append `.md` to its
URL or send `Accept: text/markdown`.