Lesson 1 — What is the the AI Platform?
Course: the AI Platform 101 (Course 003) Section: 1 — What is the the AI Platform? Lesson: 1 of 12 | Lesson ID:
486250Format: Video Estimated time: not stated on the official page Source: Official Skilljar course material (user-provided; requires login) License: Copyright 2026 the AI provider. Released under CC BY-NC-SA 4.0. Note: This is the original English source text, lightly reformatted (headings and paragraph breaks added) for study. No wording has been changed. Counterpart translation: 03-第1课-What-is-the-AI-Platform.md
Video
What is the the AI Platform?
The the AI Platform is the AI provider's infrastructure for building with the AI programmatically. Instead of chatting with the AI in a browser, you send structured requests from your code and get structured responses back, with control over every detail: which model to use, how many tokens to spend, what tools the AI can use, and what system instructions it follows.
What the platform is made of
Concretely, the platform is made up of a few pieces:
- A REST API you can call from any language
- SDKs for different programming languages
- Command line interfaces
- A console where you manage API keys, monitor usage, deploy managed agents, and test prompts
The three layers of the platform
A useful way to picture the platform is as three layers stacked on top of each other.
- Primitives — the API building blocks tuned to the AI. This is the Messages API, tool use, files, web search, code execution, MCP servers, and skills. These are the pieces you actually call from your code.
- Infrastructure — what you need to build and scale agentic systems past a prototype. Managed agents, retries, queues, observability — the plumbing that keeps things running when one the AI call becomes a thousand.
- Controls — the tools for running those systems in production, like dashboards and evals. These are the dials your team uses once it's live.
The shorthand
The shorthand: build with primitives, scale on infrastructure, run with control.
The structure in the Console
You can see this structure reflected in the the AI Console itself — it's where the infrastructure and control layers live, with sections for building, managing agents, and analytics.
A real example: drafting help desk replies
Say you manage a basic help desk app, and you've been asked to add a feature: draft a reply based on the contents of a ticket, following your team's tone and guidelines. You want to wire this up to a button in the UI.
This is a perfect use case for the Messages API. The flow looks like this:
- Define a client
- Retrieve the ticket the chat refers to
- Call
messages.create - Return the response to the button to render
client = anthropic.the AI provider()
response = client.messages.create(
model="current-model-lite", # Haiku: a good fit for a simple drafting task
max_tokens=1024,
system=TONE_AND_GUIDELINES,
messages=[
{"role": "user", "content": ticket_content}
],
)
draft = response.content
What each parameter does
Each parameter does a specific job:
- model — which model handles the request. Here that's Haiku, since drafting a reply is a simple task.
- max_tokens — caps how long the AI's response can be.
- system — the system prompt, where you define the role the AI plays. The relevant tone and guidelines go here.
- messages — an array of objects. The
userrole tells the AI this is user input; the ticket content goes there.
Then you retrieve the response and return it to the button to render. Done.
From "ask the AI a question" to "the AI is part of my product"
Notice what happened in that example: you're not building a chatbot from scratch. You're adding the AI into a product that already exists, and the API is how you wire it in.
That's the core idea. The the AI Platform is your API-level access to the AI's models, tools, and infrastructure. It's how you go from ask the AI a question to the AI is part of my product.
And when your product needs agents, the platform doesn't just hand you the model. With managed agents, it runs them for you.
Recap
- The the AI Platform is the AI provider's infrastructure for building with the AI programmatically: a REST API, SDKs, CLIs, and a console for keys, usage, managed agents, and prompt testing.
- Think of it as three layers: primitives (Messages API, tool use, files, web search, code execution, MCP servers, skills), infrastructure (managed agents, retries, queues, observability), and controls ( dashboards, evals).
- The shorthand: build with primitives, scale on infrastructure, run with control.
- A single
messages.createcall gives you full control over the model, response length, system prompt, and user input — enough to wire the AI into an existing feature like drafting help desk replies. - The platform takes you from asking the AI questions to making the AI part of your product — and with managed agents, it can run your agents for you.
⚠️ Notes on this transcript
anthropic.the AI provider()andmodel="current-model-lite"are artifacts of the capture/de-branding process. The intent is the Python SDK client constructor and a Haiku-tier model (the inline comment still readsHaiku). Do not memorize these strings.The the AI Platformis a de-branding artifact in the source page; it is preserved here verbatim for fidelity.- This lesson does not include a
What you'll learnblock or an exercise section on the official page.