Pick your handle
Check that epic.li/@you is free. Nothing is saved or reserved at this stage, and there is no email, password or account.
Open source · read-only keys · no screenshots
Connect a read-only key from your payment provider and get a public profile built from your provider’s own data, not a screenshot you can edit.
Works with Stripe, Lemon Squeezy, Polar, Dodo Payments and 7 more.
// How it works
Check that epic.li/@you is free. Nothing is saved or reserved at this stage, and there is no email, password or account.
Use a restricted Stripe key or a read-only credential from another supported provider. epic.li checks the read endpoints before anything is published.
Your public page shows aggregate metrics and product names. Keys and raw provider responses stay encrypted server-side.
// Why you can trust it
READ-ONLY REQUEST
Each provider has its own key and permission model. epic.li uses read scopes only and never asks for a full-access Stripe secret key.
MINIMAL DATA
Provider responses can include billing or contact details. epic.li encrypts raw responses server-side, publishes only aggregate metrics and catalog labels, and shows raw data only to the credential-verified profile owner.
NO ACCOUNT
A profile is created around a handle and an encrypted provider credential. Credentials are never shown on a public page or returned by the API.
// Stripe restricted key
Stripe does not expose a restricted key's complete grant list through its API. Endpoint probes confirm access only. Before publishing, the owner must review the complete key in Stripe Dashboard and attest that only these four read permissions are enabled.
Only charge/refund, subscription, plan/price, and product reads are requested. Connect-account and Files access are deliberately excluded; set them to None on an existing key or create a new key from this updated preset. Stripe responses can include billing or contact metadata; epic.li encrypts raw responses server-side and publishes aggregate metrics and public catalog labels only.