Monid

Why it's ranked here

The billing design is the argument for it. Usage is settled on the vendor's raw reply before any reshaping, so a presentation change cannot quietly alter a bill, and a vendor error finishes as data charged at zero. Credentials are added only inside the transport, and the hook that sees them is deliberately given a silent logger so it cannot leak them in a log line. The tests replay recorded responses with no network, so contributors need no vendor keys. MIT licensed.

What's good

Adding a vendor is a pull request of declarations, with a worked reference connector and a written brief meant for a coding agent. Every custom function is checked three times: when written, when compiled, and on every run, so a bad one stops the run with a contract error instead of sending a garbage request. Functions are stored once under a content hash that doubles as a tamper check. The Firecrawl connector writes down which vendor charges it does not model and why, and cross-checks its own price estimate against the vendor's reported credits on every call.

Tradeoffs

It runs only on Deno, so a Node or Python shop adopts a second runtime to contribute. The parts the pitch leads with, ranking the catalog at call time with live price, health and latency, live in the hosted product, not in this code. Running locally means holding your own key for every vendor you call. The model has grown deep: resources, rate cards, ownership checks and estimate re-runs add a lot of vocabulary before a first connector. Some vendor prices are pinned by hand, because not every vendor publishes machine-readable pricing.

How to use it well

Best for two groups: an API vendor who wants its endpoints reachable by agents through the hosted service, and an engineer who wants a reference design for metering third-party calls honestly. Start from the reference connector, record a response, trim it, and keep the offline type check and replay tests green before opening a pull request. Spend most of the effort on the endpoint's plain-language description, since agents choose endpoints by reading it. It is not an agent framework and does not decide which tool to call on your behalf.

Observed

License

MIT

Language

TypeScript

Runtime

Deno 2.x, configured as a workspace of shared packages plus the engine

Interfaces

CLI tasks for compile, run, catalog browsing, fixture recording and cost estimates; engine importable as a library

Testing approach

Replay tests against recorded fixtures with no network; live tests run only when vendor credentials are set

Credential handling

One environment variable per credential field locally; injected inside the transport on the hosted platform

Connector format

Declarative provider and endpoint definitions, compiled to JSON documents with content-hashed functions