Glossary
What is an API?
In short
An API (application programming interface) is a set of rules by which one program sends requests to another and gets an answer, for example from an AI model in the cloud.
Infrastructure · application programming interface
MMOOZZGG.com editorsChecked: 2 min read
For a child
Picture the serving window in the school cafeteria. You do not go into the kitchen and cook yourself: you say what you want at the window and get a plate. The cooks work inside, and the window has clear rules: ask the right way, get your lunch. Programs have similar windows. One program asks politely, and the other does the work and hands back the result.
In plain words
When an app uses an AI model, it usually does not keep the model itself. It sends text over the internet to the server of the company that runs the model and gets an answer. The rules of this exchange are called an API: where to send the request, in what form, with which access key and what comes back. For example, a chatbot on a store’s website takes a shopper’s question, passes it to the model and shows the answer in the chat window. The store did not train the model or buy servers for it.
For business
This connection lets you build AI into your own systems without your own servers: into a CRM, a website or a phone system. You usually pay for input and output tokens, so the bill grows with the length of documents and the number of requests. The upsides: a fast start, access to strong models and no hardware costs. The risks: customer data goes to the provider’s servers, sometimes abroad, and the provider may change prices or terms, or retire the model. Before you connect, check where the data is processed, what the contract says about using it for training, and whether you can switch to another model without rework. Compare the prices of different providers on one date and in one currency.
For a specialist
An application programming interface is a contract between programs: a set of operations, data formats and authentication rules. Language model interfaces are usually built on HTTP in the REST style (Representational State Transfer), which Fielding described in his 2000 dissertation. The client sends a POST request with JSON (messages and generation settings such as temperature and max tokens), and the server returns the answer whole or as a stream through server-sent events. Access is protected by a key or OAuth, and load is capped by limits on requests and tokens per minute (rate limits). The OpenAPI Specification, a standard, language-independent interface to HTTP services, describes such a contract in machine-readable form. Local engines copy the format of popular cloud services: the llama.cpp server offers OpenAI-compatible routes for chat and embeddings, so client code moves between the cloud and your own server almost unchanged. Tool calls by the model are built on top of this through function calling and MCP.
Example
A sales team wants calls to turn into short notes in the CRM by themselves. A developer links the phone system and the CRM with a model: the call recording goes to speech recognition, the text goes to the model, and the finished summary returns to the deal card.
Related terms
Questions and answers
Sources
Not sure whether your company needs this?
AI solutions map