FREQUENTLY ASKED QUESTIONS // KNOWLEDGE DIRECTORY

Clear answers for compliance officers and engineering teams.

Review detailed technical and operational answers regarding Diliguard data sourcing, API architecture, pricing models, and privacy safeguards.

Data Sources, Registries & Watchlists

Where does Diliguard source its intelligence data?

Diliguard connects directly to 16+ statutory government corporate registries (such as Companies House UK, Handelsregister Germany, SEC EDGAR US, and ACRA Singapore) and official regulatory endpoints. We do not purchase or resell stale third-party data broker lists. Every intelligence report cites the authoritative primary source with timestamped evidence.

How frequently are sanctions and watchlists updated?

Diliguard continuously monitors 140+ global watchlists and sanctions registries including OFAC, EU Consolidated, UK HM Treasury, and UN Security Council databases. The intelligence engine ingests regulatory amendments within minutes of publication, eliminating the standard 24 to 72 hour latency typical of legacy aggregators.

How does Diliguard handle foreign language corporate filings?

Our automated document processing pipeline extracts and normalizes unstructured corporate records across multiple languages including German, French, Spanish, Italian, Arabic, and Chinese into standardized English risk reports.

What open-source intelligence (OSINT) sources are inspected?

The OSINT engine cross-references official statutory gazettes, court records, global media archives, and verified corporate web footprints to identify adverse media, undisclosed relationships, and litigation risk.

Platform Capabilities & Entity Resolution

What is the difference between the Web Portal and Developer API?

The Web Portal at portal.diliguard.com is a graphic workspace designed for compliance officers, legal analysts, and investigators conducting manual deep dives. The Developer API exposes identical verification intelligence as structured REST JSON endpoints for engineering teams building automated onboarding and transaction screening pipelines.

Can Diliguard perform continuous monitoring after onboarding?

Yes. Diliguard supports both point-in-time verification during customer or vendor onboarding and ongoing portfolio monitoring. Automated risk sweeps can be configured to run daily or weekly, dispatching instant webhook alerts if a monitored entity receives a sanctions match, director change, or adverse media flag.

Does Diliguard support crypto counterparty risk alongside traditional KYB?

Yes. Diliguard provides unified risk scoring combining on-chain blockchain transaction graphs across Bitcoin, Ethereum, Solana, and EVM chains with corporate entity registries and beneficial ownership records.

How does Diliguard eliminate false positive screening fatigue?

Legacy compliance tools rely on simple name-string matching that triggers massive false positive volumes. Diliguard uses multi-factor entity resolution that cross-references tax identifiers, registration numbers, director biographical markers, and corporate ownership graphs to establish deterministic match confidence.

API Integration & AI Agent Skills

How long does standard API integration take?

The Diliguard REST API follows standard conventions and returns clean, typed JSON. Most engineering teams complete integration and sandbox testing within 1 to 2 business days. Comprehensive SDK guides and curl examples are available in our Developer Hub.

What callable endpoints and tools are available?

Diliguard provides 9 specialized endpoints and callable AI agent tools: Corporate KYB, Executive Person Trace, Crypto Asset Investigation, Third-Party Vendor Risk, Composite Fraud Prevention, AML Sanctions Screening, Direct Registry Checks, IP Intelligence, and Transaction Risk Scoring.

Is there a Model Context Protocol (MCP) server available?

Yes. Diliguard operates a dedicated Model Context Protocol (MCP) server that allows autonomous AI agents in Cursor, Claude Desktop, and LangChain environments to execute compliance tools directly via structured JSON-RPC protocols.

How are webhook alerts secured and verified?

All outbound webhook payloads are cryptographically signed using HMAC-SHA256 headers. Your application verifies the signature against your secret webhook key to guarantee payload authenticity.

Pricing, Credits & Commercial Tiers

How does credit pricing and query metering work?

Diliguard operates on transparent usage-based query credits. We offer Starter, Growth, and Enterprise subscription tiers with bundled monthly credits, as well as non-expiring credit top-up packs. Detailed pricing is available on our Pricing page.

Is sandbox testing available for engineering teams?

Yes. Every registered developer account receives immediate access to our sandbox environment with evaluation credits to test endpoints and validate payloads before deploying to production.

Are long-term contracts required?

No long-term commitments are required on standard subscription plans, which operate on flexible month-to-month billing. Custom annual agreements with volume pricing and uptime SLAs are available for enterprise clients.

Security, GDPR & Model Privacy

Are customer search queries used to train AI models?

Never. Customer queries, target identity parameters, and investigation artifacts are strictly isolated and are never used to train machine learning models or shared with third parties.

How are audit logs and data retention managed?

Clients can configure automated data retention policies to delete investigation records immediately after export or maintain them for statutory audit windows. Every query generates an immutable, timestamped audit log.

Where is data stored and processed?

Diliguard processes data on secure cloud infrastructure located in compliant European Union and United Kingdom regions. All network traffic is encrypted via TLS 1.3, and data at rest is secured with AES-256 encryption.

Have a specific compliance or technical question?

Speak directly with our technical team or explore our live developer documentation.