Payment received

What happens next

1. We verify the subscription and paid invoice in Stripe.
2. We provision a bearer credential scoped to the published routes, tools, and quota.
3. Within one business day, expect an email from [email protected] containing a recipient-restricted, expiring credential link.
4. You run the supplied verification request and confirm receipt. We then delete the delivery link and our local plaintext copy.

Keep the credential private

Do not email the token, paste it into chat or support tickets, commit it to source control, or place it in client-side code. Store it as a server-side secret or in your password manager.

Do not send passwords, private keys, regulated records, or sensitive personal information through the API. Browser-local tools remain the safer path for sensitive one-off work.

Verification, rotation, and cancellation

Your delivery note includes one deterministic verification request. Rotation uses a short overlap window so the old and new credentials share one quota subject. Cancel through Stripe or email us; access continues through the paid-through date unless an immediate refund or security revocation applies. If a renewal remains unpaid, access ends when that paid-through date ends.

If you paid but do not hear from us within one business day, contact [email protected] from the Stripe receipt address. Never include a bearer credential or customer payload.

Read the HTTP and MCP onboarding guide before your credential arrives. The examples use an environment variable and never ask you to paste the credential into a browser.