How Solidus Prices Identity Verification
The prices on this page are proposed commercial packages, not final contractual prices: that is the source's own status line, stated here first because everything below it should be read as a draft, not an offer. Nothing that follows is a case study. These are offer designs.
Three layers, three different jobs
Solidus prices in three layers, and they answer three different questions.
Layer 1, the protocol floor. The infrastructure story is meant to stay simple: $0.001 per credential verification, modeled, not measured against any running load, as the economic anchor underneath everything else. It exists to keep the floor visible for credibility, not to be the price anyone is quoted.
Layer 2, vertical business-event pricing. A business proof event is priced above that floor because it solves a workflow problem, not because it costs more compute. The suggested prices, unchanged from the source draft:
| Event | Suggested price |
|---|---|
| Age proof | $0.03–$0.05 |
| Hotel reuse | $0.05 |
| Travel reuse | $0.05 |
| SIM activation reuse | $0.05 |
| First hotel/travel/SIM verification | $0.10 |
| Driver/license check | $0.10–$0.25 |
| Delivery recipient/age proof | $0.05–$0.15 |
| Venue/ticket/age proof | $0.03–$0.10 |
| Fintech/CASP KYC reuse | $0.05–$0.25 |
| RWA investor eligibility | $0.25–$2.00 |
| Merchant KYB reuse | $0.25–$5.00 |
| Consent receipt | $0.001–$0.01 |
| Credential-gated API call | $0.001–$0.05 |
| Agent action verification | $0.001–$0.01 |
Two of these get their own page: hospitality/travel reuse in 112, RWA investor eligibility in 113, agent/API pricing in 118.
Layer 3, SaaS plans. The console and support wrapped around the per-event pricing:
| Plan | Price | Buyer |
|---|---|---|
| Developer | Free–$99/month | Builders, testing, hackathons |
| Team | $299–$999/month | Startups and small vendors |
| Business | $2,500–$5,000/month | SaaS vendors, marketplaces, multi-location operators |
| Enterprise | $50K–$250K/year | Telcos, fintechs, CASPs, large platforms |
| Private deployment | $100K–$500K/year | Banks, governments, strategic infrastructure |
| Integration sprint | $5K–$75K one-time | Serious pilots and enterprise integrations |
The full plan-by-plan packaging (what's actually in Developer vs. Business vs. Enterprise) is 115. Private deployment gets its own page at 117; the integration sprint line at 116.
The honest asymmetry: more expensive first, cheaper after
The layered model above prices events. A separate, worked comparison, drawn from a different reference (the tokenomics KYC-tier fee schedule, not the GTM table above), makes the reuse argument concrete, and it starts with the unfavorable number, not the favorable one: a first Solidus KYC Level 2 check is priced at $5.00, against a roughly $1.50 incumbent re-check the source models for the same tier. On a single first-time check, Solidus is the more expensive option, full stop, no hedge.
The case for reuse only shows up over multiple checks. At a modeled $0.05 per reuse event, Solidus's running total ($5.00 + $0.05 × n) crosses below the incumbent's flat-rate total ($1.50 × (n+1)) at roughly n ≈ 2.4, around the third or fourth total identity check for the same person, assuming a relying party actually accepts the reused credential instead of re-running its own check. That assumption is unproven in production. The full arithmetic, with every caveat it depends on, is 111; the underlying cost-per-verification, re-verification-cost, and total-cost-of-ownership Lexicon entries carry the full-strength version of this same concession.
Distribution has a price too
Software vendors that carry Solidus inside their own workflow, a POS, a PMS, a telco billing system, can take a revenue share of 10–50% of proof revenue depending on volume and strategic value. That mechanism, and why it's structured to turn integrations into distribution rather than a simple reseller discount, is 114.
What this page is not
Not a rate card in force. Not a quote. The rest of this track works through the pieces one at a time: the break-even math in full (111), two priced verticals (112, 113), the packaging and pilot-cost detail (115, 116), private deployment (117), machine-to-machine pricing (118), and the funding questions this pricing model sits inside, whether a token exists (119) and why grants come before a priced round (120).