# Getting started with AI

> Connect your Black Ice ontology to AI models in minutes.

**Category:** Getting started | **Tab:** getting-started

---

## Why connect AI to your ontology?

Black Ice structures your terminology, market rules, and brand voice. AI models consume that structure and turn it into governed content — translations, copy, QA checks — without guessing.

> Without an ontology, AI writes fluently. With one, it writes *correctly*.

## The 3-step pattern

**1. Pick a connection path**

There are three ways to get your ontology in front of an AI tool. They are complementary — most teams end up using two.

| Path | Best for | Access model | Plan |
|---|---|---|---|
| **MCP server** | Live agent access (Claude, Cursor, IDEs) | OAuth or API key, tools | All plans |
| **Workspace API** | Custom pipelines, CI jobs, bulk reads/writes | API key, JSON | All plans |
| **GitHub Sync** | Repo-native agents, review workflows, versioned snapshots | GitHub PAT, Markdown | Builder |

If a human is chatting with an AI client, start with **MCP** — it is always current and needs no export step. If you are scripting, use the **Workspace API**. If your agent lives in a code repo, use **GitHub Sync**.

**2. Connect your tool**

- **Claude (web or desktop)** — add Black Ice as a custom connector: [Connect Claude to your workspace (step by step)](/docs/integrations/connect-claude-mcp)
- **Cursor, VS Code, other MCP clients** — [Connect Cursor and other MCP clients](/docs/integrations/connect-cursor-mcp)
- **Custom pipelines** — [Workspace API access](/docs/integrations/workspace-api-access)
- **Repo-based agents (Claude Code, Codex, CI)** — [GitHub Sync](/docs/integrations/github-sync)
- **One-off use (Gemini, Custom GPTs, NotebookLM)** — use **Export** and attach the Markdown, ZIP, or PDF bundle

**3. Prompt with semantic context**

Your prompts no longer need to explain terminology, tone, or market rules. The ontology already contains all of that, so prompts become task-focused:

- *"Write a landing page for the Spain market"*
- *"Review these translated strings for terminology consistency"*
- *"Localize only the concepts that changed since last sprint"*

Ready-made prompts for localization workflows are in the [Claude guide](/docs/integrations/connect-claude-mcp).

## What can you do with it?

- **Generate market-specific content** without briefing docs
- **QA translations** against your approved terminology
- **Run delta localization** — only translate what changed
- **Enforce consistency** across multiple projects from a single ontology
- **Run fully local pipelines** for regulated industries

## Next steps

- [Black Ice + AI: What Your Ontology Unlocks](/docs/integrations/ai-integrations-overview) — model-specific workflows
- [Define your market rules](/docs/features/market-definitions) so AI models know your brand voice per locale
- [API & MCP rate limits](/docs/integrations/rate-limits)