verapli
Sign inJoin free
Menu

Guides · auth · Everyday developer services

Stytch project and API keys

Create a Stytch project (Consumer or Multi-tenant/B2B) and copy the project ID and secret for the Test or Live environment.

Researched · not yet run liveLast researched 25 October 2026 · Stytch · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Sign up for Stytch

    The person signs up on the Stytch dashboard. verapli never creates the account.

    • Guided by hand
    • Human step: You press submit

    Where: https://stytch.com/dashboard

  2. Create the project

    Create a project and choose Consumer Auth or Multi-tenant (B2B) Auth; the type decides which API and SDKs apply.

    • Guided by hand
    • Human step: You press submit
    • After: Sign up for Stytch

  3. Copy project ID and secret

    In the Project & API keys section copy the project ID and secret for the Test environment (development) or Live (production). verapli captures the secret into STYTCH_SECRET.

    • verapli co-pilot
    • After: Create the project

    verapli captures STYTCH_SECRET here by plain code: encrypted in your browser, never shown to AI.

    Where: https://stytch.com/dashboard

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Worth knowingThe rules say

Test and Live have separate credentials and base URLs (test.stytch.com vs api.stytch.com); production must use Live keys. [1]

What you end up with

Env varSecretFormatWhat it is
STYTCH_PROJECT_IDnot secretProject ID for the chosen environment (Test or Live).
STYTCH_SECRETsecretProject secret for the chosen environment.

Pricing

  • Free tier: 10,000 monthly active users and AI agents, 5 SSO or SCIM connections, 1,000 M2M tokens.
  • Costs: Pay as you go beyond free; $125 per extra SSO/SCIM connection.

Source [4]

For agents

The same entry as JSON: /api/v1/entries/stytch/project · requirements /api/v1/requirements/stytch/project · terms /api/v1/terms/stytch/project.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Stytch project and API keys, and how long will it take?"
  → tools/call requirements { "provider_id": "stytch/project" }

Sources

  1. Stytch API overview project_id and secret from the Project & API keys section of the Dashboard, basic auth; Test environments use test.stytch.com and Live uses api.stytch.com. · accessed 25 October 2026 · official
  2. Stytch and backend development .env with STYTCH_PROJECT_ID and STYTCH_SECRET; use the project's live or any test credentials. · accessed 25 October 2026 · official
  3. Stytch Node.js quickstart Choice of Multi-tenant Auth or Consumer Auth, and Stytch UI, Headless or Backend only implementation. · accessed 25 October 2026 · official
  4. Stytch pricing Always free 10,000 monthly active users and AI agents, unlimited organizations, 5 SSO or SCIM connections, 1,000 M2M tokens; $125 per extra SSO/SCIM connection; no hard caps. · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Stytch is not affiliated with verapli.