Use case · Software-as-a-Service
Your agent backend. Bought, not built over years.
Your SaaS product gets AI agents, knowledge processing and autonomous processes – without building your own agent backend. Hawk IVO Force is the backend: connected via API, CLI and MCP. The chat widget in your frontend is optional.
Use case · Software-as-a-Service
Three integration depths
01 · Backend-only
API + CLI
Drive agent runs, knowledge sources and tenants straight from your code – one token context across all channels.
02 · MCP both ways
Your functions become AI-operable
Your business functions become usable by agents via MCP – and Hawk IVO Force itself acts as an MCP server for your tools.
03 · Frontend optional
Widget or your own UI
Ready-made embed widget with SSO – or build your own UI on the API. Brand and customer relationship stay yours.
POST /v1/agents/support-twin/runs # Agent-Lauf aus Ihrem Backend $ getaitwin agents run support-twin --input "Ticket 4711" mcp: getaitwin.search_knowledge · getaitwin.create_todo · …
Isolated per end customer
Create tenants per end customer through the partner API – with cost visibility per tenant.
Roadmap – honestly
SDKs, service-account auth and white-label are in development. The partner program gives you architecture commitments with a timeline.