Integration
Connect Loyverse to Namsor
When Customer Update fires in Loyverse, 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 Loyverse 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 Loyverse can start in Namsor
When Customer Update in Loyverse
then Name Type Recognition in Namsor
When Inventory Update in Loyverse
then Split Full Name 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 Loyverse and Namsor
Triggers and actions 4 triggers · 56 actions
Trigger
Customer UpdateTriggers when a customer is updated.
Trigger
Inventory UpdateTriggers when a stock updates.
Trigger
Items UpdateTriggers when an item is updated.
Trigger
Receipts UpdateTriggers when a receipt gets created or updated.
Action
Create or Update CategoryCreates or Updates a single category.
Action
Create or Update DiscountCreates or Updates a single discount.
Action
Create or Update ModifierCreates or Updates a modifier.
Action
Create or Update POS DeviceCreates or Updates a single POS device.
Action
Create or Update ReceiptsCreates a receipt
Action
Create or Update Single CustomerCreates or Updates a Single Customer.
Action
Create or Update Single ItemAction
Create or Update SupplierCreates or Updates a single supplier.
Action
Create or Update TaxCreates or Updates a tax.
Action
Create Refund ReceiptCreates a refund receipt. When using the refund API you should take into account these notes: - At the moment refund API allows creating a refund only for sales receipts which are paid by a single payment. For any attempt to make a refund for a sales receipt that has more than one payment Loyverse API will respond with an error. - Refund API doesn't support a refund of receipts paid by integrated payments using Loyverse POS app (e.g. iZettle, Sumup, etc.). For this purpose please use Loyverse POS app. - If a refund is created successfully, it will cause a restock of items specified in a refund receipt.
Action
Delete Singe ItemDeletes a single item.
Action
Delete Single CategoryDeletes a single category.
Action
Delete Single CustomerDeletes a single customer.
Action
Delete Single DiscountDeletes a single discount.
Action
Delete Single ModifierDeletes a single Modifier.
Action
Delete Single POS DeviceDeletes a single POS Device.
Action
Delete Single SupplierDeletes a single supplier.
Action
Delete Single TaxDeletes a single tax.
Action
Delete Single VariantDeletes a single variant.
Action
Get List of CategoriesGet list of all categories.
Action
Get List of CustomersGet list of Customers
Action
Get List of DiscountsReturns discounts, most recently created first.
Action
Get List of EmployeesGets a list of employees.
Action
Get List of ItemsGet list of items
Action
Get List of Payment TypesGet list of Payment Types
Action
Get List of POS DevicesThe list of pos devices is sorted by created_at property in descending order. The most recent pos devices appear first
Action
Get List of StoresGet list of stores
Action
Get List of SuppliersGets a list of suppliers.
Action
Get List of TaxesGet list of taxes
Action
Get List of VariantsGet lists of item variants.
Action
Get Merchant InformationReturns the business profile of the connected Loyverse merchant account.
Action
Get Single CategoryGet Single Category.
Action
Get Single CustomerGet Single Customer
Action
Get Single DiscountGets a single discount.
Action
Get Single EmployeeGets a single employee.
Action
Get Single ItemGet single item
Action
Get Single ModifierGets a single modifier.
Action
Get Single Payment TypeFetches a payment type by ID. An error occurs if the payment type is not found.
Action
Get Single POS DeviceFetches a POS device by ID. An error occurs if the POS device is not found.
Action
Get Single ReceiptGet a single Receipt.
Action
Get Single StoreGet Single Store
Action
Get Single SupplierFetches a supplier by ID. An error occurs if the supplier is not found.
Action
Get Single TaxGets a single tax.
Action
Get Single VariantGets single item variant.
Action
Update Inventory Levels for ItemsBatch updates Inventory Levels for Item Variants.
Action
Get Country From Full NameReturns 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.
Action
Get Ethnicity From First/Last NameReturns 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.
Action
Get Ethnicity From Full NameReturns 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.
Action
Get Gender From a Full NameReturns the most likely gender of a person from their unsplit full name, with a gender scale and a calibrated probability.
Action
Get Gender From First/Last NameReturns 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.
Action
Get Indian Caste Group From First/Last NameReturns 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.
Action
Get Indian Caste Group From Full NameReturns 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.
Action
Get Origin From Full NameReturns the most likely country of origin for a person's full name, with the region, alternative country, top 10 candidate countries and calibrated probabilities.
Action
Get U.S. Race Ethnicity From Full NameReturns 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.
Action
Name Type RecognitionClassifies 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.
Action
Split Full NameSplits 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 Loyverse
Loyverse to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Loyverse to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Loyverse to MailchimpMailchimp marketing automation and email platform.
Loyverse to StripeStripe is a payment processing platform for online businesses.
Loyverse to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Loyverse to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Namsor
HubSpot to NamsorHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to NamsorSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to NamsorSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to NamsorGoogle Sheets
Gmail to NamsorGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to NamsorGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Loyverse and Namsor, answered
What can start an automation from Loyverse?
Any of Loyverse's 4 triggers in the catalog, including Customer Update, Inventory Update, Items Update and Receipts Update. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Namsor when something happens in Loyverse?
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 Loyverse?
Namsor has no triggers in the catalog today, so automations start in Loyverse. 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 Loyverse 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 Loyverse 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.