Skip to main content

Reference Index

The map to Anthropic's published material for builders. Every entry links to the original, which is always the authority.

Hand-drawn line illustration in warm terracotta and cream: a hand tips one cream book out of a neat shelf row of book spines, considered by an abstract one-line face.


How this index works

Anthropic's builder material lives on five separate surfaces that do not cross-reference each other in any organized way. This page lists what exists and where, so you can go to the primary source.

Entries are summarized in one line and linked. Nothing is reproduced here. Where a date is known it is given, because in this field a post from eighteen months ago and a post from last month can describe genuinely different APIs.

The five surfaces

SurfaceScaleWhat it actually holds
anthropic.com/engineering~25 postsThe deep technical canon. Small, dense, high signal.
claude.com/blog~193 postsThe primary developer stream. Largest and least discovered. Older anthropic.com/news developer URLs now redirect here.
platform.claude.com/docs~541 pagesMessages API, Managed Agents, prompting and evaluation guidance.
code.claude.com/docs~171 pagesA separate domain. The entire Agent SDK reference lives here.
Code with Claude sessions and talks~140 sessions, ~79 videosConference material, much of it with recordings.
Anthropic Academy~21 coursesStructured courses.

Start here: the load-bearing posts

If you read nothing else, read these. Each is linked to the original.

For founders specifically

Cost and unit economics

The highest-ROI reading in the whole corpus for anyone running a real bill.

Agent architecture and coordination

Tools, MCP, and skills

Security and containment

Runnable code

Where the gaps are

Worth knowing what is not well covered, so you stop searching for it: unit economics of an agent product beyond token pricing, multi-tenant SaaS architecture, reliability engineering against the API (retries, idempotency, circuit breakers, SLOs), model portability, evals as an operational asset at scale, regulated-industry engineering patterns, and latency engineering. Anthropic also rarely publishes the case for not building an agent at all.

Further Reading