Nimbleway/webrouter

WebRouter is an open source standard that connects your agent to the web

What it solves

Agents often need to search the web, read pages, get quick answers, run deep research, or drive a browser — but each provider has its own API, authentication, and response format. WebRouter solves this by offering one typed interface that connects to many web backends, so you write one call and can switch providers without changing your code. It also avoids vendor lock-in, since your keys remain yours and the library is open source (Apache 2.0).

How it works

WebRouter exposes core methods — search, extract, answer, research, live data, and browser sessions — that accept a provider argument (or use a default auto mode). Each provider is mapped to a set of capabilities; for example, brave searches but cannot extract, while nimble covers search, extract, live data, and research. The library routes each request to a provider that supports the requested method and options, and it can fall back to a ranked order of providers you have keys for, then to keyless ones. Responses keep a consistent shape across providers, and the response.provider field tells you which backend actually served the call. It also includes governance features: you control provider selection, keys stay scoped, unsupported constraints are rejected, and vendor writes require explicit opt-in.

Who it’s for

Developers building AI agents or LLM-based applications that need web access — whether they are prototyping with no API key, using a single provider, or managing multiple vendor accounts. It suits those who want a standard, maintainable way to fetch, extract, and research from the web without rewriting integration code when switching providers.

Highlights

  • One interface, many providers — a single call shape for search, extract, answer, research, live data, and browser sessions across dozens of backends.
  • Smart routing — static fallback and optional routers trade off cost, latency, and coverage based on the task and available keys.
  • No vendor lock-in — Apache 2.0 license, runs with your own keys, and switching providers is just changing one argument.
  • Governance and security — provider selection control, key scoping, rejection of unsupported constraints, and explicit opt-in for vendor writes.
  • Keyless quickstart — you can make a search immediately with no API key, then add providers as needed.

Related

  • Project
  • Project
  • Project
  • Project