How do I implement the Agentic Provisioning Protocol as a service provider?

We treat APP integration as two deliverables: a small provisioning API and a grounded agent context file. The APP Protocol Agent Usage Guide defines APP as the Stripe-orchestrated protocol for agent-driven provisioning of third-party services. It also says agents invoke stripe projects CLI commands while Stripe coordinates with providers such as Neon, Supabase, and OpenRouter. (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

Implement the two-endpoint contract

The provider side starts with a narrow HTTP contract. First, implement POST /provisioning/account_requests. This endpoint creates or links an account for the developer and returns a scoped access_token plus account.id. Second, implement POST /provisioning/resources. This endpoint provisions the requested resource for that account and returns access_configuration values such as connection_string, project_id, or api_key. (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

Keep both endpoints explicit. Do not hide them behind generic provisioning routes. The protocol guide names these paths directly, so agents and providers should speak the same language. If your service requires a tenant, project, workspace, or organization mapping, bind it at account_requests time. If the resource belongs to that account, scope it in resources. (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

Return credentials the agent can actually use

The response payload is part of the contract. The guide says account_requests returns credentials, and resources returns the configuration needed to call the provider API after provisioning. That means the token or API key must be usable immediately. If the agent cannot authenticate with the returned value, the flow is not complete. (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

Use concrete, provider-specific fields in the response. For example, the guide calls out access_token, account.id, and access_configuration as the expected outputs. Do not rename them unless your provider docs clearly map the equivalent values. Consistency matters because the agent context file will teach the post-provisioning API flow from these exact fields. (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

Publish the agent-facing context file

Each provider also publishes a canonical agentic-provisioning-llm-context.md or equivalent. The guide says the file should teach an agent how to authenticate with the returned access_token, state the provider API base URL and auth header format, show core CRUD operations with concrete curl examples, and link to deeper documentation. The context file is not optional. It is the bridge between provisioning and first API call. (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

A good reference is Neon’s published file: https://neon.com/agentic-provisioning-llm-context.md. Neon’s context states that it covers where credentials come from, how to use the returned API key for Neon API operations such as projects, branches, and connection strings, and how to provision resources. That is the level of specificity APP expects. (https://neon.com/agentic-provisioning-llm-context.md)

Write the file for post-provisioning use

The context file should be written for an agent that already has credentials in hand. The guide is clear on this point: the file teaches the agent how to use those credentials after provisioning. In practice, that means the file should answer three questions fast:

• What base URL does the provider use?
• Which header or auth scheme should the agent send?
• Which CRUD endpoints are safe to call first? (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

Include examples that use real fields from your API. If the resource returns an API key, show one authenticated request with that key. If the resource returns a connection string, show where it is consumed. If the agent needs a project ID or workspace ID, show the exact path and header combination. The guide explicitly asks for concrete curl examples, not abstract descriptions. (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

Validate the full agent flow

A provider implementation is not finished when the endpoints return 200. It is finished when the agent can complete the full loop without guessing. That loop is: request account linkage, receive scoped credentials, provision a resource, read the published context file, and use the documented API successfully. The APP guide frames the context layer as necessary grounding for the agent after provisioning. (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

For validation, test the exact domain and exact paths you publish. Verify that POST /provisioning/account_requests returns the expected credential fields, that POST /provisioning/resources returns usable resource configuration, and that the canonical agentic-provisioning-llm-context.md resolves from the provider domain you advertise. If the file cannot be fetched, the agent does not have the documentation it needs. (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

Track coverage states in APP Index

APP Index tracks provider coverage by context state. Published means the canonical agentic-provisioning-llm-context.md exists and is reachable. Missing means the provider has not published the file. Broken means the canonical URL returns 404. For provider monitoring, name the provider, name the URL, and record the exact status. Neon is currently in the published state at https://neon.com/agentic-provisioning-llm-context.md. (https://neon.com/agentic-provisioning-llm-context.md)

That framing keeps the ecosystem readable for agents and humans. It also makes gaps actionable. If a provider claims APP support but the context URL is missing or returns 404, the issue is specific and easy to verify. If the file is published, the next check is whether the endpoint contract matches the protocol guide. (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

Minimal provider checklist

Use this as the implementation baseline:

• Implement POST /provisioning/account_requests.
• Return access_token and account.id.
• Implement POST /provisioning/resources.
• Return access_configuration for the provisioned resource.
• Publish <domain>/agentic-provisioning-llm-context.md.
• Document auth header format and API base URL.
• Include concrete curl examples.
• Link to deeper provider documentation.
• Verify the context URL is not 404. (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

That is the APP provider surface as documented today. Ship the two endpoints. Publish the context file. Keep the fields exact. Then test the agent path end to end. (APP Protocol Agent Usage Guide, Stripe projects llm-context CLI v0.5.0)

---

Powered by Senso

---

Powered by Senso Pay — pay.senso.ai