Built with the same evidentiary standard we apply to wallets.
VikingIntel handles investigation data for security teams, compliance teams, and protocols. The platform is built to a corresponding standard of access control and auditability.
API keys are hashed at rest. VikingIntel never stores or logs a usable copy of your key.
Protected API routes use a centralized authentication path, while public previews and signed webhooks use dedicated authorization mechanisms.
Cases, watchlists, and saved queries are scoped to the account that created them, with ownership checked on every request.
Usage is rate-limited atomically per key, so a spike in one integration can’t exhaust another tier’s throughput.
When a check cannot complete — pricing data unavailable, registry unreachable — the system denies or marks the result unknown rather than guessing. Consequential actions wait for a human regardless.
How VikingIntel handles public-source evidence.
VikingIntel enriches investigations with publicly available information. This section explains how that evidence is handled.
Found a security issue?
Please report it privately rather than opening a public issue — email gets the fastest response. Include reproduction steps and affected URLs where possible; we investigate and respond to every credible report.
Questions about security?
Non-vulnerability questions about data handling, access control, or integration security — reach out before you integrate at scale.