Open source · read-only keys · no screenshots

Claim your handle.Prove your revenue.

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.

claim_handle.exe

Lowercase letters, numbers and hyphens, up to 32 characters.

Nothing is saved or reserved yet. A handle is yours only after you connect a read-only key and it checks out.

Works with Stripe, Lemon Squeezy, Polar, Dodo Payments and 7 more.

// How it works

Three steps. No theater.

01

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.

02

Connect a read-only key

Use a restricted Stripe key or a read-only credential from another supported provider. epic.li checks the read endpoints before anything is published.

03

Share your proof page

Your public page shows aggregate metrics and product names. Keys and raw provider responses stay encrypted server-side.

// Why you can trust it

Don’t trust us. Read the code.

READ-ONLY REQUEST

Use least-privilege access

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

Aggregate, don’t publish customers

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

No login or signup

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.

Audit how keys are handled on GitHub

// Stripe restricted key

Requested permission set

Preset from Stripe URL
  • rak_charge_readREAD
  • rak_subscription_readREAD
  • rak_plan_readREAD
  • rak_product_readREAD

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.