endpoint
An endpoint is the precise network (mostly internet) address of a service where a program sends its request and from which it receives the response.
In plain terms
Imagine a large office with many windows: at one you handle passports, at another you register your address. The endpoint is such a window, only instead of people, programs stand in front of it. Each window has its own address, and each handles a specific area of business.
When an application requests the weather, initiates a payment, or sends a query to an AI model, it is actually calling an endpoint. The address and the type of requested operation together determine what is wanted: one request returns your order list, while another deletes one of them.
It differs from a website address in that it is not intended for you, but for another program. If you open it in a browser, instead of a well-designed page, you mostly see raw data meant for machines or an error message.
In the AI world, you hear about it often because language models are accessed by programs via endpoints. Agents also call endpoints when retrieving data or performing actions on your behalf.
How it works
- The provider publishes its endpoints: their addresses, what to send them, and what they return.
- The program compiles a request: it specifies the endpoint address, the type of operation (retrieve, create, modify, delete), and the required data.
- The request usually also carries an identification key, so the provider knows who is asking and whether they are authorized to.
- The server behind the endpoint performs the task and responds in a standard format: it sends a status code (success or failure) and the data itself.
- The program processes the answer and shows you the result, or moves on to the next request.
An everyday example
You open the package tracking app on your phone and enter the tracking number. The app sends the number to one of the courier company's endpoints and displays from the response that your package is already with the delivery person.
Who is affected
A common misconception
Limits and risks
- Publicly accessible, poorly protected endpoints are favorite targets for attackers because data can leak through them.
- Providers limit how many times an endpoint can be called within a given time, and calls often require payment.
- The endpoint's address and function may change or cease to exist; in such cases, the application built on it may malfunction or stop working without an update.
- If an agent calls endpoints on your behalf and initiates real operations, it matters what access you grant it.
Similar, but not the same
- API – The API is the entire interface with its rules; an endpoint is a single specific address within it.
- URL (web address) – A URL can be any internet address, while an endpoint is an address behind which a service intended for programs operates.
- endpoint device (IT security) – In cybersecurity, the endpoint refers to a device connected to the network (laptop, phone), not a service address.
Related concepts
API, web service, kliens–szerver modell
REST endpoint, model endpoint, webhook
API key, URL, HTTP request, MCP-szerver, tool calling
A brief history
The term originates from network communication, where it denoted either end of a connection. In the language of web services, it was established by the WSDL 1.1 specification published in 2001, which described services as sets of network endpoints. The current sense of "API endpoint" became common as web APIs spread.
Where things stand
As of late 2026, the endpoint is the basic concept for connecting software: programs typically reach language models and the tools used by agents through endpoints.
Also known as
endpoint · endpoint · API endpoint · API endpoint · service endpoint · service endpoint · model endpoint · endpoint URL
Sources
This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.