Integration
Connect Wachete to Namsor
When New notification for monitor fires in Wachete, 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 Wachete 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 Wachete can start in Namsor
When New notification for monitor in Wachete
then Name Type Recognition in Namsor
When Any new notification in Wachete
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 Wachete and Namsor
Triggers and actions 2 triggers · 18 actions
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
Trigger
New notification for monitorFires when there is a new change notification from the specified Wachete monitor (taskId).
Action
Create monitorCreate a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
Action
Delete monitorDelete a Wachete monitor by its ID.
Action
Get monitorGet information about a specific Wachete monitor by its ID.
Action
Get monitor dataGet the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
Action
List foldersList folder contents, optionally under a parent folder.
Action
List notificationsList change notifications, optionally filtered by monitor (taskId) and date range.
Action
Update monitorChange the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
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 Wachete
Wachete to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Wachete to ActiveCampaignActiveCampaign is a marketing automation, email marketing, and CRM platform.
Wachete to JIRAAtlassian JIRA Cloud — issue tracking and project management.
Wachete to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Wachete to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Wachete to AnthropicAnthropic builds Claude, a family of large language models.
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
Wachete and Namsor, answered
What can start an automation from Wachete?
Any of Wachete's 2 triggers in the catalog, including New notification for monitor and Any new notification. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Namsor when something happens in Wachete?
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 Wachete?
Namsor has no triggers in the catalog today, so automations start in Wachete. 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 Wachete 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 Wachete 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.