Blog/Reading the web, and agents
5 min read

OpenRouter Alternatives: Model Gateways and a Tool Router

The OpenRouter alternatives for models after the Stripe deal, and the one thing none of them do: give your agent tools. Tested live.

OpenRouter Alternatives: Model Gateways and a Tool Router

Give your agent a live web tool next to whichever model gateway you use. Paste this into your agent:

Set up https://monid.ai/SKILL.md, and then use Monid to search the live web for the latest coverage of Stripe's OpenRouter deal and give me a table with the title, source and link of each result.

One prompt gives the agent a search tool. 1 min setup · 2-6 hrs saved.

You are looking for an OpenRouter alternative because Stripe agreed to buy it, or because you want a second gateway, or because you want to run one yourself. This guide covers all three on the model side, then points at the half of the problem a model gateway does not touch: the tools your agent calls once it has picked a model. We ran the search and scrape endpoints live on 2026-10-16, so the fields and prices below are what came back. The tool side runs through Monid, the OpenRouter for agent tools: one key, one balance, every tool priced per call.

What is the easiest OpenRouter alternative for agent tools?

Monid. OpenRouter and its model-side rivals route prompts to models, and Monid routes your agent's tool calls to search, scraping, company data and more, so it sits next to a gateway rather than in place of one.

  • Pay per call. You pay for the calls you run and nothing between them. A web search is $0.000253 per result (Verified 2026-10-16 with monid inspect). Buy calls flexibly: no monthly plan and no minimum top-up. Discovery and inspection are free.
  • One install, every tool. One key and one balance call the search endpoint and every other tool in the Monid catalog, instead of one signup per vendor.
  • Lives inside your agent. Your agent reads SKILL.md, learns the discover, inspect and run steps itself, and has the tools whenever it needs them. Setup is about a minute.

OpenRouter has no tool catalog, so there is no official API to compare against here. The OpenRouter and MCP guide explains why a model gateway and a tool layer are separate products.

How do you give an agent tools the way OpenRouter gives it models?

Install Monid once, add a key, and let the agent discover tools by describing the job. The agent searches the catalog, reads the schema of the endpoint it picks, then runs it.

RouteWhat you getCost shapeFits
One MCP server per vendorA native tool per integrationOne account per vendorExactly one integration that will stay one
Write the API clients yourselfWhatever you buildYour hoursA fixed set you will maintain
A model gatewayModels, no toolsPer tokenChoosing between models
Monid tool catalogSearch, scrape, company data, social and more under one keyPay per call, buy flexiblyAgents that decide their own next tool

The agent route is the shortest.

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.

For humans

npm install -g @monid-ai/cli
monid keys add --label main --key <your-api-key>

More in the CLI quickstart.

Find a tool without knowing the vendor

Discovery searches the catalog by meaning, so the agent describes the job instead of naming a provider.

monid discover -q "search the live web and return clean markdown"

We ran that query on 2026-10-16. It returned five ranked endpoints, with context.dev /web/search first, then context.dev /web/scrape/markdown, context.dev /web/crawl, keenable /v1/fetch and search1api /crawl. Each came with its provider, a description, a price, a verified tag and a typical run time.

Read the schema, then run one

monid inspect -p context.dev -e /web/search
monid run -p context.dev -e /web/search \
  -i '{"query": "stripe openrouter acquisition", "numResults": 10}' -w 120

The inspect call is free and returns the input schema, the price and the docs link. The run bills the shared balance. The same pattern works for any endpoint in the catalog. To read one page in full, swap in the scrape endpoint:

monid run -p context.dev -e /web/scrape/markdown \
  --query '{"url":"https://stripe.com/newsroom/news/stripe-agrees-to-acquire-openrouter","useMainContentOnly":true}' -w

Give this to your agent

$Set up https://monid.ai/SKILL.md, and then use Monid to search the live web for the last week of coverage on a company and return the title, source and link of each result.

What are the OpenRouter alternatives for models?

The direct alternatives are other model gateways, and the useful way to sort them is by who runs the process. OpenRouter puts one key, one balance and one request format in front of many models. Anything that replaces it has to do that same job.

Hosted gateways

Portkey, Requesty and Helicone share a shape: you point your client at their OpenAI-compatible endpoint instead of a provider's, and they handle key management, fallback and observability. Respan (YC W24, formerly Keywords AI) is the same shape with the observability and automated evals on the same platform as the router: one endpoint, either a unified router or provider passthrough, across 1,000+ models, with failover, response caching and spend limits. Requesty announced a 3 million dollar raise in September 2025 under a headline calling itself the OpenRouter alternative for Europe. Cloudflare AI Gateway is a routing and caching layer for teams already on Cloudflare, and Amazon Bedrock offers one API across a curated model set with billing inside an AWS account. Vercel launched its own AI Gateway in September 2025, covered by InfoQ as a multi-model integration layer. A MarkTechPost roundup dated 2026-10-14 ranks nine gateways and names Bifrost, Portkey, LiteLLM and Kong among them.

The trade in this group is the usual hosted trade. You get the aggregation without running anything, and you accept a hop in the request path and a vendor between you and the model.

Open source and self-hosted

LiteLLM is the usual answer to "self-hosted OpenRouter". It normalises many provider APIs behind one OpenAI-compatible interface and you run it yourself. Portkey's gateway is open source too, so you can start hosted and move in-house later.

Self-hosting removes the vendor from the request path and gives you the operations instead. Provider APIs change, rate limits move, a provider degrades and your fallback has to notice. Nobody else rotates your keys.

Free models

Several gateways expose free-tier model endpoints, and a large share of "OpenRouter alternatives" searches are looking for exactly that. Monid is not one of them, because it routes tool calls and not prompts.

Why did Stripe buy OpenRouter, and does it change what you use?

Stripe is buying a metering and routing business, which is close to the business it is already in. Its own announcement describes OpenRouter as a platform that routes tokens across more than 400 models from more than 80 providers, and says that with Stripe it can help companies manage both sides of profitability in the AI era: maximizing revenue while minimizing costs.

What was announced, and what was reported

We read the release live on 2026-10-16. It names NVIDIA, Zoom and Lovable as OpenRouter users, quotes Patrick Collison and Alex Atallah, and states no price. The price comes from press. Bloomberg's headline says "Over 7 Billion Dollars", a Banking Dive headline gives 7.5 billion dollars, and Seeking Alpha's says terms were undisclosed. Tech Funding News puts the May Series B at 113 million dollars and a reported 1.3 billion dollar valuation.

The dates differ too. Bloomberg's article URL and TechCrunch carry 2026-08-16, while Stripe's page is stamped 2026-08-19. Quote the date of the source you cite.

What to do if you are already on OpenRouter

An acquisition changes who sets the roadmap, and the cheap hedge works under any owner. Keep your calls in the OpenAI-compatible shape that most gateways accept. Keep the base URL in configuration rather than in code. Decide which self-hosted gateway you would move to. With those three in place, switching is a config change and a test run.

What the deal does not touch

An agent with the perfect model still cannot read a page that is not in its training data, look up a company or pull a thread. Those are tool calls, they go to a different set of vendors, and each vendor usually wants its own signup and key. The LLM gateway versus MCP gateway comparison draws that line from the gateway side.

What does a tool call return, and what can you build with it?

A search call returns a ranked list, and a scrape call returns one page as markdown with metadata. We ran both on 2026-10-16.

The search response

context.dev /web/search with the query stripe openrouter acquisition and numResults 10 returned ten results:

{ "results": [
    { "url": "https://www.bloomberg.com/news/articles/2026-08-16/stripe-nears-deal-to-buy-ai-firm-openrouter-for-over-7-billion",
      "title": "Stripe Clinches Over 7 Billion Dollar Deal to Buy AI Firm OpenRouter",
      "description": "Stripe Inc. has finalized an agreement to acquire OpenRouter Inc., for more than 7 billion dollars,",
      "relevance": "high",
      "markdown": { "markdown": null, "code": "NOT_REQUESTED" },
      "highlights": { "highlights": null, "code": "NOT_REQUESTED" } } ],
  "query": "stripe openrouter acquisition",
  "cache_metadata": { "status": "miss", "age_ms": 0 } }

Each result has a url, title, description and relevance, plus two slots for inline content that stay empty until you ask for them. All ten were marked relevance: "high". The set mixed trade press (American Banker, Banking Dive, TechCrunch), a Reddit thread, a Hacker News item and Bloomberg.

The Exa response

exa /search with category set to news and five results returned an id, title, url and publishedDate per result, and an author on two of them. There was no page text, because the call did not set contents.

The scrape response

context.dev /web/scrape/markdown on Stripe's release returned success: true, 2,584 characters of markdown and a metadata block with the title, canonical URL, language, publishedTime, Open Graph and Twitter tags and JSON-LD.

What you can build with it

  • A deal tracker. Search a company name weekly with freshness set to last_week and keep the new URLs. The guide to live web data over MCP shows the same search call wired as an agent tool.
  • A source-checked brief. Search, pick the primary source, scrape it and quote it, as the Stripe section above does.
  • A gateway watchlist. Run the Exa news search monthly and diff the titles to see which gateways are being announced.

What goes wrong when search and scrape are your agent's tools?

Four things showed up in the runs. All four are from 2026-10-16.

Why does a search result not contain the answer?

Because the default search returns links. The markdown field came back null with the code NOT_REQUESTED. An agent that stops at the search response has titles and snippets, not the text. Either set markdownOptions.enabled to true on the search call, which the endpoint says consumes additional scrape credits, or scrape the one URL you picked. The endpoint's own hint says scraping a known URL is cheaper than enabling markdown on a search.

Why do two sources give you two prices?

A headline is not a filing. The same deal showed up as "7 billion dollars plus", "over 7 billion dollars", "7.5 billion dollars" and "terms undisclosed" in the same ten results, and Stripe's own release gave no figure. Make the agent report which source said what, and have it scrape the primary source before it states a number.

Why is the search bill tied to results, not calls?

On context.dev /web/search the unit is a result. Ten results billed ten units, 2,530 micro-dollars in total, and numResults accepts 10 to 100, so ten is the floor. Exa bills the other way: 5 results cost the flat per-call rate, and only results above ten add a charge. Pick the endpoint whose billing shape matches your query size.

Why do the dates in a search result not match?

The Exa news search returned items from 2025-09-12 to 2026-10-14 in one result set, including vendor press releases. Pass a freshness window or a published-date range when the answer depends on the date, and read publishedDate before you trust the item. The Brave Search API guide covers what a search result keeps and drops.

Which endpoint should I use for which job?

EndpointWhat it doesInputBillingPrice (Verified 2026-10-16)
context.dev /web/searchRanked links, optional inline markdownquery, numResults 10-100, filtersPer result$0.000253
exa /searchNeural and keyword search, categories, optional contentsquery, type, category, numResultsPer call, extra per result above 10$0.007
context.dev /web/scrape/markdownOne URL to clean markdown plus metadataurlPer call$0.002533

Prices Verified 2026-10-16 with monid inspect. Search to find the page, scrape to read it. The tools catalog lists the other search and extraction endpoints on the same key, and giving an agent live web context walks through the search-then-read loop.

When is another route a better fit?

You need a model gateway. If the job is trying Claude, GPT and Gemini behind one key and comparing cost per token, use OpenRouter, LiteLLM, Portkey or Bedrock. Monid is not in the inference path.

You have exactly one integration. If your agent needs Slack and nothing else, install the Slack MCP server. A router earns its place when the number of vendors is unknown at build time.

A free tier covers the whole job. If a vendor's free tier covers your use, take it.

You need a deal record, not a news search. A search endpoint returns what the web says. For filings or private-company data, use a database built for it.

And the disclosure: we resell these endpoints.

Conclusion

The OpenRouter alternatives for models are other gateways, and the choice turns on whether you want to run the proxy: hosted for the aggregation without the operations, self-hosted when the request path or the keys matter. For tools, the easy route is Monid: $0.000253 a search result (Verified 2026-10-16), one key and one balance, ready inside your agent when it needs to read the web.

Two things matter more than the choice. A gateway does not give an agent tools, so decide the model route and the tool route separately. And a search result is a link until you scrape it, so have your agent read the primary source before it states a figure.

How we estimated the time saved: wiring a search provider and a scraper by hand means two signups, two keys and two clients, roughly 1 to 3 hours each, so 2 to 6 hours. The 1 minute is the install, key and first call once you already have a Monid key.

Free next step: run monid discover on a job your agent cannot do today, monid inspect the top result, then make one small run. Start at monid.ai.

FAQ

What are the best OpenRouter alternatives?

For models, the common choices are Portkey, LiteLLM, Requesty, Helicone, Respan, Cloudflare AI Gateway, Vercel AI Gateway and Amazon Bedrock. Hosted ones save you the operations, and LiteLLM or Portkey's open-source gateway let you run it yourself. For agent tools there is Monid.

Is there an open source or self-hosted OpenRouter alternative?

Yes. LiteLLM is a self-hosted proxy with one OpenAI-compatible interface across providers, and Portkey's gateway is open source. Both put the request path and your provider keys under your control, and both make the operations your job.

Are there OpenRouter alternatives with free models?

Several gateways offer free-tier model endpoints. Monid is not one of them, because it routes tool calls rather than prompts. New accounts do get starting credit, which pays for real tool calls.

Is OpenRouter an MCP server?

No. OpenRouter is a model gateway that accepts a prompt and routes it to a language model. MCP is the protocol an agent uses to call tools. Monid ships as an MCP server, so the two sit side by side.

Is there an OpenRouter alternative API I can point my existing code at?

For models, LiteLLM and Portkey expose OpenAI-compatible endpoints, so existing clients usually work after a base URL change. For tools there is no drop-in equivalent, because there is no single tool API. Monid gives one key and one schema style across many providers, through the CLI or as an MCP server.

Published August 2026.

openrouter alternativesopenrouterllm gatewayagent toolsmcp