All integrationsHermes Agent integration

Data AI Search inside Hermes Agent

Add one server to ~/.hermes/config.yaml and Hermes can read your brand's Insights, AI Visibility audit and Website Audit, and act on them in the same chat where it already does your SEO work.

MCP is included on paid plans. Each tool call uses credits from your workspace.
Setup01

Connect it in four steps

You need Hermes Agent installed and connected to a model, and a paid Data AI Search plan. The key stays in Hermes' .env file, so config.yaml never contains it.

1

Copy your API key

Open Integrations → Hermes Agent in the Data AI Search dashboard. The page shows your key and both snippets below with the key already filled in. Treat it like a password: anyone who has it can read the workspace and spend its credits.

2

Save it in ~/.hermes/.env

Add the key as INTURA_API_KEY, then lock the file with chmod 600. If you run a Hermes profile, use that profile's .env instead.

~/.hermes/.env
INTURA_API_KEY=your_api_key

# then, in a terminal
chmod 600 ~/.hermes/.env
3

Add Intura under mcp_servers

Hermes fills in the INTURA_API_KEY placeholder from your .env when it connects. The key has to sit in the URL as ?api_key=. An Authorization header is rejected by this server.

~/.hermes/config.yaml
mcp_servers:
  intura:
    url: "https://api.dataaisearch.com/mcp?api_key=${INTURA_API_KEY}"
4

Reload, test, ask

Type /reload-mcp in a running chat or run hermes mcp test intura. Then ask a question only your workspace can answer, and check that an mcp__intura__ tool actually ran.

Terminal
hermes mcp test intura

# or, inside a running chat
/reload-mcp

# first question
Which Intura brands can you see? Tell me which tool you called.
Tools02

What Hermes can do with your workspace

Hermes names each server tool mcp__, then the server name, two underscores and the tool name. With the server named intura, you get these three. Name a brand in your question; leave it out and the agent gets your brand list first.

Brand Insights

mcp__intura__brand_insights

The questions a brand's customers ask AI, how AI answers them, the keywords and segments behind them, and a search of those questions by meaning. Read-only.

AI Visibility audit

mcp__intura__ai_visibility_audit

Read the report, tracked questions, clusters and next actions. It can also set up the audit, add or run questions and mark an action done. Setup and runs cost what they cost in the dashboard.

Website Audit

mcp__intura__website_audit

Read scores, problems, weakest pages and the action checklist. It can also start an audit, re-check new pages or a single page, and mark an action done.

Every call costs 1 credit, reads included. Setting up or running AI Visibility questions and starting a Website Audit charge their dashboard price instead.

Control03

Decide what the agent is allowed to do

An agent asked to “check our visibility” may decide a fresh run is the best way to check. These settings keep it to what you meant.

Start read-only

List only brand_insights under tools.include. Hermes then never loads the two audit tools, so it cannot start runs or audits. Filters take the plain tool name, not the mcp__intura__ one.

Be stricter for cron and shared chats

A hermes cron job or a Telegram gateway runs without you watching. Keep those on the read-only filter unless the job is meant to start audits, and run a new job once by hand before you schedule it.

Keep the key out of logs

The key travels in the URL, so anything that logs full request URLs can capture it. Keep it in .env, never paste config.yaml with a real key into a chat, and email [email protected] if you think it leaked.

Watch the balance in week one

Agents retry and explore, so they can make more calls than you expect. The Integrations page in the dashboard shows the remaining credits.

~/.hermes/config.yaml
mcp_servers:
  intura:
    url: "https://api.dataaisearch.com/mcp?api_key=${INTURA_API_KEY}"
    tools:
      include: [brand_insights]
Troubleshooting04

When the connection fails

The server fails to connect and names a missing variable

INTURA_API_KEY is not set in the .env of the profile you are running. Hermes refuses to connect with an unresolved placeholder on purpose. Add it and run /reload-mcp.

401 or “api_key query parameter is required”

The key is missing from the URL, or you sent it in a header. Use the url line exactly as shown in step 3, with the INTURA_API_KEY placeholder after ?api_key=.

No mcp__intura__ tools after editing config.yaml

Type /reload-mcp. A running gateway picks up config changes within about a minute; a chat session does not until you reload.

The tools disappeared after adding a filter

tools.include matched nothing. Use brand_insights, ai_visibility_audit or website_audit, not the prefixed names. When a filter removes every tool, Hermes creates no toolset for the server.

Calls fail with a credits message

The workspace balance is below 1. Top up or upgrade from the dashboard; the connection itself is fine.

FAQ

Hermes Agent and Data AI Search: common questions

Get started10

See what AI says about your market

Explore the platform, or talk to us about what people ask AI in your category and how your brand shows up.

Start building your AI presence

Sign up and explore Intura. See how AI sees your brand today — and how we help you get surfaced across AI Search, Social Media, and Google.

Explore platform

Free to start • No commitment