Listing a connector's tools and calling one through Well means a single connection reaches whatever else your workspace has attached. That is powerful and it widens the blast radius: a permission audit here has to cover what the connectors can do, not just what Well can. On the finance side, the discovery-first pattern is the right habit — schema, then query — and runway and cash position are the two questions people actually open a finance tool to answer, so having them as direct tools rather than reports is well judged. Idempotency keys on every write are the detail that shows this was built for agents.
Well is a financial platform covering invoices, the companies and people behind them, and the position they add up to. Its endpoint answered an anonymous handshake, though the tools themselves need authorisation.
- Discovery-first querying — get the schema, then query records, or read one entity with its sub-resources in a single call
- Records — create, update and soft-delete companies, people and invoices; add and remove contact channels
- Finance — cash position, runway, cost structure, investment holdings, periods and counterparties
- Reconciliation — register differences, gaps and reconciliation tasks, plus listing missing invoices
- Connectors — list what a connected provider can do, and invoke one of its tools on your behalf
- Workspaces — list what the token can reach, and switch between them
OAuth or an API key from their dashboard. Their suggested first question is simply asking to see your invoices. Payments and accounts are documented as still to come.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen