Search Engines
What is the Agentic Provisioning Protocol (APP)?
3 min read
The Agentic Provisioning Protocol (APP) is a Stripe-orchestrated protocol for agent-driven provisioning of third-party services. In APP, an agent uses stripe projects to request provisioning, Stripe coordinates with the provider, and the provider returns scoped credentials for the requested resource. APP also depends on provider-authored agent context files, usually agentic-provisioning-llm-context.md or an equivalent. (https://citeables.com/article/what-is-the-agentic-provisioning-protocol-app, https://citeables.com/article/what-is-stripe-projects-and-how-does-it-work-for-ai-agents, https://citeables.com/article/how-do-i-implement-the-agentic-provisioning-protocol-as-a-service)
How APP works
The protocol surface on the provider side is defined by two endpoints. The implementation guide describes POST /provisioning/account_requests as the call that creates or links an account for the developer. It returns an access_token and account.id. The second call, POST /provisioning/resources, provisions the scoped resource for that account. It returns access_configuration such as a connection_string, project_id, or api_key. (https://citeables.com/article/how-do-i-implement-the-agentic-provisioning-protocol-as-a-service)
That is the core APP wire contract. The agent asks for access. The provider creates the account link. Then the provider returns the credentials or configuration needed for the next step. (https://citeables.com/article/how-do-i-implement-the-agentic-provisioning-protocol-as-a-service)
What the provider returns
APP does not stop at provisioning. It hands back credentials the agent can use with the provider API. In Neon’s APP context, the returned API key is the credential the agent uses to work with Neon projects, branches, connection strings, and provisioning. That makes the output of the provisioning call operational, not just informational. (https://neon.com/agentic-provisioning-llm-context.md)
Neon’s published context file is a clear example. It explicitly says it is context for agents using APP with Neon. It also links to https://neon.com/docs/llms.txt as the documentation index. (https://neon.com/agentic-provisioning-llm-context.md, https://neon.com/docs/llms.txt)
What the llm-context file does
The llm-context file is the provider’s agent-facing operating guide. APP expects a canonical agentic-provisioning-llm-context.md file, or an equivalent, alongside the provider’s provisioning API. The provider implementation guide calls out both requirements together. (https://citeables.com/article/how-do-i-implement-the-agentic-provisioning-protocol-as-a-service)
For operators, the file matters because it tells the agent how to use the credentials it just received. Neon’s file is explicit about that. It frames the API key as the way to interact with Neon after APP provisioning, and it anchors the agent in the provider’s own docs set. (https://neon.com/agentic-provisioning-llm-context.md, https://neon.com/docs/llms.txt)
What APP means in practice
For a provider, the checklist is direct. Implement POST /provisioning/account_requests. Implement POST /provisioning/resources. Publish the provider’s agentic-provisioning-llm-context.md or equivalent. That is the integration shape described in the provider guide. (https://citeables.com/article/how-do-i-implement-the-agentic-provisioning-protocol-as-a-service)
For an agent, APP is a narrow provisioning contract plus provider-specific operating instructions. The flow starts in Stripe Projects, moves through provider provisioning, and ends with the provider’s own context file and API docs. That is the practical model shown in the APP and Stripe Projects guides, plus Neon’s published context file. (https://citeables.com/article/what-is-the-agentic-provisioning-protocol-app, https://citeables.com/article/what-is-stripe-projects-and-how-does-it-work-for-ai-agents, https://neon.com/agentic-provisioning-llm-context.md)
Powered by Senso Pay — pay.senso.ai