Endpoint is a specific URL where software receives requests. When you call an API, you are calling one of its endpoints. When you deploy an AI model on a cloud platform, the platform gives you an endpoint URL where your applications can send data and get predictions back. Each endpoint typically does one job: create a contact, search records, generate a response, classify an image.
Key Takeaways
- An endpoint is one specific URL where a piece of software accepts requests. An API has many endpoints, each doing one job.
- AI model endpoints are how hosted models get called. Whether you are using OpenAI, Anthropic, AWS SageMaker, Google Vertex AI, or Hugging Face, you call an endpoint and get a response.
- For most SMBs, endpoints are invisible. The software you use is calling them behind the scenes. They become visible only when you build custom integrations or deploy custom models.
- Endpoint security is a different topic. In that context, an endpoint is a device on a network (laptop, phone, server), and endpoint security tools (CrowdStrike, SentinelOne, Microsoft Defender) protect those devices.
- Watch for rate limits, authentication, and version changes when working with endpoints. The three most common causes of integrations breaking unexpectedly.
In Simple Terms
Think of an API as the front desk of a hotel. The whole desk exists to handle requests, but different requests go to different people: one person for check-in, one for billing, one for room service. Each of those people is an endpoint. They have their own job, their own form to fill in, their own response.
In software, an endpoint is the specific URL you call to get one specific thing done. The HubSpot CRM has hundreds of endpoints. One creates a contact. One searches deals. One sends a marketing email. The same broad "API" gives you access to all of them.
In AI specifically, an endpoint is where you send data to get a prediction or a generated response back. OpenAI's chat endpoint accepts a conversation and returns the model's next message. Amazon SageMaker lets you deploy your own trained model and gives you an endpoint URL for it. The mechanics are the same as any other API endpoint. The work it does is AI.
The Three Meanings of "Endpoint"
API endpoint
A URL within an API that performs one specific function. The most common meaning in the AI and automation context. When you connect Stripe to your CRM, the connection works by calling Stripe's endpoints (create payment, fetch customer, refund charge) from the CRM.
AI model endpoint
A specialised API endpoint that wraps a deployed AI model. Sends data in, gets prediction or generation out. OpenAI's chat completions endpoint, Anthropic's messages endpoint, your custom SageMaker model endpoint, a Replicate or Hugging Face hosted model URL. All examples.
Endpoint device (security context)
A computing device on a network: a laptop, phone, tablet, server, IoT device. Endpoint security software (CrowdStrike Falcon, SentinelOne, Microsoft Defender for Endpoint) protects these devices from malware, ransomware, and unauthorised access. Same word, completely separate field.
When Endpoints Matter for an SMB
For most SMBs, endpoints are background mechanics. You buy a tool, you flip an integration on in settings, and the underlying endpoint calls happen invisibly.
Endpoints become a topic when you are building. If you are wiring up a custom workflow in n8n, Make, or Zapier, each step is essentially an endpoint call from one tool to another. If you are commissioning a custom AI agent, the agent is calling AI model endpoints (probably OpenAI or Anthropic) along with endpoints on your CRM, calendar, billing system, and so on.
The practical things to manage when you reach this point.
Rate limits. Every endpoint has a cap on how often it can be called. OpenAI imposes per-minute and per-day limits that scale with your usage tier. HubSpot limits how many endpoint calls you can make per day, per integration. Hit the limit, the endpoint returns an error until the window resets. Most SMBs are nowhere near these limits, but it is the first thing to check when an integration starts failing.
Authentication. Every endpoint that touches sensitive data needs an API key, OAuth token, or similar. Treating these like passwords (not committed to code repositories, not shared in plain text, rotated periodically) is the security baseline.
Version changes. Providers release v2, v3, v4 of their APIs and eventually retire older versions. An integration built against an old endpoint will start failing the day the provider turns it off. Subscribing to your AI and SaaS vendors' developer changelogs is the cheapest defence.
Frequently Asked Questions
What is the difference between an API and an endpoint?
What is an AI model endpoint?
What does 'endpoint security' mean? Is that the same thing?
How do SMBs use AI endpoints in practice?
What should I watch for when integrating with an endpoint?
Related Glossary Terms & Resources
API
The broader interface. An endpoint is one entry point within an API.
Webhook
The reverse of an endpoint call: a service sending data to your endpoint when something happens.
Inference
What an AI model endpoint actually does when called: runs inference on the input and returns a prediction.
Integration
Connecting two systems together, almost always through endpoint calls between them.