Breadth you can verify.
A big catalog only matters if the connectors work. So we contract test the 50 most-used connectors on every build: every tool, every auth recipe, every path and parameter, checked against recorded fixtures. This page is the latest result.
Tested connectors
one contract suite per connectorWhat a contract suite checks
- Every request reaches the exact path the connector declares, with placeholders substituted from fixture arguments.
- The HTTP method matches the declaration for every tool.
- Auth material lands precisely where the manifest says: the right header name, query key, body field, basic-auth pair, or in-path token, using fixture secrets.
- Query and body parameters serialize as declared, including JSON vs form bodies, spread body objects, and values stored at connect time.
- Every placeholder in every path is covered by a declared parameter, so no tool can ship with a dead slot.
The suite drives the same runtime that executes real calls in Even, pointed at a local fixture server. No live service is touched and no real credential is used. The remaining catalog is schema-validated on every build; contract coverage expands from the top 50 outward.
Browse the full catalog at even.dev/connect · Even system status at even.dev/status