Put the same check in your product

Define requirements in your product and enforce the result on your server. Proofable reuses existing proof before asking the user to verify again.

import { ProofableClient, defineGate } from '@proofable/sdk';

const client = new ProofableClient();
const gate = defineGate([{ verifierId: 'proof-of-human' }]);
const result = await client.gateCheck({
  gate,
  subject: { accountId: user.accountAddress },
});

if (!result.satisfied) throw new Error('Verification required');
await submitReview();

No dashboard or published listing is required.

Missing verification
SDK
API

Use Hosted Verify only when the server check reports a missing verifier.

import { getHostedCheckoutUrl } from '@proofable/sdk';

window.location.assign(
  getHostedCheckoutUrl({
    verifiers: ['proof-of-human'],
    returnUrl: 'https://app.example.com/callback',
  }),
);

Re-run the server check after the user returns. Pass mode: 'popup' and origin to keep people on your page. Hosted verification

npm install @proofable/sdk

Job	Method
Protect a page	`VerifyGate`
Check access on your server	`gateCheck`
Create proofs for a user who approved your app	`verifyFromApp`
Create agents for your users	`getHostedAgentCreateUrl`
Read a proof	`getProof`

JavaScript SDK

Call https://api.proofable.me from any language.

Need	Endpoint
Check inline requirements	`POST /api/v1/proofs/check`
Create a proof	`POST /api/v1/verification`
Read a proof	`GET /api/v1/proofs/{qHash}`
Load a gate	`GET /api/v1/profile/gates/{gateId}`

HTTP API and OpenAPI

What your users get

Your product needs	Proofable provides
Sign-in	Hosted passkey, wallet, and Google or Microsoft sign-in
Verified users	Checks that save reusable proofs
Agents for your users	An owner, identity, and permission proof for each agent
Access control	Verification UX in the browser; final decisions on your server
Payments	Visitor checkout and pay per call

Users keep their proofs. When they reach another product that accepts them, they don’t start over.

Who pays

Your app can sponsor usage, users can pay through a listing, and agents or APIs can pay per call with x402. Pricing shows who is charged in each case.

Keep credentials on the server

Access keys and other secrets stay in your backend. Call Proofable from there when you need more than the browser SDK exposes.

Server integrations

Create proofs from your backend.

Agents in the SDK

Create agents for your users with owner approval.

Overview

Use cases

Compare

Reference

Legal

Guides

Put the same check in your product

What your users get

Who pays

Keep credentials on the server

Next

Server integrations

Agents in the SDK

​What your users get

​Who pays

​Keep credentials on the server

​Next

Server integrations

Agents in the SDK

What your users get

Who pays

Keep credentials on the server

Next