Build on Anthropic

Anthropic's guidance for builders is excellent and scattered across five separate surfaces with no unified index. This is the index.

---

The problem this solves

If you are a founder deciding whether and how to build your product on Claude, the material you need already exists. Finding it is the hard part, because it is spread across five places that do not link to each other in any organized way:

Surface	Roughly how much	What most people assume
anthropic.com/engineering	25 posts	That this is the canon. It is the smallest slice.
claude.com/blog	193 posts	Largely undiscovered. This is the actual primary developer stream.
platform.claude.com/docs	541 pages	Reference, not narrative.
code.claude.com/docs	171 pages	A separate domain. The entire Agent SDK lives here.
Conference sessions and talks	~140 sessions, 79 videos	Rarely surfaced at all.
Anthropic Academy	21 courses	Rarely surfaced at all.

A reader who finds only the engineering blog misses roughly 85 percent of it.

The same is true of the proof. claude.com/customers publishes 256 customer stories, and its own index page lazy-loads a fraction of them at a time. Roughly 95 more customer stories live entirely outside that index, scattered through news posts, blog posts, and conference sessions.

How to use this wiki

Start with the question you actually have.

• "Has anyone like me built this already?" Go to Case Studies. 256 stories, cut by company stage, industry, use-case pattern, and how hard the published evidence is. The Index lists every story in one searchable table. If you are early, start with the startup cut.
• "What has Anthropic actually published?" Go to the Reference Index, the dated master list of every source, organized by surface.
• "What should I build, concretely?" Go to The Tools: paste one file into Claude and get a personalized architecture read on your own product, ending in a build brief. Operators can mint custom editions for their own audience.

Every page here is a routing layer first. It summarizes, then points you at the original. The originals are always linked and always the authority.

For agents and LLMs

This wiki ships machine-readable versions of itself, and they are meant to be used:

• /llms.txt is the index: every page, one line each, with URLs.
• /llms-full.txt is the entire wiki as one plain-text file, including The Index's full 256-row case-study table.

Point a coding agent, a research assistant, or a build brief at either file and it can read everything here without scraping. Both regenerate on every deploy, so they are always current.

How claims are handled

This wiki is source-grounded. That means:

• Every claim names its source in the sentence.
• Every number is the figure the company or Anthropic published, quoted briefly and linked to the page it came from.
• Where a published source contradicts itself, that is flagged rather than smoothed over.
• Nothing here is reproduced wholesale. This is a map to the material, not a copy of it.

If a number matters to a decision you are making, click through and read the original.

Independent, not affiliated

This wiki is an independent reference maintained by Gary Sheng. It is not affiliated with, endorsed by, or an official publication of Anthropic. Anthropic's own documentation is the authority on every technical detail. Where this wiki and Anthropic's documentation disagree, Anthropic is right and this is out of date.

Changelog

• Updated 2026-07-22 (Concept) Consumption Pricing: The Claude Developer Platform bills by tokens consumed, not seats sold. A builder's bill scales with how much their product actually runs, which aligns the platform with usage that works.
• Updated 2026-07-22 (Concept) Memory Stores: Workspace-scoped persistent memory for Managed Agents: a filesystem mounted into every session, versioned, with an audit trail, so what an agent learns survives the run.
• Updated 2026-07-22 (Concept) Outcomes: The Managed Agents primitive for defining done: you supply a rubric, and the platform runs an iterate, grade, revise loop with a separate grader until the work passes.
• Updated 2026-07-22 (Concept) Scheduled Deployments: Cron for agents on Managed Agents: a schedule fires a fresh session on the clock, every firing leaves a run record, and the whole thing can be paused or archived.
• Updated 2026-07-22 (Concept) Self-Correction Mid-Task: An agent that checks its own output against reality before handing it over, and fixes what it finds: validate in a sandbox, look at the rendered result, retry on failure.
• Updated 2026-07-22 (Concept) The Audit Trail: Citation to source as a product feature: every answer carries a pointer to the exact place it came from, so the human verifies instead of hunts.
• Updated 2026-07-22 (Concept) The Batch API: 50 percent off input and output tokens for anything that can wait up to 24 hours. The discount stacks with prompt caching.
• Updated 2026-07-22 (Concept) The Effort Dial and Model Splitting: Spend frontier-model tokens on judgment and small-model tokens on commodity steps, and turn the effort parameter down where deep thinking is wasted.

For the full month-by-month log of every change, see the Wiki Changelog.