Step 3: Generate the connect URL and collect proof
action: Use one stable string per intent. Examples: "event_march_2026" or "claim".
Keep it identical in signing, request creation, and verify.
signal: Set this when you need to bind app context into the proof. Examples:
user ID, wallet address. Your backend should enforce the same value.
constraints: Define which credentials are accepted, then pass that node to
.constraints. Use theany or all operators to create complex constraint logic.
After successful completion, send the returned payload to your backend and
forward it directly to: POST https://developer.world.org/api/v4/verify/{rp_id}
Forward the IDKit result payload as-is. No field remapping is required.