# Amplitude extended agent setup reference > Account-to-first-event guidance for coding agents installing Amplitude. Use the maintained setup skill and current SDK documentation for implementation details; this reference does not duplicate platform SDK code or provide the full documentation corpus. For product discovery and pricing, use the [root index](https://amplitude.com/llms.txt). For the full documentation corpus, use [docs/llms-full.txt](https://amplitude.com/docs/llms-full.txt). ## Start with the maintained workflow - [Getting started](https://amplitude.com/docs/get-started) ([Markdown](https://amplitude.com/docs/get-started.md)): Account access, project selection, installation, and first analysis. - [Agent installation workflow](https://amplitude.com/install.md): Retrieve Amplitude's maintained integrating-amplitude skill through the CLI and follow its selected setup journey. - [CLI installation](https://amplitude.com/docs/developers/cli/install) ([Markdown](https://amplitude.com/docs/developers/cli/install.md)): Current prerequisites and installation methods. When the user asks you to install Amplitude, inspect the application, establish the target project and region, apply the appropriate integration, and verify a specific event. Preserve existing project conventions and avoid creating a duplicate Amplitude initialization. ## Establish the account and project 1. Reuse the user's existing Amplitude organization when available. Otherwise, direct them to [create an account](https://amplitude.com/get-started) and follow the [account guide](https://amplitude.com/docs/get-started/create-a-new-account) ([Markdown](https://amplitude.com/docs/get-started/create-a-new-account.md)). The user may need to complete sign-in or email verification. 2. Confirm US or EU data storage before creating an organization. The account guide explains the region choice and its implications. 3. Select the intended project, or follow [project creation](https://amplitude.com/docs/get-started/create-project) ([Markdown](https://amplitude.com/docs/get-started/create-project.md)). Confirm which product and environment the project represents. 4. Obtain the project's public ingestion API key and region from the user or existing application configuration. Instrumenting the application does not require a Secret Key. Private API credentials and access tokens belong outside client-side code. ## Choose the SDK and retrieve setup instructions For supported new browser applications with a JavaScript bundler, prefer the [Browser Unified SDK](https://amplitude.com/docs/sdks/analytics/browser/browser-unified-sdk/get-started) ([Markdown](https://amplitude.com/docs/sdks/analytics/browser/browser-unified-sdk/get-started.md)), `@amplitude/unified`. It combines analytics, session replay, feature experimentation, and guides and surveys through one initialization entry point. Use the [SDK catalog](https://amplitude.com/docs/sdks) ([Markdown](https://amplitude.com/docs/sdks.md)) for native mobile, cross-platform, server, and game-engine SDKs. Use the applicable browser installation guide for an analytics-only requirement, an existing integration, or a website without a bundler. Do not apply browser initialization instructions to a server or native app. Follow [install.md](https://amplitude.com/install.md) for the maintained CLI invocation and any required version pin. With a compatible installed CLI, retrieve the setup skill: ```sh amp skills get integrating-amplitude --region us ``` Use `--region eu` for an EU project. Skill retrieval requires no login. See [amp skills](https://amplitude.com/docs/developers/cli/commands/skills) ([Markdown](https://amplitude.com/docs/developers/cli/commands/skills.md)) for discovery and current command behavior. Read and follow the returned skill. The CLI supplies instructions and supported checks; the coding agent applies the application changes. Honor its prerequisites, supported surfaces, and documentation handoffs. Preserve the application's package manager, framework conventions, identity model, and consent requirements. For Browser Unified SDK installations, initialize once in browser code and configure the selected data region and requested products according to the current guide. ## Verify the expected event Run relevant application checks, trigger a meaningful test action, and confirm that its event reaches the intended project. Package installation or a successful build alone does not establish event delivery. Use the skill's documented verification path. The CLI supports two checks with different meanings: - Event-specific check: `amp events check-ingestion` can filter by event type and requires an authenticated credential with `analytics:read`. - API-key check: `amp events check-ingestion-by-api-key` needs no OAuth credential or PAT, but checks for any project events in the preceding eight hours. It cannot by itself prove that this implementation's chosen event arrived. For an authorized, authenticated event-specific check: ```sh amp events check-ingestion --project PROJECT_ID --event-type "Event Name" ``` Follow [CLI authentication](https://amplitude.com/docs/developers/cli/authentication) ([Markdown](https://amplitude.com/docs/developers/cli/authentication.md)) and the [event command reference](https://amplitude.com/docs/developers/cli/commands/events) ([Markdown](https://amplitude.com/docs/developers/cli/commands/events.md)). An inconclusive result is not confirmation of delivery or proof of failure. When an event-specific CLI check is unavailable, use [Debug Analytics](https://amplitude.com/docs/analytics/debug-analytics) ([Markdown](https://amplitude.com/docs/analytics/debug-analytics.md)) to confirm the expected event and properties in the intended project. Report any verification step that still requires the user. Installation is complete when the relevant application checks pass and the expected event is confirmed in the intended project. Report the selected SDK, changed files, event name, project, and verification evidence, or the specific remaining blocker. Do not include private credentials in the report. ## Continue to analysis when requested - [Create a chart](https://amplitude.com/docs/get-started/create-a-chart) ([Markdown](https://amplitude.com/docs/get-started/create-a-chart.md)): Answer a product question using the verified data. - [Amplitude MCP](https://amplitude.com/docs/amplitude-ai/amplitude-mcp) ([Markdown](https://amplitude.com/docs/amplitude-ai/amplitude-mcp.md)): Query account data and work with resources through OAuth. US: `https://mcp.amplitude.com/mcp`; EU: `https://mcp.eu.amplitude.com/mcp`. Discover current tools and use the intended project, date range, and filters. - [Docs MCP](https://amplitude.com/docs/api/mcp): Retrieve public documentation without authentication. This is a service endpoint, not a webpage. Use SDKs or the documented ingestion API for production event delivery. Amplitude MCP works with account data and resources; it is not an ingestion endpoint. ## Find more detail - [Build tutorial index](https://amplitude.com/build/llms.txt): Stack-specific implementation guides. - [Developer and agent index](https://amplitude.com/developers/llms.txt): CLI, SDKs, APIs, MCP servers, and skills. - [Documentation index](https://amplitude.com/docs/llms.txt): Product and technical references. - [Site inventory](https://amplitude.com/sitemap-llms.txt): Additional public corpsite pages.