> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pioneeroptimisation.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrate with your AI

> Hand the PIO integration to Claude Code, Cursor, or any coding agent, in one paste.

The prompt below hands the whole integration to a coding agent: install, credentials, code, run, verify. Paste it into an agent session opened in your Unity project's repository.

Before you paste:

1. Recommended: [connect the PIO MCP server](/ai/mcp-server) in the same agent, so it can fetch its own credentials and check its own work.
2. Otherwise, have the project's API key, account id, and project id from its settings page ready; the agent will ask you for them.

```text theme={null}
Integrate the PIO Unity SDK into this Unity project.

Fetch https://docs.pioneeroptimisation.com/ai/agent-integration-guide.md and follow it step by step. Every docs page is available as markdown by adding .md to its URL; the full page list is at https://docs.pioneeroptimisation.com/llms.txt.

If the PIO MCP server is connected, use it: whoami to choose the project, get_api_key for credentials, and check_integration after each run until it reports events arriving. If it is not connected, ask me for the API key, account id, and project id, and I will read the dashboard for you at each verification.

Stop and ask me at any step the guide marks as a hand-off. With the MCP server connected nothing blocks you; remind me instead to confirm the child-directed answer within 14 days if you create a project. Without it, action definitions and event-type registration are also mine. Never commit the API key.

You are done when check_integration reports the integration streaming events, or I confirm the dashboard shows them. Then tell me what you changed, the decision point you wired, and anything you needed that the docs or tools did not provide.
```

What to expect: the agent edits `Packages/manifest.json`, adds one bootstrap script, places one GameObject in your startup scene, runs the game, and verifies the result. It reminds you to confirm the child-directed answer if it created the project; without the MCP server it also stops for action definitions and event types.

This prompt is tested. An agent given only it and a fresh Unity project must complete and verify the integration unaided; the check runs before each SDK release.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.