Tool Catalog
A tool is any HTTP API an agent reaches through the gateway. Pick from the curated connector library (base URL + auth pre-filled) or add any HTTP API as a custom tool. Each one is gated, and its key stays in Regent’s vault.
A tool is callable only when it has both a catalog entry (routing, added below) and a
vaulted key (the secret, connected by a human at /connect/gateway). Matched by name.
How to add a tool
- Dashboard → Connect → Set up Cloud Gateway → Add a tool → pick a connector (or Custom API) → Add. Then Connect a key and paste the secret.
- Over MCP →
add_gateway_tool { "name": "slack", "base_url": "https://slack.com/api" }(Admin MCP), then a human vaults the key.
Money tools bind a mandate (mandate_id) so their spend is enforced; everything is still
subject to your Cedar policy.
Built-in
| Tool | Use case |
|---|---|
pay (custody) | Pay from the agent’s Custodian wallet — on-chain, KMS co-signed by Regent, checked against the mandate. “Pay this supplier 5 USDC.” Blocked over-limit or by policy before any signing. |
Payments
| Tool | Use case |
|---|---|
| Stripe | Agent pays an invoice or issues a refund — capped by a $X/tx mandate; over-limit charges are denied, every charge is anchored with its decision id. |
| Modern Treasury | Initiate an ACH / bank payment — spend-limited + audited; escalate large transfers to a human. |
| Bank Core (generic) | Your internal bank-core API — instance-specific host; the credential is vaulted, egress is locked to it. |
Comms
| Tool | Use case |
|---|---|
| Slack | Agent posts a status to #ops — Cedar can restrict which channels; rate limits stop a loop from flooding. |
| Twilio | Send an SMS/voice alert — rate-limited so a hijacked agent can’t blast messages; token never leaves the vault. |
| SendGrid | Transactional email — gated + audited; policy can require an approved template. |
| AgentMail | Give the agent its own inbox (send + receive) — policy allowlists recipient domains, rate-limits sends, and audits every message. |
CRM & Sales
| Tool | Use case |
|---|---|
| Salesforce | Read/write contacts, opportunities, cases — object-level policy: “deny delete on Contact.” |
| HubSpot | Log an activity or update a deal — the OAuth token is vaulted; the agent only gets scoped writes. |
Compliance
| Tool | Use case |
|---|---|
| Chainalysis | Screen a wallet/address for sanctions before a payout — the result is a verified fact your policy can key on. |
| Persona · Onfido | Run identity verification — every check is audited; keys never touch the agent. |
Data
| Tool | Use case |
|---|---|
| Supabase (PostgREST) | Query/write your DB over HTTP — table-level control via policy; instance host is per-tenant. |
| Hasura | GraphQL over Postgres — the admin secret is vaulted; the agent can only run allowed operations. |
Docs & Storage
| Tool | Use case |
|---|---|
| DocuSign | Send a document for signature — scoped, audited; escalate high-value envelopes. |
| Box · Google Drive | Fetch or store a file — scoped access, credential vaulted, responses can be redacted before the agent sees them. |
Dev & Workflow
| Tool | Use case |
|---|---|
| GitHub | Open an issue or a PR — the token never touches the agent; policy can restrict repos. |
| Linear · Notion | Create issues / update docs — scoped writes, full audit trail. |
AI providers
| Tool | Use case |
|---|---|
| OpenAI · Anthropic | Call an LLM with a vaulted key — rate-limited, and the key can’t leak through the agent. |
Observability
| Tool | Use case |
|---|---|
| Datadog | Push a metric or query monitors — read-only can be enforced; API key stays vaulted. |
Custom tools
Any HTTP API works: give it a base URL and a bearer token. Use a bare base URL
(https://api.example.com, not .../v1) — the agent supplies the path. Add it as Custom API
in the dashboard or via add_gateway_tool.
The tool name in the catalog and the vaulted-key name must match exactly. Add the tool first, then connect its key.