Eligibility: the exam is limited to people at Claude Partner Network organizations. Register via the Anthropic Partner Academy and sit it with Pearson VUE
Proficiency in Python or TypeScript, plus comfort with REST, JSON, async code and git
A Claude API key with a small credit balance for the labs
Weeks 1–2 · 13 h
Claude API mechanics and application design (a third of the exam)
Call the Messages API with system prompts, multi-turn history, streaming, image input and extended thinking, and read usage and stop_reason from the response
Choose real-time vs Message Batches for a workload, and know Claude is also reachable through Amazon Bedrock and Google Cloud Vertex AI
Manage configuration with CLAUDE.md, settings.json, pinned model versions and versioned prompts
Apply software-engineering basics the blueprint tests directly, including REST error handling, async concurrency, code review and safe refactoring
Hands-on: Build a small CLI that summarises PDFs and images with streaming output. Add retry with backoff on 429/529 errors, pin the model version in config, then run the same 20 files through the Message Batches API and compare cost.
Decide workflow vs agent, and build an agent with the Claude Agent SDK including subagents and hooks for deterministic actions
Know where third-party frameworks (Strands, LangGraph, PydanticAI) fit, and self-hosted vs Anthropic-hosted agent deployment
Write tool schemas and descriptions, handle tool errors, and distinguish client-side from server-side tools and approval patterns
Build an MCP server exposing tools, resources and prompts over stdio, and choose built-in tools vs custom tools vs Skills vs MCP for a use case
Hands-on: Wrap a public REST API (e.g. a weather or GitHub API) as an MCP server with two tools and one resource. Connect it to an Agent SDK agent and add a hook that blocks any tool call containing a delete verb.
Prompts, context, security, Claude Code and debugging
Use system vs user placement, few-shot examples and output constraints, and prevent context drift with tool-output pruning and compaction
Treat retrieved and user content as untrusted, keep it apart from instructions, and use hooks or least privilege so prompt injection can't trigger sensitive actions
Keep API keys in a secrets manager or environment variables and scope them per environment
Know Claude Code components (rules, skills, commands, agents, memory), headless mode and settings.json, and isolate whether a bug sits in the integration layer or the model output
Start with the provider's official exam guide and free training, then use practice exams to find your weak domains. We never link to exam dumps, which break exam agreements and can get you decertified.