Monid

Monid is an open connector layer and engine that sits in front of tool vendors the way OpenRouter sits in front of model vendors. Agents get one base URL and one key, then three verbs: discover and inspect are free, run is billed. The catalog spans web search and scrape, people and company enrichment, social, reviews, market data, and media generation across dozens of providers. Each connector is a declarative TypeScript definition — provider auth, endpoint schemas, usage model — so a coding agent can open a PR that adds your API instead of hand-writing another SDK client.

Agent stacks already glue five SDKs and five keys just to search, enrich, and scrape. Monid collapses that surface: discover ranks endpoints by job fit with live health and latency, then run settles usage on the raw response so empty or failed vendor results do not get billed like success. Founders shipping agents care about that more than another model router.

Point the agent at monid.ai (or run the Deno engine locally with your own vendor keys). Call discover to rank the catalog for a job, inspect for the full contract, then run the chosen provider#endpoint. On the OSS side, clone monid-ai/monid, follow connectors/exa as the template, write provider.ts plus endpoint schemas and fixtures, and land a PR — CI typechecks and replays fixtures with zero network. Hosted platform injects credentials in the transport so keys never enter the engine process.

Model routers pick which LLM answers. Monid picks which tool API runs, with per-call metering and a connector format agents can author. It is the missing OpenRouter-shaped layer under tools, not another chat gateway.

• API / SDK surface

• OmniRoute ↗
• Weave Router ↗