Connections Overview

Proxy requests to third-party services through agntdata using your own vendor credentials.

What are connections?

Connections let you proxy API requests to third-party services through agntdata using your own credentials with each vendor. Store your vendor API keys (or OAuth installs) securely in agntdata and call them with a single agntdata API key — without exposing vendor credentials in your client applications.

Connections are billed by the vendor (you pay the vendor directly). For curated data sources where agntdata pays the vendor and bills you in credits, see Data APIs.

How connections work

1. Configure a connection

   Add your third-party API key (or complete the OAuth flow) for the vendor from the agntdata dashboard.

2. Make requests

   Call the connection endpoint with your agntdata API key. agntdata proxies the request to the third-party service using your stored credentials.

3. Get the response

   agntdata returns the third-party service response with a consistent envelope.

OAuth-first

For vendors that support OAuth (Google Docs, Google Sheets, Slack, Stripe, Linear, Cal.com, Supabase, Dub), agntdata prefers an OAuth install over a pasted API key. If both exist on a connection, the OAuth credential is used — and most paste-key paths are disabled in the dashboard for OAuth-capable providers. This avoids the “I pasted a key but my OAuth is also connected” footgun.

API endpoint

Make requests to third-party services through:

GET/POST/PUT/DELETE https://api.agntdata.dev/v1/connections/:vendor/*

agntdata forwards the wildcard path and query parameters to the third-party service.

Example

# Request through agntdata
curl -X GET "https://api.agntdata.dev/v1/connections/instantly/campaigns" \
  -H "Authorization: Bearer YOUR_AGNTDATA_API_KEY"

# Equivalent direct request (requires your Instantly API key)
curl -X GET "https://api.instantly.ai/api/v2/campaigns" \
  -H "Authorization: Bearer YOUR_INSTANTLY_API_KEY"

Response format

Successful responses include the proxied data:

{
  "success": true,
  "data": {
    // Response from third-party service
  },
  "meta": {
    "vendor": "instantly",
    "cached": false,
    "latencyMs": 245
  }
}

As MCP tools

Every connection automatically becomes a family of MCP tools (connection_<vendor>_<operationId>) on any deployed agent that has the connection enabled in its config. The Builder surfaces these under list_workspace_integrations. You don’t have to pick them per-operation — installing the connection enables the whole family.

Benefits

Secure credential storage

Vendor API keys are encrypted at rest. OAuth tokens are refreshed automatically; your client never sees the bot or access token.

Unified authentication

One agntdata API key authenticates every vendor proxy. Your app handles one key, not N vendor secrets.

Consistent error handling

agntdata normalizes errors into the same envelope shape as the rest of the API.

Agent-ready

Connections are automatically available to any deployed agent that needs them — no separate wiring.

Available connections

Documented in detail:

Stripe

Payments, customers, subscriptions, invoices, checkout.

Linear

Native MCP + GraphQL. Issues, projects, cycles, teams.

Cal.com

Bookings, event types, schedules, availability (v2).

Supabase

Your own Supabase organization — projects, SQL, edge functions, branches.

Dub

Short links, analytics, attribution.

Slack

Native bot — chat, channels, escalations.

Exa

Neural search.

Also available in the dashboard

Other providers ship with proxy support but don’t have a dedicated page yet — find them in the dashboard at Connections → Add connection:

• Google Docs and Google Sheets (OAuth)
• Attio (CRM)
• AgentMail (transactional email)
• HeyReach (LinkedIn outreach)
• Instantly (email outreach)
• PostHog (product analytics)
• SocialScraper (additional social data)
• X (official API) — distinct from the unified X data API; useful when you need posting/write scopes.
• memelord — image generation utility.

Next steps

Configuring connections

The step-by-step setup guide for OAuth and BYOK.

Tools

How connections appear as agent tools.