insforge-integrations

This skill covers integrating third-party providers with InsForge. Currently two categories are supported: auth providers (RLS via JWT claims) and payment facilitators (x402 HTTP payment protocol). Each provider has its own guide under this directory. Auth Payment facilitators Each provider guide includes full code examples for: Refer to the specific references/ .md file for complete examples. Auth Payment facilitators (x402) Auth Payments (x402) - Provider signs or issues a JWT containing the user's ID - JWT is passed to InsForge via edgeFunctionToken in createClient() - InsForge extracts claims via request.jwt.claims in SQL - RLS policies use a requesting_user_id() function to enforce row-level security - Server returns 402 Payment Required with a JSON challenge base64-encoded in PAYMENT-REQUIRED header - Client signs an EIP-3009 authorization using the stablecoin's EIP-712 domain - Server forwards the signed payload to the facilitator's /verify + /settle endpoints - Server records the settled payment in an InsForge table with a realtime trigger for live dashboards - Clerk — Simplest setup; JWT Template handles signing, no server code needed - Auth0 — Flexible; uses post-login Actions for claim injection - WorkOS — Enterprise-focused; AuthKit middleware + server-side JWT signing - Kinde — Developer-friendly; built-in token customization - Stytch — API-first; session-based...