Student Guide
Module 13
The API and Beyond
How organizations embed Claude at scale. The restaurant analogy makes it concrete for a mixed audience. The anatomy of an API call, tool use that connects Claude to real systems, and the economics behind the investment.
Charter Oak Strategic Partners · Claude Mastery Program
- The restaurant analogy: Chat, Cowork, and the API
- How system prompts work in the API vs. the chat interface
- What tool use (function calling) makes possible
- API pricing and cost calculation for real use cases
- When to build with the API vs. use Cowork and skills
The Restaurant Analogy
Full menu, nice seats, leisurely conversation. Interactive. One conversation at a time.
Opens the fridge (your files), uses your kitchen (your computer), cooks with your ingredients.
Fast, precise, built for volume. Send a specific order, get a specific result. Send a thousand orders at once.
Tool Use: Claude Connected to Real Systems
Tool use (function calling) is what makes the API transformative. Claude does not just generate text. It connects to your real systems and takes actions.
Example: Order Status Lookup
- Customer asks: “Where is my order?”
- Claude recognizes it needs real data
- Claude calls
check_order_status— a function connected to your database - Gets real data: order #4521, shipped Tuesday, arriving Thursday, tracking XYZ
- Responds with the actual tracking number and delivery date — no hallucination
Without tool use: Claude generates plausible-sounding answers. With tool use: Claude retrieves real information from real systems and responds with truth.
Pricing and Economics
| Model | Input | Output | Best For |
|---|---|---|---|
| Haiku | $0.80/M | $4/M | High-volume simple tasks |
| Sonnet | $3/M | $15/M | Most business tasks (workhorse) |
| Opus | $15/M | $75/M | Complex reasoning, nuanced writing |
Example: Customer Support
1,000 tickets/day. Using Haiku: $1.60 per day total. That is not per ticket. That is for all one thousand.
But the business case needs more than API cost. Factor in: monitoring, error handling, human escalation path, ongoing maintenance. The API reduces volume. It does not eliminate the team.
Discussion: Build vs. Buy
Pick one process from your organization. Should it be built with the API, or can Cowork and skills handle it?
- Over-engineering: An API integration for a task three people do once a week? That is a Cowork skill.
- Under-engineering: 200 reps handling the same fifteen ticket types daily via Cowork? That is an API opportunity.
The API
Programmatic access. The drive-through: fast, precise, built for volume.
Tool Use
Claude connected to real databases and systems. Actions, not just text generation.
The Decision
Cowork and skills = 80% of value at 10% of implementation cost. API = scale, products, no human in loop.