Most apps add a gate and check the result on the server with gateCheck. Backends that create proofs directly, or automate your own profile, use the paths below.
Choose a path
Create proofs for approved users
After a user approves your app once, your server can create proofs for them without a signature on every request.
This needs:
- An active user approval for your
appId and site origin. App link
X-Proofable-App from appId and a matching Origin on each request. In Node, appOrigin sets both.
If the approval is missing, send the user through Hosted Verify first.
Automate as your profile
An access key identifies your builder profile for automation. Pass it as apiKey on the server. Creating proofs for other people still needs their approval. Access keys
Billing
Published gates are the default billing source. Pass gateId to hosted checkout and gateCheck, and Proofable resolves the owner, usage, and payment from that gate. appId is public attribution for server flows and does not bill your account by itself. Pricing
Next: API authentication Last modified on October 25, 2026