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

ProviderMCP toolsStatus
Uniswapuniswap_swap_quoteAvailable
LiFilifi_swap_quoteAvailable
1inchoneinch_swap_quoteAvailable
Jupiterjupiter_swap_quoteAvailable

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.

Swap confirmation

User Confirm / Cancel before signing swaps in chat.

Dashboard

  1. Open Agentic Stack → Integrations for your application.
  2. Enable a provider (e.g. Uniswap).
  3. 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

StepComponentResponsibility
1DashboardEnable integration + store API key
2User-ServiceEncrypt credentials (THIRD_PARTY_CREDENTIALS_KEY)
3validation-serviceDecrypt and return thirdPartyProviders on agent validation
4Agent Kit MCPGate tools — return UNISWAP_NOT_ENABLED if disabled
5Your backendSign 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:
  1. The integration is enabled in the dashboard for that application.
  2. A valid API key is stored for the provider.
  3. 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

SecretPurpose
Application API key (dashboard Overview)Auth to Agent Kit REST/MCP
Agent accessKeySign 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

ServiceRequired for integrations
User-ServiceMigration agent_third_party_provider, THIRD_PARTY_CREDENTIALS_KEY
validation-serviceSame encryption key, AGENT_KIT_POSTGRES_DB
web3-agent-kit-serviceVALIDATION_SERVICE_URL, provider MCP tools
agent-app-serviceSwap signing + optional confirmation UI
frontend-uiIntegrations page

Next steps