What problem does it solve? Agents working with the Agentic Provisioning Protocol (APP) need clear guidance on where Neon credentials come from and how to use the returned API key for Neon API operations like managing projects, branches, and connection strings. ## Core Features & Use Cases - APP Credential Handling: Explains how the orchestrator obtains a user-scoped API key from the account request response and how to send it as a Bearer token on every Neon API call. - Neon API Operations: Covers listing projects, creating branches with compute endpoints, and provisioning resources via the Neon REST API at console.neon.tech/api/v2. - Documentation Navigation: Provides a topic-indexed map of Neon docs (branching, autoscaling, connection pooling, Neon Auth, SDKs) with Markdown-fetchable links. - Use Case: When Stripe Projects provisions a Neon database for your app, use this Skill to authenticate with the returned access token, create a development branch, and retrieve the connection string. ## Quick Start Ask the agent to use the Neon API key from the APP account request to list your Neon projects and create a new branch with a read-write endpoint.