[01]
sign up.
email, phone, or a bitcoin wallet you already use. no kyc, no waitlist. behind the scenes you get an oc identity, a federation-custodied lightning wallet, and an attest tier you can upgrade later.
§ me · ochk · io · v1 · accepting users
the bitcoin-backed online identity that pays you to use it.
sign into apps, pay through one identity, earn sats. federation-custodied by default, self-custody when ready. you pay nothing. integrating sites configure their own per-event prices and user-share splits; a meaningful fraction of every fee paid in your name flows to you, in bitcoin.
· sat-earning by default · federation-custodied · self-custody-ready · no token · no custody ·
§ network · livestreaming
payment authorized· fold
class B · action-bound · 4s ago
+780sats
session opened· damus
class C · session · 11s ago
+38sats
payment authorized· strike
class B · action-bound · 19s ago
+1,240sats
§ users earning · last 60s+150,234sats
aggregate across the integrating-site network
· synthesized stream · same shape as /me/earn · class A/B/C dots match the canonical taxonomy
§ sats earned · last 7 days
4,287,140sats
≈ $4,073 · across users on me·ochk·io
this counter aggregates sats credited to me·ochk·io users in the rolling 7-day window — across sessions, payments, verifications, and state transitions. each event is content-addressed and verifiable on /me/earn and on the public /api/stats/earned endpoint. no token, no points, no airdrop — these are sats.
§ how it works
three things happen, in order. the rest is the product.
[02]
use the apps you already use.
sites that integrate me·ochk·io accept your identity in one tap. each session, each payment, each verification creates a content-addressed envelope. the site pays the price it configured — oc keeps 20%, you earn the share the site set, the rest is the site's rebate. nothing hidden.
[03]
graduate when ready.
stay federation-custodied for the convenience of recovery, or graduate to self-custody by sweeping your sats to a wallet you control. the same oc identity works either way.
§ what your /me/earn looks like
/me/earn7 events · +2,441 sats net
payment authorized
class B · action-bound · 1d ago
+1,538sats
session opened
class C · session · 1d ago
+39sats
session opened
class C · session · 2d ago
+56sats
session opened
class C · session · 3d ago
+39sats
session opened
class C · session · 4d ago
+45sats
payment authorized
class B · action-bound · 5d ago
+704sats
session opened
class C · session · 5d ago
+20sats
§ what a site sees · oc envelope
envelope · oc-me-event · v1
{
"v": 1,
"id": "oc-me-7a3c9e2f",
"kind": "oc-me-event",
"class": "B",
"subtype": "payment_authorization",
"occurred_at": "2026-04-30T16:08:42Z",
"identity": "bc1q...e3lr",
"site": "breez.example",
"gross_fee_sats": 1280,
"platform_fee_sats": 448,
"user_earned_sats": 832,
"context": {
"payment_amount_sats": 240000,
"currency": "sat"
},
"sig": "ed25519:2b:fF9k...HpD1"
}§ how the loop closes
sites configure prices. oc takes 20%. you earn the rest.
no subscription fee, no per-click invoice, no app-tracking-app cross-graph. each integrating site sets its own per-event prices and chooses how much of the post-platform 80% flows to you — anywhere from 0% to 80%. OC operates the substrate; the configuration surface is yours.
for users
you earn sats every time you do something real.
- > account creation at a new site — one-time, varies by site (typical $0.30–$1.40).
- > sessions you open with sites you actually use — a few sats each, all day.
- > cashback on payments authorized through your oc identity — the dominant earnings line.
- > kyc upgrades, agent delegations, stamp signing, governance votes — high-trust actions earn more.
typical range: $5–$30/month, mostly cashback. amounts vary because each site picks its own. breakdown on /earn; per-site configs on /me/identity.
for sites that integrate
you set every price. oc takes 20%. user-share is yours.
- > per-session billing, not per-signin. signin within a valid session is free.
- > configure each event subtype: enabled / disabled, fixed sats or % of amount, user-share fraction.
- > sybil-resistance via attest tiers — anonymous, bonded, kyc-light, kyc-strong — at the gates you pick.
- > full developer telemetry on non-billable events. transparency is the trust model.
live configurator + drop-in code at /integrate; suggested defaults + sample configs at /pricing.
§ for integrators
why your saas, marketplace, or community should integrate.
every site asking users to sign in is already paying for something — auth seats, payment fees, sms 2fa, kyc verifications, fraud-rule subscriptions. integrating me·ochk·io reroutes those payments through a content-addressed protocol where a meaningful fraction flows back to your users as bitcoin cashback. you spend less than the legacy stack. users prefer the sat- earning button. fraud is priced out before it reaches your gates. verification continues forever, with or without us.
[01]
lower cost-of-goods than the stack you have today.
you're already paying for auth, payments, sms 2fa, and kyc. me·ochk·io is one bill that's smaller than the sum. cheaper than auth0 above ~3,000 mau. cheaper than stripe above ~$2k/mo volume. cheaper than twilio per text. integrate once, retire four invoices.
> at 10k MAU + $50k/mo payment volume, ~$3.4k/mo savings vs the legacy stack.
[02]
higher conversion at the sign-in button.
users overwhelmingly choose providers that pay them. the same way "fold pays sats on every purchase" beats "use your normal card", "sign in with oc" beats "sign in with email." the user gets paid, you get the conversion. nothing else changes.
> design-partner cohorts are seeing 18–32% lift in completed signups when oc is offered alongside email + apple + google.
[03]
sybil resistance that replaces your fraud rules.
attest tiers (anonymous · bonded · kyc-light · kyc-strong) are a property of the user identity, not your fraud rule engine. your gate just checks the tier. promotion abuse, fake-account farming, multi-account bonus extraction — the protocol layer prices each of these out of profitability before they hit you.
> see /security for the published abuse-rate-limit table. visible, public, and enforced.
[04]
no vendor lock-in. ever.
every receipt me·ochk·io issues — every sign-in, every payment, every kyc verification — is a content-addressed envelope you can verify offline against bitcoin headers, with or without us being online. the protocol is the api. if we get acquired, regulated, or hostile, your verification path keeps working.
> the public verifier is at /verify. JSON envelopes at /api/envelope/[id]. open spec at github.com/orangecheck.
§ cost comparison
the bills you retire when you integrate.
snapshot at a representative mid-stage saas profile (~10k monthly active users, ~$50k/mo payment volume, 200 kyc verifications/mo). your actual savings depend on session frequency, payment composition, and kyc tier mix — see /pricing for the full price bands.
| line item | legacy stack | me·ochk·io |
|---|---|---|
| sso · 10,000 MAU | $240/mo auth0 b2c starter | ~$70/mo sessions @ 0.05¢ each, ~140k/mo |
| payment fees · $50,000/mo volume | $1,750/mo stripe 2.9% + $0.30 × 1k transactions | $375/mo 0.75% lightning settlement, ~78% saved |
| sms 2fa · 10,000 logins/mo | $80/mo twilio @ $0.008/sms | $0 oc verifier replaces sms gate |
| kyc verifications · 200/mo | $300/mo $1.50/check at a vendor | $200/mo pass-through cost + thin margin |
| fraud / sybil rules engine | $500–$2,000/mo arkose, sift, internal | $0 attest tiers replace rules |
| monthly total | $2,870 – $4,370 | ~$645 · saves $2,200+/mo |
legacy ranges drawn from auth0 b2c starter, stripe standard, twilio sms, averaged kyc vendor pricing, and entry-tier sybil-rule tools. real invoices vary; we'll model your specific stack against your actual statements at /contact.
§ three pathways
five minutes, thirty minutes, or a conversation.
[01]
drop-in
time to integrate · ~5 minutes
paste a script tag and a button. for static sites, marketing pages, or "let me try this real quick" prototypes. all the session policy + scope wiring, none of the build setup.
see drop-in spec ↗<script src="https://me.ochk.io/sdk.js" async></script>
<button data-oc-signin
data-scope="identity,attest_tier"
data-session-policy="7d">
sign in with oc
</button>[02]
sdk
time to integrate · ~30 minutes
install @orangecheck/me-client. full session lifecycle (oc.session.create / refresh / invalidate), payment authorization (oc.payment.authorize), developer telemetry. typescript-typed against the canonical billable-event taxonomy.
sdk reference ↗yarn add @orangecheck/me-client @orangecheck/auth-client
import { OcSignInButton, oc } from '@orangecheck/me-client';
<OcSignInButton
scope={['identity', 'payment']}
sessionPolicy={{ duration_seconds: 7 * 86_400 }}
onSignin={(session) => yourSite.bind(session)}
/>[03]
co-branded · managed
time to integrate · a conversation
we operate a co-branded me·ochk·io instance on your domain (signin.yourcompany.com), with your logo, your session policies, your kyc requirements, your payment rails — built on the same protocol substrate. annual contract, dedicated support, deeper integrations.
talk to us →signin.yourcompany.com → oc·me protocol → bitcoin headers
# managed by you · operated by us · verified by anyone§ start integrating
first 1,000 sessions are free. flip a switch when you're ready.
sign up for a project key. ship the drop-in or the sdk. exercise all three event classes (account, session, payment) on a sandbox with mock cashback. flip prod when you're ready and start paying — and start paying your users.
§ the four no's
what we don't do is the product, too.
[01]
no token.
what you earn is sats — actual bitcoin — not a points balance, not an airdrop, not a proprietary unit. published on /charter as a binding commitment.
[02]
no custody.
the company never holds your funds. federation guardians hold custody collectively until you graduate to self-custody. one guardian among several, never the single custodian.
[03]
no cross-site tracking.
each integrating site verifies its own envelopes locally. me·ochk·io doesn't maintain a graph of which sites you sign into. that's the privacy distinction from sign in with google.
[04]
no kyc by default.
an email and phone get you a working oc identity. kyc is opt-in, only for premium events. pii lives with third-party verifiers, never with us.
§ start now
one identity, sat-earning by default.
sign up with email, phone, or a bitcoin wallet you already use. no token, no custody, no kyc required. graduate to self-custody whenever you're ready.