Create a proof

Use proofable_verify_or_guide as the normal trust path. It reuses a qualifying proof when one exists or returns the one next step needed to finish verification. Use proofable_verify when the signed-in account can complete a known check in-session and a new proof is actually needed. Ownership checks finish here. When a separate signer is required, call proofable_verify_prepare to get the exact signing string, then proofable_verify_submit with its signature and original timestamp. Preparation does not create a proof. Use proofable_proofs_check only when the user explicitly needs a yes/no eligibility, gate, or access answer. When signed in, omit walletAddress. The tool uses your profile account from proofable_context. For ownership-basic, omit owner. The signed-in account is filled in.

Input

Field	Required	Notes
`verifierIds`	Yes	One or more check IDs
`walletAddress`	No	Omit when signed in; required only when acting for another account
`data`	No	Check inputs (see each check)
`chain`	No	CAIP-2 chain when needed
`signedTimestamp`	No	Optional timestamp for direct creation or preparation
`options.returnUrl`	No	Where to send the user if a hosted step is needed
`options.publishToHub`	No	Record the proof on the hub chain. Offchain by default. Does not change who can see the proof. A background job’s request is refused (Proofs).

{ "verifierIds": ["ownership-basic"], "data": { "content": "Hello Proofable" } }

The direct tool does not ask for a signature. For a separate signer, pass the walletAddress, verifierIds, data, and chain used in preparation to proofable_verify_submit, together with the returned signedTimestamp and the signature over signerString.

Output

A plain-language Passed, Action needed, or Blocked result. On success, the tool also returns the proof ID in qHash for your server. proofable_verify_prepare returns signing details or a hosted fallback for an outside step.

Overview

MCP

JavaScript SDK

HTTP API

Verifier catalog

Standards

Input

Output

​Input

​Output

Input

Output