Third-Party Integrations

Third-party integrations let you connect external vendor APIs to Agent Kit using your own API keys (BYOK). Keys are configured once per application in the dashboard, encrypted at rest, and injected into MCP tool calls at runtime — never exposed to end users or the browser.

Available integrations

Provider	MCP tools	Status
Uniswap	`uniswap_swap_quote`	Available
LiFi	`lifi_swap_quote`	Available
1inch	`oneinch_swap_quote`	Available
Jupiter	`jupiter_swap_quote`	Available
CoinGecko	`data_and_analytics`	Available
Firecrawl	`firecrawl_scrape`, `ecommerce_price_compare`	Available
Bitrefill	`bitrefill_search_products`, `bitrefill_get_product`, `bitrefill_buy_gift_card`, `bitrefill_get_invoice`	Available

Uniswap

Swap quotes and unsigned transactions on EVM chains.

LiFi

Cross-chain and same-chain routes via LiFi.

1inch

Same-chain EVM aggregator swaps via 1inch.

Jupiter

SPL token swaps on Solana mainnet and devnet.

CoinGecko

Market data, charts, and GeckoTerminal on-chain analytics.

Firecrawl

Web scraping, search, and ecommerce price comparison.

Bitrefill

Gift cards, eSIMs, and mobile refills.

Swap confirmation

User Confirm / Cancel before signing swaps in chat.

Dashboard

Open Agentic Stack → Integrations for your application.
Enable a provider (e.g. Uniswap).
Paste the vendor API key and save.

Keys are stored encrypted in agent_third_party_provider and apply to all agents under that app when the integration is enabled.

How it works

Step	Component	Responsibility
1	Dashboard	Enable integration + store API key
2	User-Service	Encrypt credentials (`THIRD_PARTY_CREDENTIALS_KEY`)
3	validation-service	Decrypt and return `thirdPartyProviders` on agent validation
4	Agent Kit MCP	Gate tools — return `UNISWAP_NOT_ENABLED` if disabled
5	Your backend	Sign and broadcast transactions with agent `accessKey`

Set the same THIRD_PARTY_CREDENTIALS_KEY on User-Service and validation-service in each environment. Rotating it without re-saving integrations will break decryption.

MCP tool gating

Third-party MCP tools are only callable when:

The integration is enabled in the dashboard for that application.
A valid API key is stored for the provider.
Agent validation succeeds (application or per-agent API key).

If gating fails, tools return structured errors such as UNISWAP_NOT_ENABLED with a message to configure Integrations.

Distinction from other keys

Secret	Purpose
Application API key (dashboard Overview)	Auth to Agent Kit REST/MCP
Agent `accessKey`	Sign on-chain txs and x402 payments
Third-party API key (Integrations)	Call vendor APIs (Uniswap, etc.) on your behalf

See Credentials for the full cheat sheet.

Deployment checklist

Service	Required for integrations
User-Service	Migration `agent_third_party_provider`, `THIRD_PARTY_CREDENTIALS_KEY`
validation-service	Same encryption key, `AGENT_KIT_POSTGRES_DB`
web3-agent-kit-service	`VALIDATION_SERVICE_URL`, provider MCP tools
agent-app-service	Swap signing + optional confirmation UI
frontend-ui	Integrations page

Next steps

Uniswap integration — chains, uniswap_swap_quote, specialist chat
LiFi integration — cross-chain routes, lifi_swap_quote, specialist chat
1inch integration — EVM aggregator swaps, oneinch_swap_quote, specialist chat
Jupiter integration — Solana swaps, jupiter_swap_quote, specialist chat
CoinGecko integration — market analytics, data_and_analytics, Data & Analytics agent
Firecrawl integration — web scraping and price compare, Web Research and Shopping agents
Bitrefill integration — gift cards, eSIMs, and mobile refills, Gift Cards & eSIMs agent
Swap confirmation — human-in-the-loop before broadcast
MCP tools reference — uniswap_swap_quote in the tool catalog
Dashboard setup — Agentic Stack navigation

Getting started

SDK & wallets