AI Agent Tools: Add a Tool Layer to Your Model Gateway
A model gateway gives your agent a brain, not hands. Add agent tools next to AIHubMix: discover, inspect, run, then hand the result back to the model.

Give your agent a tool it can discover, price and call on its own. Paste this into your agent:
Set up https://monid.ai/SKILL.md, and then use Monid to look up aihubmix.com and stripe.com, and give me a table with each company's name, headcount, location and funding raised.
One prompt gives the agent tools. 1 min setup · 6-12 hrs saved.
You connected a model gateway, changed one base_url, and now any model answers your agent. Then you asked it what a company charges today, or how many people work there, and it declined or made something up. A better model ID does not fix that, because the missing piece is tools, not intelligence. This guide shows how to add the tool half, what came back when we ran it on 2026-10-16, and where each half stops. It runs through Monid, the OpenRouter for agent tools: one key, one balance, every tool priced per call. You are on the Monid blog and Monid sells the tool layer. AIHubMix is a content partner and the model-side example. It is not in the Monid catalogue, and what we say about it comes from its public site.
What is the easiest way to give an AI agent tools?
Monid. Install it once, add a key, and your agent searches a catalogue of tools in plain language, reads the schema and the price, then calls the one it picked, with no vendor signup in between.
- Pay per call. Each run is billed on its own. Discovery and inspection are free, and only a run costs anything. A company lookup on the Hunter endpoint is $0.0049 per call (Verified 2026-10-16 on the AI tools page). Buy calls as you need them: no monthly plan and no minimum top-up.
- One install, every tool. The same key and the same balance reach search, enrichment, scraping and media endpoints. A second capability is another call, not another vendor account.
- Lives inside your agent. Your agent reads
SKILL.mdand learns the discover, inspect, run workflow itself, so setup is about a minute and nothing keeps running between jobs.
Why can your agent still not do anything once the model is wired?
Because a model integration and a tool integration are different things, and usually only one of them is done. A model gateway chooses which brain answers. It does not give that brain a way to look anything up.
Most advice on AI agent tools starts with a list of tools to hand the agent at build time. That list fails in two ways. The agent can only use what you predicted it would need, and each tool on it is a separate vendor with its own signup, key and invoice, so the second capability costs as much work as the first. The workaround of describing tools in the system prompt fails more quietly: the model writes a call against a schema it half remembers, the provider answers with an error or accepts a wrong field, and the agent reports the job as done. A schema has to be read when the agent runs, not remembered from training.
Both layers solve the same problem one level apart, which is why they fit in one table.
| Model layer | Tool layer | |
|---|---|---|
| The question it answers | Which model should answer this | Which API should be called |
| Integration | One endpoint, change base_url | One key, or one line for an agent |
| Choice happens | When the request is made | When the agent runs |
| Choosing costs | Nothing you need to budget for | Free: discover and inspect are not billed |
| What is billed | The completion | The call, or the result |
| Example | AIHubMix, an OpenAI-compatible model gateway | Monid, the tool layer for AI agents |
Read the middle row. Both layers move a decision from your build time to the moment the agent runs. An agent that picks its model per request and its tool per task is a different program from one that was handed both. If you want the difference between a gateway of models and a gateway of tools in more depth, LLM gateway versus MCP gateway draws the line.
How do you connect the model side with AIHubMix?
Point the SDK you already use at the gateway, add your key and pick a model ID. AIHubMix keeps the OpenAI calling pattern, so the change is the base_url and the key:
from openai import OpenAI
client = OpenAI(
api_key="<your-aihubmix-key>",
base_url="https://aihubmix.com/v1",
)
response = client.chat.completions.create(
model="<model-id>",
messages=[{"role": "user", "content": "..."}],
)
We are not going to re-document someone else's product, and their developer docs cover the model half in more depth than this article will. What matters here is the shape: a model call needs a key and a model name, and nothing else. Hunter's public company record for aihubmix.com, which we pulled on 2026-10-16, describes it as a platform that gives access to multiple large language models through one interface, which is the arrangement you just configured.
Note what has and has not happened. Your agent can now think with whichever model you name. It still cannot look anything up.
How do you give your agent tools, and what comes back?
Install the CLI or give your agent one line, then let it discover, inspect and run. Everything before the run is free.
For agents
Grab an API key at app.monid.ai, then paste this to your agent and hand it the key:
set up https://monid.ai/SKILL.md
It learns the whole discover, inspect, run workflow itself. More in the agent quickstart. There is also a remote MCP server if your runtime speaks MCP.
For humans
npm install -g @monid-ai/cli
monid keys add -k <your-api-key> -l main
More in the CLI quickstart.
Step one: find a tool nobody told the agent about
monid discover -q "company profile and funding by domain"
On 2026-10-16 this returned eight ranked endpoints from four providers, each with a provider slug, an endpoint path, a one-line description, a price and a status. Nobody had to know in advance which provider covers company data. The rows are written for a reader that is not a person: the slug and path are what the next command needs, and the billing shape (per call or per result) is visible before anything runs.
Step two: read the contract
monid inspect -p pdl -e /v5/company/enrich
This returns the input schema, the price and the docs. On People Data Labs it showed a POST endpoint billed at $0.10 per call (Verified 2026-10-16), which is why the agent reads this step before it commits. We inspected this one and did not run it. The cheaper Hunter endpoint covers the same job here.
Step three: call it
monid run -p pdl -e /v5/company/enrich \
-i '{"website": "aihubmix.com"}'
A POST endpoint takes its fields with -i. The Hunter endpoint is a GET, so it takes --query. We ran that one twice:
monid run -p hunterio -e /companies/find --query '{"domain":"aihubmix.com"}'
monid run -p hunterio -e /companies/find --query '{"domain":"stripe.com"}'
For aihubmix.com the record came back with a name, a description, a location in Dover, Delaware, an employee range of 1-10 with employeesCount 3, five detected technologies, an empty fundingRounds array and a null raised. For stripe.com it came back with a founding year of 2010, an employee range of 10K-50K with employeesCount 16597, raised of 7708000000 and six funding rounds. Each call billed $0.0049 (Verified 2026-10-16), $0.0098 for the two.
Step four: hand the result to the model
The tool returned facts, not prose. The completion goes back through the gateway and becomes the brief you asked for. In code, the two halves meet in a dozen lines, and the tool result is just context:
from openai import OpenAI
client = OpenAI(
api_key="<your-aihubmix-key>",
base_url="https://aihubmix.com/v1",
)
# `facts` is the JSON your agent got back from the Monid run above
brief = client.chat.completions.create(
model="<model-id>",
messages=[
{"role": "system", "content": "Write a two sentence brief. Cite only what is in the data."},
{"role": "user", "content": str(facts)},
],
)
Four steps, two vendors, and nobody hard-coded which provider answered. If web context is your specific job, which MCP server gives an agent live web data compares the vendor and catalogue routes for it.
Give this to your agent![]()
Set up https://monid.ai/SKILL.md, and then use Monid to find company data for a domain and write a one paragraph brief.What goes wrong when an agent calls tools?
Four things showed up in the two Hunter records, and they are the same four an agent meets with any enrichment tool.
Why does an empty field not mean no?
Because the record only holds what the provider had on its index date. The aihubmix.com record had an empty fundingRounds array, a null raised and a null foundedYear. That is a statement about the record, not about the company. Tell the model to report "not in the data" for nulls, which is the reason the system prompt above says to cite only what is in the data.
Why is a funding round not always complete?
On stripe.com every funding round had an empty investors array, one round had an amount of just "$", and a Seed round dated 2023-07-01 followed a Series I dated 2023-04-15. The rounds are usable as a trail, but an agent that sums the amount fields will get a wrong total. Use raised when you want the headline number and the rounds when you want the dates.
Why is the response bigger than the question?
The stripe.com record carried a long list of site email addresses and a long list of detected technologies, when the question was headcount and funding. Every token of that goes through the model on the next step. Pick the few fields you need before you pass facts to the completion, not after.
How old is the data?
Each record has an indexedAt date: 2026-10-11 for aihubmix.com and 2026-06-18 for stripe.com. The second is about four months old on the day we ran it. For a headcount that is fine. For a number the agent will quote as current, pass the date along with it.
What does a list cost?
Each call is one billed unit. A hundred domains at $0.0049 is $0.49 (Verified 2026-10-16), and the same hundred on the $0.10 endpoint would be $10.00. A domain the provider does not know answers 404 and costs nothing, according to monid inspect. The model bill and the tool bill answer different questions: one says how much the agent thought, the other says how much it went and found out. Current prices are on monid.ai/tools. Funding data bought by the call against a seat is its own trade-off, and Crunchbase Pro versus the API by the call works through when each wins.
Which endpoint should I use for which job?
| Endpoint | What it does | Input | Billing | Price (Verified 2026-10-16) |
|---|---|---|---|---|
hunterio/companies/find | Profile from a domain: industry, size, location, tech, funding rounds | domain (required) | Per call, a 404 is free | $0.0049 |
pdl/v5/company/enrich | Profile from a name, website, LinkedIn URL or ticker, with a match likelihood | name, website, profile or ticker | Per call | $0.10 |
Prices Verified 2026-10-16 with monid inspect. Use the first when you have a domain and want a cheap answer. The second takes a name or a ticker when you do not have a domain, and its description promises a likelihood score on the match. Inspect it for free, then spend one call on a company you know before you commit a batch.
When is another route a better fit?
The agent only ever calls one API. A pipeline that fetches from one endpoint on a schedule should call that endpoint. A layer in front of a single known dependency buys you nothing and costs you a hop.
You have a fixed vendor requirement. If a rule says one named vendor must process the data, the choice is not the agent's to make, so a catalogue adds nothing.
Your tool use is narrow and predictable. A single-vendor MCP server is simpler to reason about, and simple is worth money in production. MCP versus API for AI agents works through that trade.
Your model workload is one prompt shape. If every request goes to one model you have already benchmarked, a gateway is solving a problem you do not have. Both layers answer variety, and neither answers a pipeline that does the same thing every time.
And the disclosure: we resell the tool endpoints in this post, and AIHubMix is a content partner. The most useful thing here is independent of both: keep the model choice and the tool choice as separate integrations, so changing one never touches the other.
Conclusion
The quickest way to give an AI agent tools is a catalogue it can search at run time, reached through Monid: $0.0049 for a company lookup (Verified 2026-10-16), one key for this and every other tool, about a minute to set up and ready inside your agent whenever it needs it. A model gateway such as AIHubMix covers the other half, and the two do not depend on each other.
Two things matter more than which tools you pick. Treat a null as "not in the data" and say so to the model. And trim the tool result before the completion, because the cost and the confusion both come from the fields you did not need.
How we estimated the time saved: wiring one vendor API by hand, with signup, key handling, reading the schema and writing the call and its error handling, is roughly 2 to 4 hours. For three capabilities that is 6 to 12 hours, and each new one adds more. The 1 minute is the install, key and first call once you already have a Monid key.
Free next step: run monid discover -q "company profile and funding by domain", then monid inspect -p hunterio -e /companies/find, then make one call on a domain you know and compare the record with what you expect. Start at monid.ai.
FAQ
What tools does an AI agent need besides a model?
A way to search tools at run time and a way to pay for one call without a contract. A model can reason about a company but cannot look it up, so the agent needs data, search or action endpoints it can discover, read the schema of and call. Monid provides that as a catalogue billed per call.
What is the difference between AI agent tools and MCP?
MCP is a protocol for exposing tools to an agent, and a tool is the thing being exposed. A vendor MCP server wraps one company's API, while a catalogue exposes many providers behind one key. Both reach the agent the same way, so the choice is about how many vendors you want to manage.
Are there free AI agent tools?
Discovery and inspection on Monid are free, and a run bills per call, for example $0.0049 for a company lookup (Verified 2026-10-16), with no monthly plan and no minimum top-up. Many open-source tools are also free to run, but you host and maintain them yourself.
Can I use AI agent tools inside n8n or a similar workflow tool?
Yes. The workflow runs the steps, the model gateway answers the reasoning step, and the tool layer answers the data step. The tool layer does not replace the automation platform, it is what the workflow calls when it needs something from outside itself.
Do I have to use AIHubMix with Monid?
No. Nothing on the tool side cares which model answered, so any gateway or provider your agent already uses leaves the tool half unchanged. This post pairs the two because they sit on opposite halves of the same problem.
Published August 2026.


