Integration
Connect Commerce Layer to Base64.ai
When New Attachment fires in Commerce Layer, your agent runs Scan a Document by Bytes in Base64.ai. 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 Commerce Layer and Base64.ai to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 Commerce Layer can start in Base64.ai
When New Attachment in Commerce Layer
then Scan a Document by Bytes in Base64.ai
When New Customer in Commerce Layer
then Scan a Document by URL in Base64.ai
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 Commerce Layer and Base64.ai
Triggers and actions 13 triggers · 32 actions
Trigger
New AttachmentTriggers when a new Attachment is created.
Trigger
New CustomerTriggers when a new Customer is created.
Trigger
New Customer Address EventTriggers when a customer address is created.
Trigger
New Customer Password Reset EventTriggers when a customer password reset is requested.
Trigger
New Customer Subscription EventTriggers when a given customer_subscription event (one of create or destroy) is fired.
Trigger
New PriceTriggers when a new Price is created.
Trigger
New Price ImportFires when a new price import is created in Commerce Layer.
Trigger
New Price ListTriggers when a new Price List is created.
Trigger
New Shipping CategoryTriggers when a Shipping Category is created.
Trigger
New SKUTriggers when a new SKU is created.
Trigger
New SKU ImportTriggers when a new SKU import is created.
Trigger
New Stock Item ImportTriggers when a new Stock Item import is created.
Trigger
New Stock Transfer EventTriggers when a given stock transfer event (one of create, upocoming, picking, in_transit, complete, cancel is fired).
Action
Add Customer AddressAdds an existing address to a customer's address book.
Action
Add Customer Password ResetRequests a password reset for a customer, returning the reset token to send them.
Action
Add Customer SubscriptionSubscribes a customer email to a list, identified by a reference such as a newsletter id.
Action
Add Stock TransferMoves a quantity of a SKU from one stock location to another.
Action
Balance Change Gift CardChange balance of a gift card.
Action
Create AddressCreates a postal address that can be attached to customers, orders and stock locations.
Action
Create AttachmentCreates a new Attachment.
Action
Create CustomerCreates a new Customer.
Action
Create Gift CardCreates a new Gift Card.
Action
Create Price ImportCreates a new Price Import.
Action
Create Price ListCreates a new Price List.
Action
Create SKUCreates a new SKU.
Action
Find AttachmentFinds a Attachment by name.
Action
Find CustomerFinds a customer by id or reference.
Action
Find Gift CardFinds a gift card by id or reference.
Action
Find PriceFinds a price by price list.
Action
Find Price ImportFinds a Price Import by status.
Action
Find Price ListFinds a Price List by name.
Action
Find Shipping CategoryFinds an Shipping Category by name.
Action
Find SKUFinds an SKU by code.
Action
Find SKU ImportFinds an SKU Import by status.
Action
Find Stock Item ImportFinds a Stock Item Import by status.
Action
Get AddressRetrieves one address by id.
Action
Get Customer AddressRetrieves one customer address link by id.
Action
Get Customer Password ResetRetrieves a customer password reset by id, returning customer_email, reset_password_token and reset_password_at.
Action
Get Customer SubscriptionRetrieves one customer subscription by id.
Action
Get Stock TransferRetrieves one stock transfer by id.
Action
Update Customer ReferenceUpdate customer data setting external identifier.
Action
Match faces/api/face. With one document, detects faces; with document (ground truth) plus query (e.g. selfie), returns matching face coordinates. Accepts base64 data URI or url.
Action
Match signatures/api/signature. With one document, detects signatures; with document (ground truth) plus query, verifies whether the signatures match. Accepts base64 data URI or url.
Action
Scan a Document by BytesScans a document that is provided by a string of bytes (e.g. data:image/png;base64,iVBORw0KGgoAAAANSUhEU...). File can be an image (jpeg, png etc.), PDF, zip or an office document (.doc, .docx, etc.).
Action
Scan a Document by URLScans a document that is provided by a URL or Hydrate File. File can be an image (jpeg, png etc.), PDF, zip or an office document (.doc, .docx, etc.).
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 Commerce Layer
Commerce Layer to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Commerce Layer to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Commerce Layer to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Commerce Layer to Google SheetsGoogle Sheets
Commerce Layer to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Commerce Layer to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Base64.ai
HubSpot to Base64.aiHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Base64.aiSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Base64.aiSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Base64.aiGoogle Sheets
Gmail to Base64.aiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Base64.aiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Commerce Layer and Base64.ai, answered
What can start an automation from Commerce Layer?
Any of Commerce Layer's 13 triggers in the catalog, including New Attachment, New Customer, New Customer Address Event and New Customer Password Reset Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Base64.ai when something happens in Commerce Layer?
Any of Base64.ai's 4 actions, including Match faces, Match signatures, Scan a Document by Bytes and Scan a Document by URL. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Base64.ai to Commerce Layer?
Base64.ai has no triggers in the catalog today, so automations start in Commerce Layer. If you need the other direction, ask: your agent reads Base64.ai's API documentation and adds it.
Do I have to build a connector for Commerce Layer or Base64.ai?
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.
Can my AI client use Commerce Layer and Base64.ai without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.