01 · Inputs
5
Signals
DNS, HTTPS, pages, contact, security
Trust intelligence API
Businesswebsitetrust. One API call.
Pre-screen domains, score website trust, and enrich business leads with explainable signals. Deterministic. Fast. Built for onboarding workflows.
- ●
No KYB / KYC claims
Pre-screening, not compliance.
- ●
Edge-cached worldwide
ms-class warm latency.
- ●
Explainable scoring
Insights with evidence.
● Worker · ms-class latency
request
curl https://api.zygentrust.com/v1/analyze?domain=example.com \
-H "Authorization: Bearer zt_live_..."import { ZygenTrust } from "@zygentrust/sdk";
const zt = new ZygenTrust(process.env.ZT_KEY);
const res = await zt.analyze("example.com");from zygentrust import ZygenTrust
zt = ZygenTrust(api_key=os.environ["ZT_KEY"])
res = zt.analyze("example.com")
200 OK
application/json
{ "domain": "example.com", "trust_score": 82, "risk_level": "low", "recommended_action": "approve", "confidence": 0.78, "insights": [ /* 2 items */ ]} Trust intelligence API
Businesswebsitetrust. One API call.
Pre-screen domains, score website trust, and enrich business leads with explainable signals. Deterministic. Fast.
● Worker · ms-class latency
request
curl https://api.zygentrust.com/v1/analyze?domain=example.com \
-H "Authorization: Bearer zt_live_..."import { ZygenTrust } from "@zygentrust/sdk";
const zt = new ZygenTrust(process.env.ZT_KEY);
const res = await zt.analyze("example.com");from zygentrust import ZygenTrust
zt = ZygenTrust(api_key=os.environ["ZT_KEY"])
res = zt.analyze("example.com")
200 OK
application/json
{ "domain": "example.com", "trust_score": 82, "risk_level": "low", "recommended_action": "approve", "confidence": 0.78, "insights": [ /* 2 items */ ]}- ●
No KYB / KYC claims
Pre-screening, not compliance.
- ●
Edge-cached worldwide
ms-class warm latency.
- ●
Explainable scoring
Insights with evidence.
02 · Output
1 score
Verdict
Risk · action · confidence — explainable
03 · Speed
ms-class
Latency
Cold ≤ 2s · warm cached at the edge
Built with the first wave of users.
ZygenTrust is in early access. These slots are reserved for the design partners and pilot users we are onboarding now — no placeholder logos, no fabricated quotes.
Design partner
Pilot user
Slot 3
Slot 4
Slot 5
Slot 6
Want this slot? Join the waitlist and mention "design partner" in your use case.
How it works
Signals to verdict,
Signals to verdict,
in one round trip.
Watch the analyze pipeline collect deterministic signals, then resolve to a trust score and a recommended action you can ship into onboarding.
- 01 · Domain risk Resolve and verify the domain
- 02 · Reachability Reach the website over HTTPS
- 03 · Trust pages Look for the pages real businesses publish
- 04 · Verdict Deterministic score, recommended action
01 · Domain risk
stage 1 / 4
Resolve and verify the domain
DNS over HTTPS for A, AAAA, MX. We confirm the domain is alive and that mail infrastructure exists before anything else.
- DNS A + AAAA resolves
- MX records 2 hosts
- Reverse path consistent
02 · Reachability
stage 2 / 4
Reach the website over HTTPS
We try HTTPS first, fall back to HTTP, and follow at most one redirect with a strict timeout. Cross-domain hops to abuse TLDs are flagged.
- HTTPS 200 OK
- HSTS max-age=31536000
- Redirect chain 1 hop, same host
03 · Trust pages
stage 3 / 4
Look for the pages real businesses publish
Privacy, terms, contact, and about. Six shallow probes, never recursive, never deeper than one click.
- /privacy found
- /terms found
- /contact found
- /about found
04 · Verdict
stage 4 / 4
Deterministic score, recommended action
Weighted rules and explainable insights — never a black box. You always see why.
Trust score 0
- Trust score 82
- Risk level low
- Action approve
- Confidence 0.78
How it works
Signals to verdict,
Signals to verdict,
in one round trip.
The analyze pipeline collects deterministic signals, then resolves to a trust score and a recommended action.
01 · Domain risk
Resolve and verify the domain
DNS over HTTPS for A, AAAA, MX. We confirm the domain is alive and that mail infrastructure exists before anything else.
- DNS A + AAAA resolves
- MX records 2 hosts
- Reverse path consistent
02 · Reachability
Reach the website over HTTPS
We try HTTPS first, fall back to HTTP, and follow at most one redirect with a strict timeout. Cross-domain hops to abuse TLDs are flagged.
- HTTPS 200 OK
- HSTS max-age=31536000
- Redirect chain 1 hop, same host
03 · Trust pages
Look for the pages real businesses publish
Privacy, terms, contact, and about. Six shallow probes, never recursive, never deeper than one click.
- /privacy found
- /terms found
- /contact found
- /about found
04 · Verdict
Deterministic score, recommended action
Weighted rules and explainable insights — never a black box. You always see why.
Trust score 0
- Trust score 82
- Risk level low
- Action approve
- Confidence 0.78
A single endpoint.
Five signal modules.
ZygenTrust collects deterministic signals across DNS, HTTP, trust pages, contact, and security — and turns them into an explainable score.
Domain risk
DNS + reachability
Resolves A, AAAA, and MX records via DNS over HTTPS. Verifies the website actually responds.
Website trust
HTTPS + redirects
Checks HTTPS, redirect chains, and flags cross-domain hops to high-risk TLDs.
Business enrichment
Pages + intent
Detects privacy, terms, contact, about, pricing, services, and testimonial signals.
Explainable
Insights, not vibes
Every score comes with insights, evidence, and a recommended action — not a black box.
Use cases
One call. Predictable JSON. Made to slot into onboarding, lead scoring, and merchant pre-screening pipelines.
SaaS
Onboarding pre-screen
Block obvious junk signups before they hit your trial pipeline.
Marketplace
Seller review
Quickly triage new vendor applications by domain trust.
Lead-gen
Lead scoring
Add a deterministic trust signal next to your firmographic data.
Agencies
Prospect filtering
Skip prospects whose websites lack the trust signals to support a deal.
Pricing preview
Free
Free
50 checks / month
Kick the tyres without a credit card.
- Trust score, risk level, action
- Up to 5 insights per check
- Test API keys (zt_test_*)
- Public OpenAPI access
Starter
$ 0 /mo
2.500 checks / month
For early-stage onboarding flows.
- Everything in Free
- Production keys (zt_live_*)
- Email support
- 24h analyze cache
Growth
$ 0 /mo
25.000 checks / month
For teams shipping merchant onboarding.
- Everything in Starter
- Priority queue at the edge
- Configurable cache TTL
- Slack onboarding channel
Pro
$ 0 /mo
100.000 checks / month
For platforms vetting at scale.
- Everything in Growth
- Dedicated support engineer
- SSO + audit log (when shipped)
- Early access to batch endpoint
Shipping notes
See full log What changed lately.
The last three things we shipped. Each line is one decision the team made — what changed, why, and where to read more.
Engineered for production
Edge-cached worldwide · ms-class warm latency Postgres-grade durability · ACID transactions Schema-validated end-to-end · Zod-backed contracts TS-strict by default · no any, no escape hatches Deterministic by design · no AI in scoring Explainable, not magic · every score has evidence Audit-ready logs · compliance-grade trail Bot-defended at the edge · request-time verification Edge-cached worldwide · ms-class warm latency Postgres-grade durability · ACID transactions Schema-validated end-to-end · Zod-backed contracts TS-strict by default · no any, no escape hatches Deterministic by design · no AI in scoring Explainable, not magic · every score has evidence Audit-ready logs · compliance-grade trail Bot-defended at the edge · request-time verification
Eight honest answers.
The questions we hear before sign-up. If yours is not here, hit the waitlist with it — we will reply on the same thread.
-
Is this KYB or KYC?
No. ZygenTrust is lightweight pre-screening for business websites — domain risk, trust pages, contact signals, security headers, and business intent. It is not identity verification, sanctions screening, or document-based KYB. It pairs well with a full KYB stack but does not replace one.
Link to this answer -
How is the trust score calculated?
Deterministic, weighted rules across DNS, HTTP, trust pages, contact, and security. No AI in the scoring path. Every score ships with a confidence value, evidence, and template insights so you can audit why a domain landed where it did. Full weights live in the public scoring rules document.
Link to this answer -
Can I configure cache TTL?
On the higher tiers, yes. Default cache TTL is 24 hours and applies to all tiers. Growth and Pro plans will accept a per-request TTL parameter when that gate ships. Cached responses still consume one quota check so billing stays predictable.
Link to this answer -
What about high-volume usage?
The API is built on an edge runtime with KV cache, so warm latency stays in the millisecond class regardless of volume. Per-key monthly quotas enforce billing, and per-IP rate limits are layered in for abuse defense. If you expect more than 100,000 checks a month, talk to us before signing up so we can scope the right plan.
Link to this answer -
Do you have GDPR or DPA support?
ZygenTrust is GDPR-aligned in how it handles data. A Data Processing Addendum is available on request — see the DPA page. Note that ZygenTrust intentionally does not store extracted contact details (no email or phone harvesting), so the DPA scope is narrow by design.
Link to this answer -
Is there a self-hosted option?
Not in the MVP. The API is delivered as a managed edge service. If you have a hard regulatory reason for self-hosting, mention it on the waitlist and we will keep your details for a future evaluation when an enterprise tier ships.
Link to this answer -
What happens when my quota runs out?
The API returns 429 with the QUOTA_EXCEEDED error code. Response headers include X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset (epoch seconds for the next monthly reset). Cached responses still consume quota — that is a deliberate billing decision so you do not get surprised by burst caching.
Link to this answer -
Is the roadmap public?
Yes. The product roadmap, frontend roadmap, and backend roadmap are all checked into the repo and updated session by session. The shared memory file logs every meaningful change with dated audit entries. Pricing, scoring rules, and the API design document are public too.
Link to this answer
How you will actually get access.
Three steps. No black box, no surprise pricing wall, no "contact sales" gate before you can see the API in action.
-
Today
Join the waitlist
Drop your email and use case. Mention the volume you expect and what you would replace ZygenTrust for. That context shapes who we onboard first.
-
Rolling early access
We send you a test key
Early access is rolling, not a fixed SLA. We onboard in small waves so feedback stays close. When your slot opens, you get a test key and a short brief on what is stable and what is still moving.
-
Day one
First analyze call in five minutes
One GET request returns a deterministic trust score, risk level, recommended action, confidence, signals, and explainable insights. No SDK to install. No webhook to configure for the first call.
Pre-production note: ZygenTrust is currently on a temporary preview domain. A custom domain, business email, and a public status page roll out together with the first paid plans.
Early access
Join the waitlist
Be the first to use ZygenTrust in production. We will email you when API keys are available for your plan.