Proofable Docs | Portable Trust Infrastructure

Checks cost credits. Your credits spend first. Visitors only pay when you turn on visitor checkout. Pricing has the amounts and the live estimator. Sign-in never costs credits. Credits apply when a check runs, a result is saved, or hosted AI is used.

How money moves on Proofable

Three lanes cover every flow. Most products only use the first.

Lane	Who pays	Use it for
You pay for checks	Your Proofable credits	Default. Checks through your gate bill your account
Charge visitors at a gate	Your visitor	Paid content and member access. Card or USDC at checkout
Charge per API call (metered)	The caller / agent	Metered APIs and agents that pay as they go (`x402`)

Default: you pay for visitor checks

When you publish a gate, you own it, so checks through that gate bill your Proofable account by default. Visitors embed or link your checkout with one public gateId:

<VerifyGate gateId="gate_your-app-name" />

There is no app ID or billing wallet to copy for this path. The gate carries the check policy and the payer.

Server checks

Confirm eligibility before you grant access with gateCheck. Pass the same gateId and the visitor’s account address (from Proofable sign-in or the saved result):

const result = await client.gateCheck({
  gateId: 'gate_your-app-name',
  address: user.accountAddress,
});

if (result.data?.gate?.allRequiredSatisfied !== true) {
  // Send the visitor back to Proofable sign-in
}

Charge visitors instead

A gate can charge visitors directly. Turn it on in the gate’s pricing step. Card: connect a payout account once from Profile → Payouts. Card payments for your paid gates then settle to that account. USDC checkout (optional): for products that already support stablecoin payers. Not required for account-based products. Until payouts are connected, paid gates offer USDC checkout only. Payment runs after verification by default. For the full checkout sequence, see Hosted Gate Checkout.

When your app creates agents for users

Agent setup creates two separately signed proofs. Billing follows the signer for each step unless a validated sponsor or pay-per-call proof is present.

Step	Default payer
Agent signs `agent-identity`	Agent account
Signed-in account signs `agent-delegation`	Signed-in approving account
Server signs with its own profile	Builder profile account
Valid sponsor grant	Sponsoring organization
Valid pay-per-call proof	Caller that bought the proof

For a dedicated agent account, create identity first, then send the user through the delegation-only hosted callback. See proofable_agent_create.

When credits run out

Billable calls return 402 with a quote. Pay per call with x402 (no account needed; see x402) or complete payment and retry with PAYMENT-SIGNATURE.

Advanced server integration

Server-side proof creation and per-user approvals use separate flows. See Integrations. Next: Pricing and x402

Ecosystem

Pricing & billing

Legal

Billing

How money moves on Proofable

Default: you pay for visitor checks

Server checks

Charge visitors instead

When your app creates agents for users

When credits run out

Advanced server integration

​How money moves on Proofable

​Default: you pay for visitor checks

​Server checks

​Charge visitors instead

​When your app creates agents for users

​When credits run out

​Advanced server integration

How money moves on Proofable

Default: you pay for visitor checks

Server checks

Charge visitors instead

When your app creates agents for users

When credits run out

Advanced server integration