Connectors

One library for every system you connect.

More than 1,800 systems catalogued once, shared by agents and workflows. Agents use only the connectors you tag for AI.

Connectorslibrarymore than 1,800 systems
⌕ payments
Allaivoiceon-prem
{}Core banking APIREST · bearer tokenai
$Payment providerREST · API keyai
⇄Regional payments networkregional banking and paymentsworkflows
§Tax authority e-filinggovernment and taxworkflows
The catalogue

The systems regulated work runs on.

Alongside the global platforms, the regional and public-sector systems that are hard to find elsewhere.

Regional banking and payments

Banks, payment networks and gateways that operate in specific markets.

Government and tax

Tax authorities, e-filing and public registries.

Your own APIs

Any REST or HTTP API, with a bearer token, an API key or a user name and password.

Your databases

MySQL, MariaDB, PostgreSQL, Microsoft SQL Server, Oracle and DB2.

Tagging

Agents only reach what you tag.

A connector needs the ai tag before any agent can use it. Everything else stays with your workflows.

  • Checked on every save: it must belong to your team, carry the tag and be the right kind.
  • BAA status on record for every outside provider.
  • Guarded on the way out: internal addresses refused, redirects never followed.
Agent StudioLoan deskadd a toolai-tagged only
{}
Core banking APItagged ai
$
Payment providertagged ai
DB
Ledger databasenot tagged · workflows only
§
Tax authority e-filingnot tagged · workflows only
Credentials

Secrets go in. They never come back out.

Connector credentials are write-only and encrypted with AES-GCM. Credentials only go to the connector's own hosts, over HTTPS.

ConnectorsCore banking APIcredentialsAES-GCM
•••••••••••••••• saved
Show token: secrets are write-only. Replace it, or test it.
✓Test connection: connected, written to the audit log without the secret.
Talk to our team

Bring a system you need to connect.

We will show you the connector, how it signs in and who can use it.