Build solutions, not workarounds.
What do you want CryptAPI and Jobber 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 Jobber
When Payment received (instant) in CryptAPI
then Add note to job in Jobber
When Payment received (instant) in CryptAPI
then Add Note to Request in Jobber
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 Jobber
Triggers and actions 1 trigger · 20 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 note to jobGraphQL mutation jobCreateNote.
Action
Add Note to RequestAdds a note to a request
Action
Add Tags to ClientAdds one or more tags to an existing Jobber client, keeping the tags it already has.
Action
Create ClientCreates a new client.
Action
Create JobCreates a new job. This will create the job for the client's first property.
Action
Create QuoteCreates a quote for a client's property in Jobber, with its line items.
Action
Create RequestCreates a new request. This will create the request for the client's first property.
Action
Find ClientFinds the client that aligns most closely with the search criteria.
Action
Find invoicesReturns up to 50 invoices that match the specified search term and filters.
Action
Find quotesReturns up to 50 Jobber quotes that match the search text and filters.
Action
Find requestsGraphQL query requests.
Action
Update clientUpdates an existing Jobber client by ID. Only the fields you fill in are changed.
Action
Update jobUpdates an existing job in Jobber: title, instructions, number, schedule, invoicing, salesperson, tax rate, job forms and custom fields. Only the fields you fill in are changed.
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 Jobber
HubSpot to JobberHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to JobberSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to JobberSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to JobberGoogle Sheets
Gmail to JobberGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to JobberGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
CryptAPI and Jobber, 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 Jobber when something happens in CryptAPI?
Any of Jobber's 13 actions, including Create Client, Create Job, Create Quote and Create Request. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Jobber to CryptAPI?
Jobber has no triggers in the catalog today, so automations start in CryptAPI. If you need the other direction, ask: your agent reads Jobber's API documentation and adds it.
Do I have to build a connector for CryptAPI or Jobber?
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.