E.epic.li
ContributeCreate

// Create a public profile

Prove the numbers. Keep the key private.

epic.li makes read-only requests to your selected revenue provider, then creates a public page with aggregate metrics and catalog labels. Add an optional private contact email, plus public website, app, and social links. Your email stays private; no account or password is needed.

// Source registry

One profile. 11 sources.

  • Stripe
  • Lemon Squeezy
  • Polar
  • Dodo Payments
  • Paddle Billing
  • RevenueCat
  • Superwall
  • App Store Connect
  • Creem
  • Whop
  • Razorpay

Provider keys stay private. Profiles store aggregate snapshots and public catalog names only.

Back to epic.li

// Profile setup

Your public page

No signup

1 · Payment gateway

2 · Create your read-only keyOpen Stripe and create the key
  1. 01Click this box. Stripe opens with a restricted key pre-filled with four read permissions.
  2. 02Confirm the four permissions are set to Read and everything else is None, then click Create key.
  3. 03Copy the rk_live_ key. Stripe shows it only once.
  4. 04Come back and paste it below.
Opens in a new tab · the whole box is a link

Only an rk_live_ restricted key is accepted. Never paste an sk_live_ secret key. The key is sent over HTTPS, encrypted before it is saved, and cleared from this form when submitted.

4 · About you

@

Lowercase letters, numbers, and hyphens. Changing this updates your public URL.

Stored privately for your records. This address is never shown on your public page.

Social profiles (optional)

Add direct HTTPS profile links. Only links on the selected platform are accepted.

// Required manual check

Review the key in Stripe Dashboard

Stripe does not return a restricted key's complete grant list through its API. The probes below check endpoint access only; they cannot detect extra permissions.

Confirm each listed permission is set to Read

Charges and refunds · Read

Subscriptions · Read

Plans and prices · Read

Products · Read

Only aggregate metrics and public catalog labels are saved. Customer records and raw provider responses are never stored or shown.