LOCKEDIN / FORWARD-DEPLOYED ENGINEERING 101
Understand it.
Then build it.
You can be an experienced engineer and still be new to agents. Start with what each thing is and how it helps a person do useful work. Explore 48 original introductions across software, agents, cloud, security and delivery. Start here without a model key; each topic connects to deeper instruction and practice.
- 101UnderstandPlain language, visual walkthrough, vocabulary
- 102Build with guidanceOriginal lessons, examples and knowledge checks
- 103Practise and explainRunnable labs, failure cases and handover
Model family, coding tool and service interface
Claude, Claude Code and the Claude API
Anthropic develops the Claude model family. Claude Code is an agentic coding tool. The Claude API is an interface developers use to integrate model capabilities into their own applications. An SDK helps call that API. These names describe different layers, not interchangeable products.
FDEs both use AI to engineer software and engineer software that uses AI. The access and operating responsibilities differ.
UNDERSTAND THE SYSTEM
Claude is the model; your application runs the tools
Anthropic provides Claude models and developer interfaces. Calling the Claude API is different from using the Claude chat product or Claude Code to develop software.
Read the connections in plain English
- 01Your application → API client or SDK
Choose a supported model and bounded request settings.
- 02API client or SDK → Claude model
The provider processes the supplied messages and tool definitions.
- 03Claude model → Your tool executor
A model-generated tool request is not business authorization.
- 04Your tool executor → Tool result
The application performs the permitted work and records its outcome.
- 05Tool result → Your application
Provide the result for the next model call or stop the task.
Check your understanding: Does an API request turn your application into Claude Code?
No. Claude Code is a development product. A Claude API integration is part of an application you build and operate, with its own tools and access controls.
CONNECT IT TO WHAT YOU KNOW
Start with something familiar.
Distinguish an engine, a finished vehicle and an interface for incorporating the engine into your own design. Using a coding assistant does not automatically add AI to your deployed product.
The account, permissions and billing for a development tool and an application API may differ. Verify the intended product and deployment route instead of assuming a subscription covers every use.
Words worth knowing
- Model family
- A group of related trained models.
- Coding agent
- A tool that can help perform software-development tasks.
- API client
- Application code that calls a service interface.
ONE EXAMPLE / FICTIONAL CASE
Follow the connections.
You use Claude Code to implement a maintenance service; that service independently calls a model endpoint at runtime.
UNDERSTAND THE SYSTEM
Claude is the model; your application runs the tools
Anthropic provides Claude models and developer interfaces. Calling the Claude API is different from using the Claude chat product or Claude Code to develop software.
See what moves and why.
Read the connections in plain English
- 01Your application → API client or SDK
Choose a supported model and bounded request settings.
- 02API client or SDK → Claude model
The provider processes the supplied messages and tool definitions.
- 03Claude model → Your tool executor
A model-generated tool request is not business authorization.
- 04Your tool executor → Tool result
The application performs the permitted work and records its outcome.
- 05Tool result → Your application
Provide the result for the next model call or stop the task.
Check your understanding: Does an API request turn your application into Claude Code?
No. Claude Code is a development product. A Claude API integration is part of an application you build and operate, with its own tools and access controls.
FROM RECOGNITION TO REASONING
Draw development-time and runtime AI on separate diagrams.
- 01
Place Claude Code beside the repository in the first diagram.
- 02
Place the application and model endpoint in the second.
- 03
Identify which credentials and permissions belong to each.
Two diagrams that do not share accidental authority.
Compare your reasoning when you are ready
A developer tool may edit code, while the runtime application may read approved business data. Neither should inherit the other's broad permissions merely because both use Claude.
Keep notes in your own working copy. Moving through these cards does not record completion.
TURN THE IDEA INTO USEFUL WORK
You can now go deeper.
The account, permissions and billing for a development tool and an application API may differ. Verify the intended product and deployment route instead of assuming a subscription covers every use.
Academy lessons use your existing training access. Free guides stay open.
Learn with the original creators
Follow the provider's API instruction after distinguishing the model, SDK and application here.