Integration
Connect CryptAPI to RD Station
When Payment received (instant) fires in CryptAPI, your agent runs Add contact in RD Station. 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 RD Station 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)CryptAPI generates the crypto payment addresses your customers send funds to, and RD Station holds the contact records behind those payments. Joining them means a payment landing on a CryptAPI address can create or update the contact in RD Station, record the conversion, mark the sale as won and tag the person, without anyone copying details between the two.
Example flows
What CryptAPI can start in RD Station
When Payment received (instant) in CryptAPI
then Add contact in RD Station
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 RD Station
Triggers and actions 1 trigger · 22 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.
- Add contact
Creates a new contact in the RD Station Marketing lead base. Fails if a contact with the same email or phone already exists.
- Add custom field
Creates a new custom contact field in your RD Station Marketing account.
- Add tag to contact
Adds one or more tags to an existing RD Station Marketing contact, found by UUID, email or phone. Tags are added alongside the contact's existing tags.
- Conversion Event
Records a conversion event in RD Station Marketing, creating or updating the contact identified by email or phone.
- Delete contact
Deletes a contact from RD Station Marketing, found by its UUID, email or phone.
- Delete custom field
Deletes a custom contact field from the RD Station Marketing account. Default fields cannot be deleted.
- Get contact
Returns a contact's standard and custom fields, looked up by UUID, email or phone.
- List contact events
Returns the conversion or opportunity events recorded for an RD Station Marketing contact.
- List custom fields
Returns all contact fields in the RD Station Marketing account, both standard and custom fields.
- List segmentation contacts
Returns the contacts that belong to an RD Station Marketing segmentation.
- List segmentations
Returns the segmentations (contact segments) defined in your RD Station Marketing account.
- Lost Deal
Marks an existing RD Station Marketing contact as a lost opportunity in the default funnel, with a loss reason.
- Update contact
Updates an existing contact in RD Station Marketing, found by its uuid, email or phone. Creates the contact if none matches.
- Update custom field
Updates the name, label, data type, presentation type and options of an existing contact custom field in RD Station Marketing.
- Won Deal
Marks an existing RD Station Marketing contact as a won opportunity (sale), optionally with the deal value.
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 RD Station
Google Calendar to RD StationGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
CryptAPI and RD Station, answered
How does RD Station know a crypto payment arrived?
CryptAPI calls back the moment a payment address created through Create payment address receives funds, and that callback starts the run. From there the agent can record a Conversion Event, update the contact or mark a Won Deal in RD Station with the amount paid.
What if the payer is not yet in our RD Station base?
The agent can look the person up with Get contact by email or phone first and only continue when a record exists. If you would rather not lose anyone, use Add contact or Update contact, which creates the contact when nothing matches.
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 RD Station when something happens in CryptAPI?
Any of RD Station's 15 actions, including Add contact, Add tag to contact, Conversion Event and Update contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from RD Station to CryptAPI?
RD Station has no triggers in the catalog today, so automations start in CryptAPI. If you need the other direction, ask: your agent reads RD Station's API documentation and adds it.
Do I have to build a connector for CryptAPI or RD Station?
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.