Integration
Connect Hume AI to Not Human Search
When something happens in Hume AI, your agent does the next thing in Not Human Search. Describe it 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 Hume AI and Not Human Search 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 Hume AI can start in Not Human Search
When New Voice in Hume AI
then Add site for crawling in Not Human Search
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 Hume AI and Not Human Search
Triggers and actions 4 triggers · 22 actions
- Chat ended (instant)
Fires when an EVI chat session ends (chat_ended webhook event).
- Chat started (instant)
Fires when a new EVI chat session begins (chat_started webhook event).
- New Voice
Triggers when a new voice is created.
- Tool call (instant)
Fires when EVI calls a registered tool during a conversation (tool_call webhook event).
- Add config
Create a new EVI configuration (voice assistant setup).
- Add prompt
Create a new system prompt for use in an EVI configuration.
- Add tool
Create a new tool definition that EVI can call during a conversation.
- Add voice
Save a new custom voice to the account from a TTS generation ID, for reuse in later speech requests.
- Convert voice
Convert the speech in an uploaded audio file into a different saved voice.
- Delete config
Delete an EVI configuration from the account.
- Delete voice
Delete a saved custom voice from the account.
- Generate Text to Speech
Convert text to speech using Hume AI's expressive text-to-speech technology.
- List configs
List the EVI configurations saved to the account.
- List prompts
List the prompts saved to the account.
- List tools
List the tool definitions saved to the account.
- List voices
List the custom voices saved to the account.
- Update config
Update an EVI configuration's name or description.
- Add site for crawling
Submit a site for crawling to be indexed for agentic readiness.
- Check site readiness
Run an on-demand agentic readiness check via a live crawl of a URL.
- Find sites by criteria
Search for agent-ready sites matching criteria.
- Get index statistics
Get overall index statistics for the agentic readiness index.
- Get site readiness report
Get detailed agentic readiness report for a site by domain.
- List categories
Get all category buckets and their site counts.
- List commerce catalog
Get the agent-readable commerce catalog.
- List top sites
List top-scored agent-ready sites.
- Verify MCP compliance
Live-probe a URL for MCP (Model Context Protocol) compliance.
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 Hume AI
Hume AI to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Hume AI to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Hume AI to MailchimpMailchimp marketing automation and email platform.
Hume AI to StripeStripe is a payment processing platform for online businesses.
Hume AI to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Hume AI to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Not Human Search
HubSpot to Not Human SearchHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Not Human SearchGoogle Sheets
Gmail to Not Human SearchGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Not Human SearchGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Hume AI and Not Human Search, answered
What can start an automation from Hume AI?
Any of Hume AI's 4 triggers in the catalog, including New Voice, Chat ended (instant), Chat started (instant) and Tool call (instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Not Human Search when something happens in Hume AI?
Any of Not Human Search's 9 actions, including Add site for crawling, Check site readiness, Find sites by criteria and Get index statistics. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Not Human Search to Hume AI?
Not Human Search has no triggers in the catalog today, so automations start in Hume AI. If you need the other direction, ask: your agent reads Not Human Search's API documentation and adds it.
Do I have to build a connector for Hume AI or Not Human Search?
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.