Platform · Integrations
How Hullproof plugs into your stack.
CoatingPassport is the canonical data product. Nine channels (JSON, PDF, Cognite CDF, OSDU, RDF, DNV Veracity, EU ETS bundle, BIMCO biofouling, MCP) are derived from it — same source object, different shipping form. Click any channel for the live demo.
CoatingPassport JSON (canonical)
Enterprise APIThe schema-validated, versioned, machine-readable condition object that backs every other channel.
Why it exists. Output is structured data first, presentation second. Every renderer derives from this object.
What the payload carries
- asset metadata (asset_id, type, material)
- inspection context (timestamp, footage source, operator tier)
- findings array (severity, confidence, n_frames, image quality, source frames)
- compliance section (EU AI Act class, model card URI, lineage URI)
- history (versioned across inspections)
- interoperability (CDF / OSDU / Veracity / knowledge-graph flags)
Endpoint
/api/passports/{id}Buyers
CDO / AI team · Data product owner · Integration engineer
PDF report (human-readable)
Self-serveRendered passport for the technical superintendent, surveyor, or owner who wants a document.
Why it exists. Operators ship physical paperwork. PDF is the lowest-friction shipping format for that audience.
What the payload carries
- all findings with severity badges
- AI model version + inference timestamp
- per-finding confidence + frame counts
- source-frame references
- applicable standards per asset type
Endpoint
/api/passports/{id}/pdfBuyers
Technical superintendent · Class surveyor · Fleet manager
Cognite Data Fusion (CDF)
PlatformPassport exported as CDF Asset + Events records, ready for ingest into Cognite Data Fusion + Atlas AI.
Why it exists. One integration unlocks Aker BP, Equinor, and 15+ Cognite-native industrial operators. Atlas AI agents need the hull/vessel data layer they currently lack.
What the payload carries
- CDF Asset record (asset_id, type, material, metadata)
- CDF Event records per finding (severity, confidence, location, frames)
- time-series-ready timestamps
- asset hierarchy parent references
Endpoint
/api/passports/{id}/cdfBuyers
Aker BP · Equinor · Vår Energi · ConocoPhillips · Cognite-native industrials
OSDU (Open Subsurface Data Universe)
PlatformPassport exported as OSDU-compatible InspectionRecord + ConditionObservation records.
Why it exists. OSDU is the energy-sector data standard. E&P operators require OSDU compatibility for enterprise integration with their data platforms.
What the payload carries
- InspectionRecord (kind, version, acl, legal)
- ConditionObservation records per finding
- OSDU-canonical asset references
- master-data record IDs
Endpoint
/api/passports/{id}/osduBuyers
Equinor · Aker BP · ConocoPhillips · Shell / BP / Chevron via OSDU Forum
RDF / Turtle (knowledge graph)
Enterprise APIPassport as RDF triples for SPARQL endpoints, enterprise knowledge graphs, and semantic data layers.
Why it exists. Energy majors and shipping conglomerates build internal knowledge graphs. RDF export lets passport data join the semantic layer without bespoke ETL.
What the payload carries
- asset, inspection, finding triples
- standard ontology references (hullproof: namespace)
- severity / confidence / quality predicates
- source-frame URIs as RDF resources
Endpoint
/api/passports/{id}/rdfBuyers
Enterprise data architecture teams · Equinor Echo team · Knowledge-graph platform owners
DNV Veracity Data Exchange
Compliance bundlePassport packaged for upload to DNV Veracity Data Exchange — the DNV classification + assurance data marketplace.
Why it exists. DNV is a classification-society partner + distribution channel. Veracity-ready output lets Hullproof passports become first-class citizens in the DNV ecosystem.
What the payload carries
- Veracity-compatible asset + observation packaging
- DNV-RP severity mapping native
- class-society audit trail
- Veracity dataset metadata
Endpoint
/api/passports/{id}/veracityBuyers
DNV · DNV Veracity Data Exchange consumers · DNV-class operators
EU ETS / IMO CII compliance bundle
Compliance bundleAudit-ready evidence pack for EU ETS Maritime, IMO CII rating defense, Poseidon Principles, and FuelEU Maritime.
Why it exists. Vessel-hull and naval-hull operators face dual-regulator exposure (EU ETS + IMO CII + FuelEU). Hullproof emits the structured biofouling + condition evidence verifiers need.
What the payload carries
- biofouling extent + severity per zone
- fuel-burn proxy from hull condition
- verifier-grade source-frame lineage
- multi-regulator applicable-standards array
Endpoint
/api/passports/{id}/eu-etsBuyers
Maersk · Hapag-Lloyd · CMA CGM · MSC · Wallenius Wilhelmsen · EU ETS verifiers
BIMCO biofouling standard
Compliance bundlePassport mapped to the BIMCO digital biofouling assessment schema — reference implementation.
Why it exists. BIMCO is the standard-setter for shipping. Standard-conformant output positions Hullproof as the reference biofouling-assessment data product.
What the payload carries
- biofouling extent + severity per BIMCO zone
- fouling-condition rating per BIMCO scale
- next-clean recommendation per BIMCO guidance
- standard-version tag
Endpoint
/api/passports/{id}/bimcoBuyers
Maersk · Wallenius Wilhelmsen · BIMCO members · IMO secretariat readers
MCP (Model Context Protocol) tools
Enterprise APIHullproof exposed as a tool Claude / GPT / other LLM agents can call. Tool spec + JSON Schema published openly.
Why it exists. Agentic stacks are the next consumption layer. MCP-native means Hullproof is a tool agents reach for, not a UI humans navigate.
What the payload carries
- tool list endpoint (/api/mcp/tools)
- asset-type discovery endpoint
- CoatingPassport schema endpoint
- self-describing argument signatures
Buyers
Agent-builders · AI-platform teams · MCP-host operators
Need a channel that isn't listed?
CoatingPassport is the canonical object. New channels are renderers of it — not new data pipelines. If your stack speaks something specific (proprietary CMMS, internal data fabric, custom audit template), we add the renderer.