daBongo LMS AI Training Courses

← Back to Course

The Anthropic Developer Platform – From First Call to Production

Lesson 1: The Anthropic Developer Platform – Architecture and Key Concepts

Lesson Objectives

By the end of this lesson, students should be able to:

  • Describe the Anthropic API's core architecture
  • Identify the key components: models, messages API, tools, tokens
  • Distinguish between the available Claude model families and their capability tiers
  • Locate the primary developer documentation resources

Lesson Content

The Anthropic API – what it is.

The Anthropic API provides programmatic access to Claude models. Your application sends a request (typically a JSON payload with a model ID, system prompt, and user messages) and receives a response (text or structured output). The API is stateless – each request includes all the context needed to generate the response.

Core components.

Models: Anthropic offers multiple Claude models across capability tiers. As of 2026, the main families include Opus (highest capability), Sonnet (balanced), and Haiku (fastest/lowest cost). Current model IDs and capabilities are at docs.anthropic.com/en/docs/about-claude/models – always use current model IDs from the documentation rather than ones memorized from a course.

Messages API: The primary API endpoint. Accepts a structured messages array (system + user/assistant turns), model ID, and parameters. Returns a completion.

Tokens: The unit of API pricing and context length. Tokens are approximately 0.75 words in English. Both input (prompt) and output (response) tokens are counted and billed. Understanding token consumption is essential for cost management.

Tools: The mechanism for function calling – allowing Claude to request your application to run a function and return results. Covered in depth in a later course.

SDKs: Anthropic provides official Python and TypeScript/JavaScript SDKs. The SDKs wrap the HTTP API with type-safe methods, automatic retry logic, and other production conveniences. Using an SDK is recommended for most integrations.

Documentation resources.

Primary developer reference: docs.anthropic.com

  • API Reference: complete endpoint documentation
  • Model overview: current model IDs, capabilities, context windows, pricing
  • Guides: prompt engineering, tool use, production best practices
  • Anthropic Cookbook (GitHub): practical code examples

Practical Example

A web developer who has used Claude via claude.ai wants to add AI summarization to her application.

She opens docs.anthropic.com, reviews the model overview to understand the capability vs. cost trade-offs for her use case (summaries, not reasoning), selects Haiku for cost efficiency, reviews the Messages API reference, and copies the Python SDK quickstart.

Her first working API call takes forty minutes – most of which is reading documentation.

The documentation investment up-front prevents the trial-and-error debugging that would have taken longer.

Safety Notes

API keys provide programmatic access to your Anthropic account and are billed against your account for every request. Store API keys in environment variables or a secrets manager – never hardcode them in source code or commit them to version control. Treat API keys with the same security as passwords. Verify current key management best practices at docs.anthropic.com.

Log in and enroll to access lesson quizzes.

← Back to Course

Scroll to Top