Atlas · building
APIs and HTTP
How one program asks another for something over the web. Every agent talks to its model this way.
See it working: Plate VI
In plain words
An API is a door one program opens for another. Most of them speak HTTP, the same language your browser uses: one side sends a request, the other sends back a response.
How it works
MDN describes HTTP as a client opening a connection, sending a request and waiting for the server’s response. It was designed for browsers and web servers, and is also used for machine-to-machine communication and programmatic access to APIs. MDN says a beginner can treat a “REST API” as an HTTP service that standard web libraries and tools can call.
Going deeper
An agent is a client of this kind. Claude’s API answers at api.anthropic.com; a local Ollama server answers at localhost on port 11434. Plate VI follows one request out and back.
Sources
- HTTP: Hypertext Transfer Protocol MDN
It was designed for communication between web browsers and web servers, but it can also be used for other purposes, such as machine-to-machine communication, programmatic access to APIs, and more.
HTTP follows a classical client-server model, with a client opening a connection to make a request, then waiting until it receives a response from the server.
- REST MDN
HTTP APIs in general are sometimes colloquially referred to as RESTful APIs, RESTful services, or REST services, although they don't necessarily adhere to all REST constraints.
Beginners can assume a REST API means an HTTP service that can be called using standard web libraries and tools.
- API overview Anthropic
The Claude API is a RESTful API at https://api.anthropic.com that provides programmatic access to Claude models and Claude Managed Agents.
- Introduction Ollama
http://localhost:11434/api
Cloud requests need an API key. Local requests do not.
Quotes were checked against the live pages on 2026-11-12.