Choose a route
Compare research evidence, required inputs, user participation and access limits.
Build verification into
your next product.
Find country-specific requirements. Plan your integration.
Test the happy path and the failures before going live.
Research: 198 countries / territories · Sandbox: synthetic results · Live routes: 0
Start with your use case.
Research shows what a source documents. It does not mean GridZen has commercial access to that service.
No personal details or credentials needed.
Choose a country to beginSANDBOX / RESEARCH
Raw API response
API keys and codes remain unchanged. Research notes retain their source language.
No real provider is called.
Use it where you build.
Six task-focused Skills and a local MCP server. The local tools work offline after installation.
Integrate & test
Add a sandbox flow to your app with an HTTP API, Python SDK or Next.js example.
Explain a result
Keep missing data and provider failures distinct from a mismatch.
Mexico pilot scope
Draft owners, permissions and non-production limits; no pilot activation.
Payout policy draft
Design missing-evidence and provider-failure handling; no payment authorization.
Provider rights checklist
Identify contractual evidence gaps; no legal or compliance conclusion.
python -m pip install './gridzen-developer-kit[mcp]' gridzen plan --country ID --event payout gridzen simulate --country ID --capability bank_account_match --scenario timeout
Unzip the developer kit first. Python 3.11+ required. MCP launch command: gridzen-mcp.
Have a real verification use case?
Tell us your country, verification type and expected volume. We’ll evaluate an authorized route for your pilot.
Discuss a pilot