⚙ Development environment — API behavior and data may change.

Access

Early access, by request.

Normatico is in a development phase. We onboard teams personally — no public price list yet, no credit card, no self-serve surprises. Tell us your use case and we'll set you up.

Sandbox

Evaluate the API on the dev environment. Full endpoint access, sample data, generous limits for testing.

✓All public endpoints
✓dev.normatico.com environment
✓Community support by email
Request sandbox key
MOST TEAMS
Production

For CRMs, email platforms, and products shipping to real users. Usage-based terms agreed during onboarding.

✓Production API keys & SLA
✓Verified-renderings cache
✓no_store privacy mode
✓Priority human review queue
Request access
Enterprise

Custom dictionaries, your own verified name sets, dedicated review capacity, and compliance paperwork.

✓Custom locales & standards
✓person_preferred overrides at scale
✓DPA, security review, provenance audit
Talk to us

Fair questions.

Why no public prices?
We're in dev. Usage patterns differ wildly between a CRM deduping 10M records and a newsletter greeting 50K readers — we'd rather price your case honestly than publish a grid that fits nobody.
What happens after I email?
A human replies (usually same day) with a sandbox key and a short call invite if your case is production-scale. No sales sequence.
Can we bring our own verified names?
Yes — person_preferred entries always win for that customer, and enterprise plans support custom dictionaries with your own review workflow.
What about privacy?
Under no_store, raw names are never persisted and never logged in production. Every rendering carries its source and license.

One email. A key within a day.

api@normatico.com