Integration
Connect CryptAPI to Pickaxe
When Payment received (instant) fires in CryptAPI, your agent runs Create Document in Pickaxe. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want CryptAPI and Pickaxe 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 Pickaxe
When Payment received (instant) in CryptAPI
then Create Document in Pickaxe
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 Pickaxe
Triggers and actions 1 trigger · 25 actions
- 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.
- Convert price
Convert a value between a fiat currency and a cryptocurrency, or between two cryptocurrencies, for a given ticker.
- Create payment address
Generate 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.
- Estimate blockchain fees
Estimate the blockchain network fee to forward a transaction to a wallet address, for a given cryptocurrency ticker.
- Generate payment QR code
Generate a base64-encoded QR code image for a payment address, for a given cryptocurrency ticker.
- Get payment address logs
Get the callback/payment activity log for a previously created payment address, for a given ticker.
- Get ticker info
Get details (minimum transaction amount, fees, current price) for a specific cryptocurrency ticker.
- List supported cryptocurrencies
List all cryptocurrencies and blockchains supported by CryptAPI, with logos, minimum transaction amounts, and fee tiers.
- Connect Document
Connect a document to a Pickaxe or User.
- Create Access Group
Create a new access group.
- Create Document
Create a new document with the provided details.
- Create User
Create a new document with the provided details.
- Delete Access Group
Delete an access group, or reassign links and users before deleting it.
- Delete Document
Delete a specific document by its ID.
- Delete User
Delete a specific user by their email.
- Disconnect Document
Detach a document from a Pickaxe or User.
- Find Access Group
Retrieve a specific access group by its ID.
- Find Access Groups
List all access groups for a studio workspace.
- Find Document by ID
Retrieve a specific document by its ID.
- Find Documents
Finds knowledge base documents whose name or title contains the given text.
- Find User by Email
Retrieve a specific user by their email.
- Find Users
List all users with optional pagination.
- Preview Delete Access Group
Preview the impact of deleting an access group.
- Remove Access Group Links
Remove access groups from deployments or portals, or remove resources from an access group.
- Update Access Group
Update an existing access group.
- Update User
Update a specific user by their email.
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 RD StationRD Station is a complete digital marketing platform to help you generate more results in traffic generation...
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
More into Pickaxe
Gmail to PickaxeGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PickaxeGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
CryptAPI and Pickaxe, 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 Pickaxe when something happens in CryptAPI?
Any of Pickaxe's 18 actions, including Create Access Group, Create Document, Create User and Update Access Group. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pickaxe to CryptAPI?
Pickaxe has no triggers in the catalog today, so automations start in CryptAPI. If you need the other direction, ask: your agent reads Pickaxe's API documentation and adds it.
Do I have to build a connector for CryptAPI or Pickaxe?
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.