How IATO uses artificial intelligence services
IATO integrates with the following third-party AI services to power its intelligent features:
| Provider | Service | Used for |
|---|---|---|
| Anthropic | Claude (claude-sonnet-4-20250514) | Navigation detection, sitemap AI assistant, content analysis, SEO recommendations |
| OpenAI | GPT-4o, GPT-4o-mini | Alternative AI provider configured by the platform administrator for all AI features. Users may also bring their own API key (BYOK) |
Not all IATO features labeled “AI” make calls to external language models. Here is a breakdown:
These features use local heuristic, keyword-matching, or rule-based algorithms and do not send data to any external AI provider:
When an AI feature is triggered, only the minimum data necessary for that specific task is sent to the AI provider. For example, navigation detection sends page HTML snippets; the sitemap assistant sends sitemap structure and page metadata. No data is sent to any AI provider unless you actively use an AI-powered feature.
IATO does not use your data to train AI models. Both Anthropic and OpenAI provide API terms that exclude customer API data from model training. For details, see Anthropic’s Privacy Policy and OpenAI’s Enterprise Privacy.
IATO supports a Bring Your Own Key model. You can configure your own Anthropic or OpenAI API key in the dashboard settings. When a personal key is configured, AI requests are made directly using your key and billed by the provider to your account. When no personal key is configured, IATO uses its own system key and the cost is included in your subscription at a marked-up rate.
All AI API calls are logged in the IATO platform with full attribution: which feature triggered the call, which provider and model were used, token counts, estimated cost, and whether a system or user-provided key was used. Platform administrators can review this data in the Admin → AI Usage & Costs dashboard.
IATO provides a Model Context Protocol (MCP) server with 105 tools that allow AI assistants like Claude to interact with IATO programmatically. The MCP server acts as a bridge between AI agents and the IATO REST API — it does not itself make AI inference calls. Any AI reasoning happens on the agent side (e.g., in Claude Desktop or another MCP-compatible client), not within IATO’s infrastructure.
If you have questions about how IATO uses AI services, please contact us at [email protected].
This page was last updated on March 23, 2026.