For OTAs, airlines, baggage, insurance, and travel apps

Battery compliance checks for travel platforms.

CertiWatt helps platforms prevent battery-related travel surprises with embeddable, citation-backed verdicts for booking, baggage, insurance, support, and agent workflows.

Request pilot access View API surface

Pilot CTA clicks are recorded as anonymous operator signals; CertiWatt does not receive or store the prefilled email body. Privacy details.

Why partners use it

01
Power-bank and lithium-battery rules are no longer simple: country overlays, airline limits, active recalls, serial checks, label clarity, and onboard-use policies all matter.
02
When guidance is wrong or missing, the platform still receives the support ticket, complaint, baggage dispute, or unsafe-handling risk.
03
Partner teams need one embedded decision layer with the same cited answer, policy basis, ruleset version, and request-level audit trail.

Why a general AI answer is not enough

AI answer

CertiWatt embedded decision

General explanation of battery rules

Route, device, airline, and recall-aware verdict

No operational accountability

Verdict ID, ruleset version, timestamp, and source trail

Stale or generic recall guidance

Exact-model recall intelligence with optional serial evaluation

Answer outside the product flow

API response embedded in booking, baggage, insurance, support, and agent flows

Integration modes

Booking flow

Warn travelers before departure when a device needs airline approval, has recall risk, lacks clear label evidence, or may be banned.

Baggage flow

Prevent checked-baggage mistakes by surfacing carry-on-only constraints before the traveler reaches the airport.

Insurance flow

Add battery-related exclusions, warnings, and documentation before purchase or claim intake.

Support and agent flow

Give human agents and AI assistants a consistent verdict with sources, not a generic answer.

Pilot package

Start narrow: one workflow, one route corridor, and one measurable traveler decision. CertiWatt can return Trip Battery Pass verdicts before a platform-wide rollout.

Scope

Pick one corridor such as China to Singapore to the United States, one airline group, or one baggage-support workflow.

Integrate

Send device, route, airline, compartment intent, and optional serial evidence to /api/trips/verify or /api/verify.

Measure

Track warning views, blocked-risk cases, support deflection, baggage mistake prevention, and escalation outcomes.

Pilot success signals

Battery-related support tickets reduced or deflected
Travelers warned before airport arrival
Recall-risk cases surfaced with exact-model evidence
Baggage carry-on-only constraints shown before checkout or check-in
Support teams can cite verdict ID, ruleset version, and source trail

Request pilot access

Pilot CTA clicks are recorded as anonymous operator signals; CertiWatt does not receive or store the prefilled email body. Privacy details.

Pilot operating path

CertiWatt pilots move in controlled steps: scope, technical review, LOI if needed, kickoff, then production traffic only after agreement and integration gates are complete.

Scope-ready: One workflow, one business or technical owner, API path, final-authority copy, and a Day-60 metric are named before a pilot scope is sent.
LOI review: A lightweight LOI can document intent, but it does not grant production access, public announcement rights, SLA, indemnity, insurance, or liability transfer.
Kickoff gate: Post-LOI kickoff confirms owners, allowed origins, rate limits, failure-mode UI, audit export, and Day-30/Day-60 review dates.
Production traffic: Production credentials require the signed partner agreement, data-flow review, final-authority copy, failure-mode UI, and integration-readiness gates.

Pilot operating kit

CertiWatt runs partner pilots from a controlled operating kit: CRM snapshot, Week 1 send pack, pre-send safety checklist, and post-demo 24h advance plan. Cold outreach uses only the one-pager and public scorecard; pilot scope, legal packets, LOI, kickoff, integration readiness, API keys, and production traffic wait for the right stage gates.

Week 1 send pack: T0 and Day-5 messages stay owner-seeking and do not attach pilot-scope-template.md, partner-legal-packet.md, loi-template.md, pilot-kickoff-checklist.md, integration-readiness.md, or partner-pilot-instrumentation-spec.md.
Pre-send safety gate: Every partner email must clear role fit, CRM stage, next action, no competitor-evaluation claim, no airport/security acceptance, no public SLA, and no unapproved measurement endpoint promise.
Post-demo advance: A good demo does not jump to signed_loi. The 24h path classifies scope-ready, owner-missing, technical-review, legal-first, objection-heavy, or warm-pool outcomes before sending a packet.
Credential boundary: Partner API keys are production gates, not outreach assets. Credentials wait for partner agreement, allowed origins, rate limits, data-flow review, failure-mode UI, and integration-readiness gates.

Operating model for embedded decisions

CertiWatt is not a content widget. It is a decision service that lets a partner show, log, review, and escalate the same battery verdict across product and support surfaces.

Freshness window: Every Trip Battery Pass includes generated_at and expires_at so platforms know when to recheck before departure.
Audit trail: Partners can store verdict_id, trip_verdict_id, request payload, ruleset_version, and citations for support review and later audit exports.
Change intelligence: Policy-change access exposes source-watch counts publicly and deeper change history, fingerprints, and review signals for partner/authenticated access.
Serial responsibility: Exact-model recall checks can evaluate serial patterns locally; manufacturer-list cases return external_list_required and an official lookup URL.
SLA by agreement: Production response targets, support windows, allowed origins, rate limits, and responsibility terms are handled in the partner agreement.

What travels with every verdict

Verdict ID: Audit handle for support review, escalations, and later reporting.
Ruleset version: Shows which rule corpus produced the answer; unsupported historical pins return 400 instead of silently falling back.
Recall intelligence: Exact-model recall policy, verdict_impact, and serial_evaluation where evidence exists.
Citations: Regulator, airline, manufacturer, or recall source links for defensible traveler guidance.
Change signal: Tracked source changes, confidence, and review status for monitored airlines.
Final-authority notice: Clear boundary that airline and security staff decide.

Commercial path

Commercial boundary

CertiWatt is a cited informational verdict engine. It is not a regulatory certification, legal opinion, product approval, or guaranteed airport-security outcome.