
WAGMI
We're All Gonna Make It
WAGMI FOR AI ASSISTANTS
Your assistant.
Your WAGMI account.
Check balances, explore Earn markets and compare swap quotes from the conversation you’re already having.
“What USDC balances can you see in my wallet?”
“Compare the supported USDC Earn markets.”
“Quote 100 USDC to WAGMI on Ethereum.”
ONE BACKEND. MORE WAYS IN.
The API, ready for your assistant.
The API lets applications talk to WAGMI. MCP gives compatible AI assistants a list of tools they can understand and call. Both use the same WAGMI account permissions and backend.
This version reads data and creates quotes. It cannot sign transactions, execute trades or change trading permissions. Use WAGMI to review and submit a trade; a quote in chat is not a submitted transaction.
GET CONNECTED
One key. A few simple steps.
- Sign in and open Settings → API & bots. Create a dedicated key for your assistant and select the wallets it may access.
- Choose the read permissions you need and quote creation if you want swap quotes. You do not need to enable standing trading access to connect MCP.
- In a client that supports remote MCP with custom authorization, add the server URL below. Set
Authorization: Bearer YOUR_WAGMI_BOT_KEYin its secure connection settings. - Ask “Which WAGMI wallets and permissions can you see?” to verify the connection.
https://wagmi-api.vercel.app/mcpConnection type: Streamable HTTP. Keep the key in your client’s secret storage, never in a prompt, shared screenshot or public configuration file.
CHOOSE YOUR CLIENT
Connect where your assistant runs.
Support depends on the client, not just its model. These are API integration examples; they do not automatically connect the consumer Grok or ChatGPT apps.
OpenAI · Responses API
Add this MCP tool to the request’s tools array. Your application should inject the API key from server-side secret storage and handle approval requests.
{
"type": "mcp",
"server_label": "wagmi",
"server_url": "https://wagmi-api.vercel.app/mcp",
"authorization": "<WAGMI_BOT_KEY_FROM_YOUR_SECRET_STORE>",
"require_approval": "always"
}Grok · xAI API
Use the remote MCP tool in the xAI Responses API. Supply the WAGMI server URL and authorization token from your backend, and let the user choose which tools the assistant can call.
{
"type": "mcp",
"server_label": "wagmi",
"server_url": "https://wagmi-api.vercel.app/mcp",
"authorization": "<WAGMI_BOT_KEY_FROM_YOUR_SECRET_STORE>",
"allowed_tools": [
"get_account",
"get_balances",
"get_earn_markets",
"search_assets",
"quote_swap"
]
}Other MCP clients
Add a remote Streamable HTTP server using the URL and bearer header above. This release uses WAGMI API keys; OAuth sign-in and clients that require OAuth are not supported yet. If a client cannot securely supply a bearer header, use a compatible client or integrate through the Developer API.
AVAILABLE TO YOUR ASSISTANT
Useful tools. Familiar permissions.
Your assistant only discovers tools allowed by your key’s permissions. API coverage can differ from the website; request capabilities before assuming a network or asset is supported.
get_accountYour available wallets and key permissions
search_assetsToken identifiers to use in quotes
get_capabilitiesSupported API networks and actions
get_balancesSpot balances for an authorized wallet
get_earn_marketsSupported Morpho vaults and Aave reserves
get_earn_positionsYour supported Earn positions
quote_swapA fresh swap quote, including its returned fees and minimum output
get_executionsYour WAGMI API execution history
get_executionStatus and settlement of a specific API execution
You control the connection.
Revoke the key in Settings whenever you want to stop future access. Even a key with trading permissions cannot execute trades through these MCP tools. Never share your wallet password, recovery phrase or signing shares with an assistant.
Quotes can expire and expected output can change. Check minimum received, fees and network costs in WAGMI before signing. Missing balances or fee estimates must not be treated as zero.
Want to build an automated trading application? The Developer API documentation covers separate, explicitly authorized execution policies.