Choosing an integration method
Zyphe supports three main ways to put verification in front of a user. All of them share the same flows, results, and webhooks: you choose based on engineering effort, UX control, and how you want to operate the product.
At a glance
| Public link | SDK | Agent / MCP | |
|---|---|---|---|
| Setup time | Minutes | Hours | Minutes with an agent |
| Engineering | None–low | Low–medium | Low (AI-assisted) |
| User stays in your app | No (hosted UI) | Yes (embed or redirect you control) | Depends on what you build |
| Best for | Pilots, email/SMS invites, no-code launch | Production web or mobile UX | Automating setup and ops |
Do you need a working verification today with almost no code?
├─ YES → Public link
└─ NO → Do you need a native experience in your app?
├─ YES → SDK (browser, Node session creation, React Native)
└─ NO → Are you configuring the platform with an AI assistant?
├─ YES → MCP / agent tools
└─ Prefer API-driven ops → Node SDK + webhooks + dashboard
Public link
Each flow has a shareable URL. The user completes verification on Zyphe's hosted UI; your backend is notified via webhook and results appear in the dashboard.
Choose public link when:
- You need to start verifying users immediately
- Engineering capacity is limited
- You are running a pilot or proof of concept
- You distribute invites by email, SMS, or partner portals
How it works (high level):
- Create a flow in the dashboard
- Share the public link (or generate a session link from the server when you need per-user context)
- Receive a signed webhook when the result is ready
- Review the flow result (or automate with scoring)
→ Verification process: public web link · Sharing a flow
SDK
Use the SDK when you want control over session creation, branding in-context, or a native mobile experience.
| SDK | Role |
|---|---|
| Node | Create verification sessions server-side; generate links or tokens securely |
| Browser | Embed the verification UI in your web app (iframe) |
| React Native | Present verification in a mobile WebView |
Choose SDK when:
- Users should stay in your product experience
- You need server-side session creation with your own user IDs and metadata
- You are building production web or mobile onboarding
Typical production pattern:
- Backend creates a session with the Node SDK and an API key
- Frontend opens the session with the browser or React Native SDK
- Backend consumes webhooks and optionally polls or fetches result details via API
→ SDK overview · Verification process: SDK
Agent / MCP
Zyphe ships a Model Context Protocol (MCP) server so compatible assistants (Claude Desktop, Claude Code, Cursor, and others) can create and manage flows, forms, and API keys through natural language, authenticated with a bot token.
Choose MCP when:
- You want to scaffold or iterate on flows quickly
- Operators or developers already work with AI coding agents
- You are automating repetitive dashboard setup
MCP complements public link and SDK; it does not replace user-facing verification. Ship the integration with a link or SDK, and use the agent for configuration and maintenance.
→ MCP guide · LLM-friendly docs
What every path still needs
Regardless of integration method:
- A sandbox organization to test without production data. See Quickstart
- A flow that defines the steps the user completes
- A way to receive results: webhooks are recommended for production
- Clear roles so reviewers and developers only see the PII they need, Manage users · PII access control
Recommended next step
- New to Zyphe → Quickstart (public link or SDK, end to end)
- Already know you need embed → Browser SDK or React Native
- Automating setup → MCP