Integration
Connect CryptAPI and PostStack
When something happens in CryptAPI or PostStack, your agent does the next thing in the other. Describe it 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 PostStack 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 and PostStack can do together
From CryptAPI to PostStack
When Payment received (instant) in CryptAPI
then Add a broadcast in PostStack
When Payment received (instant) in CryptAPI
then Add a contact in PostStack
From PostStack to CryptAPI
When Contact Updated (instant) in PostStack
then Create payment address in CryptAPI
When New Contact (instant) in PostStack
then Convert price in CryptAPI
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 PostStack
Triggers and actions 8 triggers · 38 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.
Trigger
Contact Deleted (instant)Fires when a contact is deleted (event: contact.deleted).
Trigger
Contact Updated (instant)Fires when a contact is updated (event: contact.updated).
Trigger
Email Bounced (instant)Fires when an email bounces (event: email.bounced).
Trigger
Email Delivered (instant)Fires when an email is delivered (event: email.delivered).
Trigger
New Contact (instant)Fires when a contact is created (event: contact.created).
Trigger
New Inbound EmailPolls for newly received inbound emails.
Trigger
New Sent Email (instant)Fires when an email is sent (event: email.sent).
Action
Add a broadcastCreate a new marketing broadcast.
Action
Add a contactCreate a new contact.
Action
Add a segmentCreate a new manual contact segment.
Action
Add a templateCreate a new email template.
Action
Add contacts to segmentAdd contacts to an existing segment.
Action
Add suppressionAdd an address to the suppression list.
Action
Cancel broadcastCancel an in-flight broadcast.
Action
Cancel emailCancel a scheduled or queued email before it sends.
Action
Delete a contactDelete a contact.
Action
Delete a templateDelete an email template.
Action
Get a contactFetch one contact by ID.
Action
Get a templateFetch one email template by ID.
Action
Get broadcastRetrieve one broadcast by its public id, including the HTML and text bodies that the list endpoint omits.
Action
Get emailFetch one sent or queued email by ID.
Action
Get email eventsGet the delivery event timeline for one email.
Action
Get inbound emailFetch one received inbound email by ID.
Action
Import contactsBulk-import a CSV list of contacts.
Action
List broadcastsList marketing broadcasts.
Action
List contactsList contacts in the account.
Action
List emailsList sent, queued, and scheduled emails.
Action
List inbound emailsList emails received via inbound parsing.
Action
List segmentsList contact segments.
Action
List suppressed addressesList addresses on the suppression list.
Action
List templatesList email templates.
Action
Send an emailSend a transactional email through PostStack.
Action
Send broadcastStart sending a broadcast to its recipients.
Action
Send emails in batchSend up to 100 emails in a single request.
Action
Update a contactUpdate an existing contact's fields.
Action
Update a templateUpdate an email template, creating a new version.
Action
Update emailReschedule a queued email's send time.
Action
Validate email addressCheck whether an email address is valid and deliverable.
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 PostStack
HubSpot to PostStackHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PostStackGoogle Sheets
Gmail to PostStackGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PostStackGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PostStackGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PostStackMailchimp marketing automation and email platform.
Questions
CryptAPI and PostStack, 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 PostStack when something happens in CryptAPI?
Any of PostStack's 31 actions, including Send an email, Send broadcast, Send emails in batch and Update a contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PostStack to CryptAPI?
Yes. When something happens in PostStack, your agent can act in CryptAPI too. This page covers both directions: PostStack's triggers and CryptAPI's actions are listed here as well.
Do I have to build a connector for CryptAPI or PostStack?
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.