Search HGInsights

Resources

No posts found! Try adjusting your filters.

Frequently asked questions

What does a team need to run HG Agents?

A company domain or campaign criteria and a delivery channel. There is no schema to learn, no pipeline to build, and no prompt engineering required. HG Agents run on HG Fabric rather than relying on data sources the customer has to provide.

How do HG Agents handle security and compliance?

GDPR and CCPA apply. Endpoints are authenticated, logged, and monitored, inputs are screened for prompt injection, sensitive data is redacted before storage, and every agent run creates an audit trail. HG Insights runs testing quarterly.

Can HG Agents be invoked from a customer's own agent?

Yes. Agents can be triggered and monitored through HG MCP Server, so a customer-built agent or MCP client can call an HG agent as one step in a larger workflow and read the finished artifact back.

Where do HG Agents outputs get delivered?

Slack, Microsoft Teams, the HG MCP App, or embedded in the customer's own application. Account admins configure each HG Superagent instance, including its name, identity, and the skills available to that organization.

How is HG Agents priced?

Consumption is credit based, so a team pays for the agent runs and data calls it uses.

What's the difference between HG Agents and HG Superagent?

HG Agents is the library of pre-built agents, each built to handle a specific GTM workflow such as account research, committee mapping, list building, contact discovery, and more. HG Superagent is the routing layer: when a request doesn't name a specific agent, it directs the request to the right workflow across the full catalog of more than 60 GTM workflows and 60 supporting skills. Superagent is included with HG Agents, not a separate add-on.

Schedule a Custom Demo