stripe projects llm-context). Service-specific guidance for cloud browser API keys is in Stripe Projects — browser API access.
Service catalog
Stripe service slugs are prefixed withkernel/ (from the app manifest name).
- Only one plan can be active per Kernel org at a time (
allowed_updatesdefines upgrade/downgrade paths). browser:api-accessis free when any active plan is provisioned; otherwise it is usage-based ($0.01/min standard, $0.02/min stealth).
Common CLI flows
stripe projects services list and copy the exact service slug from the output before stripe projects add — do not guess slugs.
Account and project mapping
Each Stripe Project maps 1:1 to a Kernel project within the org. Resources provisioned for a new
project_id create a Kernel project if needed.
Authentication
New accounts use the agentic credentials flow: afterstripe projects link / account request, Kernel returns bearer access and refresh tokens. Use stripe projects env --pull to load credentials locally.
- Dashboard (humans): https://dashboard.onkernel.com
- Existing Kernel customers with billing already on file may receive
payment_credentials: "provider"when linking to avoid double-billing.
Billing and Shared Payment Tokens (SPT)
Paid plans are charged through Stripe Shared Payment Tokens on the Metronome-managed Stripe customer.Full documentation
- Doc index for agents: https://kernel.sh/docs/llms.txt
- Create and connect browsers: https://kernel.sh/docs/introduction/create
- API keys: https://kernel.sh/docs/info/api-keys
- Pricing: https://kernel.sh/docs/info/pricing
- Cursor / Claude skills: https://github.com/kernel/skills