PROOFGATE developer platform

Build verification on sprime.us.

Use Sprime's existing keys, dashboard, docs, and sandbox to test privacy-preserving age and eligibility checks. sprime.io stays the buyer-facing PROOFGATE front.

Console and keys Create keys, inspect usage, and keep verification traffic on the developer platform.
Credential API docs Wire /request, /verify, and /session from the current /v1/credentials contract.
Live sandbox Exercise the browser credential flow against this host before production work.
OpenAPI spec Pin request shapes, response envelopes, and compatibility paths.

Buyer-facing PROOFGATE copy lives at sprime.io.

Zero PII
No name, DOB, ID number, or image stored
3 profiles
personhood, age_over_18, age_over_21
15 min
Short-lived session token window
2 formats
SD-JWT VC first, mdoc where supported
Developer Surface

The operational side of PROOFGATE stays on sprime.us.

Use this host for API contracts, key management, traffic inspection, and sandbox runs. The buyer story stays on sprime.io.

Request Credential challenge 
GET /v1/credentials/request?profile=age_over_18

Returns:
- nonce
- requestId
- client_id for this host
- response_uri for this host
Verify Wallet presentation 
POST /v1/credentials/verify

Checks:
- nonce is single-use
- aud matches the stored origin
- trusted issuer is pinned
- only the requested predicate passes

A successful response returns pass/fail plus a non-reversible audit token. It does not store raw identity data.

Integration Path

Wire the verifier in three passes.

01

Read the contract

Start with the credential API docs and OpenAPI spec. Confirm the exact request and response envelopes before coding.

02

Run the sandbox

Issue a challenge from this host and inspect how the wallet flow returns a presentation to the verifier.

03

Monitor production

Use dashboard traffic and API keys for test, pilot, and production verification calls.

Resources

Everything a developer needs to test the gate.

Credential API docs

Request a challenge, verify a wallet presentation, and check a short-lived session token.

Docs

Live sandbox

Run a browser credential challenge and inspect the verifier response from this host.

Sandbox

OpenAPI spec

Pin request bodies, response fields, and failure envelopes for client work.

Spec

Dashboard

Create keys, inspect usage, and keep operational work off the buyer-facing site.

Console

Developer guide

Review endpoint examples, demo calls, and current plan limits before production traffic.

Guide

Buyer surface

Use sprime.io for customer-facing PROOFGATE positioning, trust copy, and pilot conversations.

sprime.io
Pricing

Metered verification with a clear unit.

Start free in the sandbox. Move to a production plan when the host flow is live, then scale on a per-check rate.

Sandbox
$0
no card required
  • Credential request challenge
  • Sandbox verifier walkthrough
  • OpenAPI reference
  • Developer examples
  • Zero stored PII
  • No production SLA
Open sandbox
Popular
Production
$250
per month, includes 5,000 checks
  • Production API keys
  • 5,000 verifications included
  • $0.05 per additional check
  • Issuer allowlist controls
  • Zero-PII audit log
  • Integration support
Start production
Volume
Custom
for regulated volume
  • Higher-throughput verification
  • Customer audit exports
  • Issuer allowlist planning
  • Operational review
  • Contracted support
  • Launch coordination
Contact sales
FAQ

What developers ask before wiring the verifier.

What does the host receive?

The host receives a verification result, the requested claim profile, and a non-reversible audit token. Raw identity fields are not stored.

Which profiles are supported?

The current profiles are personhood, age_over_18, and age_over_21. Unknown explicit profiles return 400 instead of falling through to another gate.

How is the verifier origin bound?

The request endpoint stores the serving origin with the nonce. The verify endpoint rebuilds the expected audience from that stored origin before accepting a presentation.

Can I test without a compatible wallet?

The sandbox can still show the real challenge payload. It does not fake a successful wallet presentation.

Where should buyer-facing traffic go?

Use sprime.io for PROOFGATE positioning and pilot conversations. Use sprime.us for developer docs, keys, dashboard, and sandbox work.

What is sprime.us for now?

sprime.us is the developer platform for PROOFGATE. It carries console, keys, dashboard, docs, sandbox, and API contracts.

Building a PROOFGATE integration?

Start with the credential request docs, then use the sandbox and dashboard to verify traffic against this host.

Open credential docs →