Insforge Integrations

Wire Clerk, Auth0, WorkOS, Kinde, Stytch, or Better Auth into InsForge for JWT-based row-level security, or add OKX's x402 payment facilitator for onchain pay-per-use billing with USDG on X Layer. Each provider gets its own reference guide with full setup steps, from dashboard config to RLS policies. The auth side is cleanest with Clerk (JWT templates do the signing) or Better Auth (self-hosted in your own Postgres, no SaaS vendor). The payment side implements the full x402 flow: 402 response, EIP-3009 signature, facilitator verification, settlement, and a realtime-triggered payment table. Solid if you need third-party auth or metered API billing settled onchain.

skills.sh installs: 15.1K
GitHub stars: 30
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add insforge/agent-skills --skill insforge-integrations --agent claude-code

Installs into .claude/skills of the current project.

Files

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 Providers

Provider	Guide	When to use
Clerk	Clerk JWT Templates + InsForge RLS	Clerk signs tokens directly via JWT Template — no server-side signing needed
Auth0	Auth0 Actions + InsForge RLS	Auth0 uses a post-login Action to embed claims into the access token
WorkOS	WorkOS AuthKit + InsForge RLS	WorkOS AuthKit middleware + server-side JWT signing with `jsonwebtoken`
Kinde	Kinde + InsForge RLS	Kinde token customization for InsForge integration
Stytch	Stytch + InsForge RLS	Stytch session tokens for InsForge integration
Better Auth	Better Auth + InsForge RLS	Self-hosted auth running in your InsForge Postgres — no third-party SaaS, no per-MAU cost