Investigative report
Single target
Narrative and structured findings for a vessel, company, counterparty or transaction.
- Evidence-linked conclusion
- Ownership and relationship maps
- Risk and confidence
- Analyst-ready output
Data delivery and APIUse Tevuna intelligence
Use Tevuna intelligence
inside the operating workflow.
Receive case reports, structured batches or schema-aligned API outputs with ownership, control, identifiers, evidence and risk.
Delivery models
One intelligence architecture across every scale.
The product and research depth remain explicit whether the output is a single report or a portfolio dataset.
Structured batch
Volume-based
Consistent fields and quality controls across vessel or entity lists.
- CSV or agreed structured format
- Entity identifiers and Tevuna IDs
- Field-level reasoning and references
- Defined refresh cadence
API integration
Custom
Input and output alignment for internal platforms and decision products.
- Schema mapping
- Request and delivery workflow
- Confidence and exception handling
- Operational support
Structured intelligence
Deliver more than a name and a flag.
- Canonical entity names and jurisdictions
- Company registration, IMO company, LEI and other available identifiers
- Direct and indirect ownership layers
- UBO or UCB conclusion
- Ownership percentages and dates where available
- Risk Y/N with explanation where included
- Source references, reasoning and confidence
Output schemaTRACEABLE
IdentityNames and identifiers
OwnershipAll required layers
ControlUBO or UCB
DATAstructured intelligence
RiskY/N and explanation
EvidenceReferences and reasoning
QualityConfidence and exceptions
Quality controls
Preserve what is known, inferred and unresolved.
Structured delivery should not hide evidence limitations or force ambiguous cases into false precision.
01
Entity resolution
Canonical names, identifiers and jurisdiction checks reduce duplicate and conflicting entities.
02
Evidence traceability
References and reasoning remain connected to the relevant entity or conclusion.
03
Confidence
Assessment reflects source quality, completeness, corroboration and contradictions.
04
Exception handling
Missing, inaccessible and analytically unresolved fields remain explicit.
Integration process
Align the intelligence to the receiving system.
- Define input identifiers and triggering logic
- Map Tevuna fields to the target schema
- Set required and optional outputs
- Define confidence, exceptions and retry behavior
- Test representative difficult cases
- Establish volume, cadence and monitoring rules
System workflowCONFIGURABLE
InputIMO, entity or case
RulesScope and product tier
SchemaRequired outputs
TEVUNAinvestigation
OutputReport, batch or API
QAValidation and exceptions
RefreshMonitoring cadence
Enterprise scope
Pricing follows volume, cadence and investigative depth.
Published per-vessel maritime prices apply to individual products. Batch, monitoring and API deployments are scoped around the full operating requirement.
Use a representative sample
Test the schema on difficult cases before deployment.
A mixed sample exposes evidence gaps, exceptions and mapping requirements before scale.