Build solutions, not workarounds.
What do you want CryptAPI and Peaka to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What CryptAPI can start in Peaka
When Payment received (instant) in CryptAPI
then Add connection in Peaka
When Payment received (instant) in CryptAPI
then Add query in Peaka
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with CryptAPI and Peaka
Triggers and actions 1 trigger · 17 actions
Trigger
Payment received (instant)Fires when a payment address created via Create payment address receives funds; CryptAPI calls the callback URL supplied at creation time with the payment details.
Action
Convert priceConvert a value between a fiat currency and a cryptocurrency, or between two cryptocurrencies, for a given ticker.
Action
Create payment addressGenerate a new cryptocurrency payment address for a given ticker (e.g. btc, eth, trc20/usdt) that a customer can send funds to, with a callback URL for payment notifications.
Action
Estimate blockchain feesEstimate the blockchain network fee to forward a transaction to a wallet address, for a given cryptocurrency ticker.
Action
Generate payment QR codeGenerate a base64-encoded QR code image for a payment address, for a given cryptocurrency ticker.
Action
Get payment address logsGet the callback/payment activity log for a previously created payment address, for a given ticker.
Action
Get ticker infoGet details (minimum transaction amount, fees, current price) for a specific cryptocurrency ticker.
Action
List supported cryptocurrenciesList all cryptocurrencies and blockchains supported by CryptAPI, with logos, minimum transaction amounts, and fee tiers.
Action
Add connectionCreates a new data source connection in a Peaka project.
Action
Add queryCreates a saved SQL query (plain or materialized) in a Peaka project, optionally inside a folder.
Action
Delete connectionDeletes a connection from a Peaka project. Any catalogs using this connection lose access to their data source.
Action
Delete queryPermanently deletes a saved query from a Peaka project.
Action
Get queryReturns a single saved query in a Peaka project by its ID, including its SQL, type, schedule and folder location.
Action
List connectionsLists all connections (authenticated links to external data sources) in a Peaka project.
Action
List projectsLists all projects within a Peaka workspace.
Action
List queriesReturns all saved queries in a Peaka project, including each query's folder path when it sits in a folder.
Action
Run Peaka Query (With Line Item Support)Runs a SQL statement, a saved query, or a query builder request in a Peaka project and returns the result rows as line items.
Action
Update queryUpdates the display name, SQL, type or schedule of an existing Peaka query. Fields left blank keep their current values.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from CryptAPI
CryptAPI to SLFSLF is a German-language geographic reference service covering cities, countries, and rivers.
CryptAPI to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CryptAPI to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CryptAPI to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CryptAPI to Google SheetsGoogle Sheets
CryptAPI to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Peaka
HubSpot to PeakaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to PeakaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to PeakaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to PeakaGoogle Sheets
Gmail to PeakaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PeakaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
CryptAPI and Peaka, answered
What can start an automation from CryptAPI?
Any of CryptAPI's 1 trigger in the catalog, including Payment received (instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Peaka when something happens in CryptAPI?
Any of Peaka's 10 actions, including Update query, Add connection, Add query and Get query. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Peaka to CryptAPI?
Peaka has no triggers in the catalog today, so automations start in CryptAPI. If you need the other direction, ask: your agent reads Peaka's API documentation and adds it.
Do I have to build a connector for CryptAPI or Peaka?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.