Do not take SeenRelay on faith.
A freshness preflight sits close to validation, provider spend and agent decisions. That deserves scrutiny. SeenRelay is designed so you can begin with almost no trust: inspect the client source, install a zero-runtime-dependency package, run in shadow mode, keep your original validation path, and verify the live deployment and release evidence yourself.
Start with a wrapper that is easy to remove.
Trust should be earned after integration, not required before it.
Verify what you install and how it was released.
The client source is public and MIT-licensed. Automated package publishing is configured for registry Trusted Publishing/OIDC instead of long-lived publication tokens. Registry provenance or attestations should be checked for the exact version you install; a release process is evidence, not a substitute for reviewing the package.
Current client: v0.1.0 · 0 runtime dependencies.
npm install seenrelay # or pip install seenrelay Production commit: GET https://seenrelay.com/healthz
Production should be reproducible from enforced evidence.
Pull request -> required CI verify -> required isolated Preview Release Gate -> main -> Production.
verify check and the isolated preview-release-gate. Inspect the linked ruleset instead of trusting this sentence./healthz exposes the Production deployment SHA so an integrator can compare what is live with the public repository.SeenRelay reports observations. It does not ask you to outsource truth.
The service does not browse the fact source or use an LLM to decide truth. SAME_OBSERVED is evidence that matching observations exist within the requested window; whether that evidence is reusable remains your policy decision.
Billing is disabled in the current deployment. Current public access is free and requires no account. The current client cannot silently create a charge on your behalf.