LLM API
On this page
An LLM API is a hosted endpoint that accepts a prompt and returns generated text or structured output over HTTP. For agents, the more useful question is which API gives a model access to tools. MCP tools let an agent call external services through one standard interface. 0 to 29.99 is the pricing range for APIbase plans. The plan you pick depends on call volume and the number of tools your agent needs.
What an LLM API does for a developer
An LLM API takes a request containing messages, a model name, and optional parameters. The model returns a completion. Most providers expose this through a REST or streaming endpoint with an API key header.
Developers use this for chat, summarisation, classification, and code generation. The text output is the core product. Tool calling extends it. The model returns a structured request that names a function and its arguments. The application then runs that function.
Why tool access matters more than raw completions
A completion alone cannot read a calendar, query a database, or send an email. The application must wire each service by hand. Each new service adds its own auth flow, schema, and error handling.
MCP, the Model Context Protocol, defines one message format for tools and resources. The agent connects to an MCP server, lists the available tools, and calls them with JSON arguments. The same client code works across services.
The Model Context Protocol specification is published at https://modelcontextprotocol.io.
How APIbase fits into an LLM stack
APIbase is an MCP gateway. It gives an agent a single connection point to a large and growing catalog of tools from hundreds of providers across many categories. The agent calls a tool through the gateway and receives the result in the MCP response format.
The gateway handles credential routing for each provider. The developer configures one MCP client entry instead of one integration per service.
Pricing starts at 0 and reaches 29.99. The exact plan depends on usage volume.
Choosing an LLM API for an agent
Pick the model provider first. Model quality, context length, and per-token cost decide that choice. Then pick the tool layer.
- Check whether the model provider supports native tool calling or requires a wrapper.
- Count the external services the agent must reach. Few services can use direct integrations. Many services favour a gateway.
- Test latency on the tool path. Each tool call adds a network round trip.
- Review the error format. Consistent errors make retry logic simpler.
Setting up MCP tools in an agent
Add the gateway to the MCP client configuration. The client starts a session, calls the list-tools method, and receives the tool schemas. The model reads those schemas and selects a tool.
Give the agent clear tool descriptions. The model chooses tools based on those descriptions, so vague descriptions produce wrong calls. Test each tool with a sample prompt before deploying the agent.
Caveats and limits
A gateway adds one network hop to every tool call. Measure the added latency against your agent's response budget.
Tool quality varies by provider. Check each tool's output before relying on it in production. No public benchmark comparing gateway latency across all providers was found, so run your own test.
Live pricing — developer
Data source: live tool catalog snapshot, fetched 2026-11-02.
Chart data as a table
| Tool | Price per call | Cache-hit price |
|---|---|---|
| Usage Time Series | $0.0 | $0.0 |
| Per-Tool Usage Breakdown | $0.0 | $0.0 |
| Usage Summary | $0.0 | $0.0 |
| Discover Tools | $0.0 | $0.0 |
| Batch Tool Calls | $0.0 | $0.0 |
| Tool Quality Metrics | $0.0 | $0.0 |
| Tool Quality Rankings | $0.0 | $0.0 |
| List Programming Languages | $0.001 | $0.0001 |
| Check CVE ID Reservation Status | $0.001 | $0.0001 |
| Security Advisories (deps.dev) | $0.001 | $0.0001 |
| Dependency Tree (deps.dev) | $0.001 | $0.0001 |
| Package Info (deps.dev) | $0.001 | $0.0001 |
| Tool | Provider | Price/call | Cache-hit |
|---|---|---|---|
| Usage Time Series | account | $0 | $0 |
| Per-Tool Usage Breakdown | account | $0 | $0 |
| Usage Summary | account | $0 | $0 |
| Discover Tools | apibase | $0 | $0 |
| Batch Tool Calls | platform | $0 | $0 |
| Tool Quality Metrics | platform | $0 | $0 |
| Tool Quality Rankings | platform | $0 | $0 |
| List Programming Languages | judge0 | $0.001 | $0.0001 |
| Check CVE ID Reservation Status | cve-mitre | $0.001 | $0.0001 |
| Security Advisories (deps.dev) | depsdev | $0.001 | $0.0001 |
| Dependency Tree (deps.dev) | depsdev | $0.001 | $0.0001 |
| Package Info (deps.dev) | depsdev | $0.001 | $0.0001 |
Connect via MCP
Data source: gateway design, no measured values.
$ curl -X POST https://apibase.pro/api/v1/tools/account.timeseries/call \
-H "Content-Type: application/json" -d '{"params": {}}'FAQ
What is an LLM API?
An LLM API is a hosted endpoint that accepts a prompt and returns a model-generated completion over HTTP. Many also support tool calling, where the model returns a structured function request.
What are MCP tools for LLM API workflows?
MCP tools are services exposed through the Model Context Protocol. An agent lists them and calls them with JSON arguments, using one client interface for every service.
How much does APIbase cost?
APIbase pricing ranges from 0 to 29.99. The plan that fits depends on how many tool calls your agent makes.
Do I need a gateway if I call one API?
No. A single direct integration is simpler. A gateway helps when the agent must reach many services with one client configuration.
Recommended next step
- STEP 1/2 Connect your MCP client
- STEP 2/2 Browse the full catalog
Related guides
Published: 2026-11-02Source: live apibase.pro catalog snapshot