Integration
Connect Commerce Tools to Namsor
When New customer fires in Commerce Tools, your agent runs Name Type Recognition in Namsor. 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 Tools and Namsor 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 Tools can start in Namsor
When New customer in Commerce Tools
then Name Type Recognition in Namsor
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 Tools and Namsor
Triggers and actions 2 triggers · 32 actions
- New customer
Triggers when a new customer is created in your commercetools project.
- New order
Triggers when a new order is created in the commercetools project.
- Add cart
Creates a new shopping cart in your commercetools project, optionally with line items, customer, addresses and discount codes.
- Add category
Creates a category in your commercetools project for organizing products.
- Add customer
Creates a customer in your commercetools project and returns the new customer record.
- Add order from cart
Creates an order from an existing cart, optionally setting its order number and initial order, payment and shipment states.
- Add product
Creates a product in your commercetools project with its product type, name, slug and optional variants, prices, categories and attributes.
- Delete customer
Deletes a customer, optionally erasing all of their related personal data. Returns the deleted customer.
- Delete product
Deletes a product from the catalog and returns the product as it was when deleted.
- Find categories
Finds categories in your commercetools project that match a filter, such as a key, slug or name.
- Find customers
Finds customers matching a filter condition, such as an email address or last name.
- Find inventory entries
Returns the inventory entries (stock quantities per SKU and supply channel) that match a filter.
- Find orders
Finds orders in the commercetools project that match a filter condition.
- Find products
Finds products in your commercetools project that match a filter condition, such as a product key or name.
- Get cart
Returns a cart by its id, including its line items, totals, addresses and state.
- Get customer
Returns a single customer by its id, including addresses and custom fields.
- Get order
Returns an order by its id, including line items, totals, state and custom fields.
- Get product
Returns a product by its id, including its current and staged data, variants and prices.
- Update cart
Updates a cart by applying one or more update actions, such as adding line items or setting the shipping address, and returns the updated cart.
- Update customer
Applies one or more update actions to an existing customer, such as changing their email, name or addresses, and returns the updated customer.
- Update inventory entry
Updates an inventory entry, for example adding, removing or setting its stock quantity, and returns the updated entry.
- Update order
Updates an order by applying one or more update actions, such as changing its order, shipment or payment state.
- Update product
Updates a product by applying one or more update actions, and returns the updated product.
- Get Country From Full Name
Returns the most likely country of residence for a person's unsplit full name, with the runner-up country, region, the top 10 likely countries and calibrated probabilities.
- Get Ethnicity From First/Last Name
Returns the most likely ethnicity or diaspora for a person's first and last name, with a ranked top 10 and calibrated probabilities, optionally in the context of a country of residence.
- Get Ethnicity From Full Name
Returns the most likely ethnicity or diaspora of a person from their full name, optionally in the context of their country of residence, with the top 10 likely ethnicities and calibrated probabilities.
- Get Gender From a Full Name
Returns the most likely gender of a person from their unsplit full name, with a gender scale and a calibrated probability.
- Get Gender From First/Last Name
Returns the most likely gender (male or female) for a person's first name and optional last name, with a gender scale and a calibrated probability.
- Get Indian Caste Group From First/Last Name
Returns the most likely Indian caste group (General, OBC, SC or ST) for a person's first and last name and their Indian state or Union territory, with alternatives and confidence scores.
- Get Indian Caste Group From Full Name
Returns the most likely Indian caste group (General, OBC, SC or ST) for an unsplit Indian full name and the person's Indian state or union territory.
- Get Origin From Full Name
Returns the most likely country of origin for a person's full name, with the region, alternative country, top 10 candidate countries and calibrated probabilities.
- Get U.S. Race Ethnicity From Full Name
Returns the most likely U.S. race/ethnicity (U.S. Census categories) for a person's full name, with the runner-up category and calibrated probabilities.
- Name Type Recognition
Classifies a proper noun as a personal name (anthroponym), a place name (toponym), a brand name or a pseudonym, and returns the most likely and second most likely type with a reliability score.
- Split Full Name
Splits a person's full name into its most likely first name and last name, with the detected name structure and a reliability score.
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 Tools
Commerce Tools to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Commerce Tools to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Commerce Tools to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Commerce Tools to Google SheetsGoogle Sheets
Commerce Tools to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Commerce Tools to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Namsor
Questions
Commerce Tools and Namsor, answered
What can start an automation from Commerce Tools?
Any of Commerce Tools's 2 triggers in the catalog, including New customer and New order. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Namsor when something happens in Commerce Tools?
Any of Namsor's 11 actions, including Get Country From Full Name, Get Ethnicity From First/Last Name, Get Ethnicity From Full Name and Get Gender From a Full Name. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Namsor to Commerce Tools?
Namsor has no triggers in the catalog today, so automations start in Commerce Tools. If you need the other direction, ask: your agent reads Namsor's API documentation and adds it.
Do I have to build a connector for Commerce Tools or Namsor?
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 Tools and Namsor 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.