Clerk through Squiid

What Clerk is

Clerk is authentication delivered as components. SignIn, SignUp, UserButton and OrganizationSwitcher are React elements you place in a layout, and the hosted flows behind them cover email and password, magic links, OAuth with the usual providers, passkeys, one-time codes and multi-factor. Sessions are managed with short-lived tokens and middleware for Next.js and other frameworks, organizations give you B2B team structures with roles and invitations, and the user profile UI comes with it. Webhooks report user and organization events, which is how a local users table stays in step with the identity provider.

For vibe-coded apps this is the part of the stack that punishes improvisation. Hand-rolled auth written by an agent tends to look correct and fail in specific ways: session fixation, tokens in local storage, password reset links that do not expire, no rate limit on login. Clerk moves those decisions to a vendor whose whole product is getting them right, and the components mean an agent produces a working, styled sign-in page in one pass. Impersonation and session revocation are also part of the product, which support teams ask for sooner than most plans expect.

Why connect it through Squiid

Clerk is on the Squiid roadmap. When it lands, Squiid will provision the application, hold the secret key and route backend calls through https://api.squiid.io/v1/clerk/... with Authorization: Bearer $SQUIID_API_KEY, with the SDKs working by base URL swap (gateway convention). The Pro plan passes through at $25 a month at Clerk's listed price with no Squiid fee, and monthly active user charges above the included allowance meter against prepaid credits at list on your single invoice.

• One account, one key, one bill, one dashboard. Clerk sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Clerk credentials. Your code carries SQUIID_API_KEY, so CLERK_SECRET_KEY, NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY, CLERK_WEBHOOK_SECRET never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Clerk costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned Clerk application with the secret held by Squiid
• Prebuilt sign-in, sign-up and profile components
• Social login, passkeys and multi-factor
• Organizations with roles and invitations
• Pro at $25 a month passed through at list price

How to connect Clerk

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces CLERK_SECRET_KEY, NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY, CLERK_WEBHOOK_SECRET
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/clerk/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Clerk charges a monthly plan fee plus per monthly active user above the included allowance, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Clerk usage, with no markup and no per-request margin.

Clerk Pro passes through at $25 a month at the provider’s listed price on your monthly Squiid invoice. Service subscriptions carry no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Clerk usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: users are exported from Clerk, with password hashes where Clerk supports it, and imported into an instance in your own account. Squiid never owns your code, your schema or your domain, and the gateway speaks Clerk's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Clerk through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Clerk usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.