Every finding has a reason.

Facts from FMCSA

Jibletto accepts a USDOT number and consults available FMCSA data. Every established field keeps the source name, the verification method and the time it was retrieved, together with publication time and freshness where the source states them.

One source. A check today consults FMCSA and nothing else. Jibletto does not claim multiple independent registries, and because only one source answers, no fact is cross-checked against a second one.

Certificate details your team enters

If you record details from a certificate of insurance or a carrier packet, you type the values from the document in front of you and confirm them before they are stored. They are kept as user-confirmed document claims: a person’s account of what a document said.

With manual entry, Jibletto has not seen the document.These values are never treated as document-verified evidence.

Optional ChatGPT certificate review pilot

When enabled, AI reads a certificate attached in ChatGPT and presents a draft with supporting excerpts. You review and correct the fields before confirming. The receipt retains both readings and corrections, the file fingerprint and the findings at confirmation. These remain user-confirmed document statements, separate from FMCSA facts. The extraction does not establish document authenticity or current insurance coverage. A file fingerprint identifies the bytes processed; it is not a carrier certification or a cryptographic seal.

Deterministic review findings

From those two inputs, Jibletto runs comparison and arithmetic only. No inference, no judgment calls.

• Does the USDOT number on the certificate match the carrier you checked?
• Does the insured name match the legal or operating name FMCSA reported?
• Has a date passed, or does it fall within thirty or sixty days?
• Which values were left blank?

Findings are graded critical attention, attention or watch. When none apply, the result isno issue identified in the submitted values. That is not a statement that coverage exists, is current, or was verified. A future expiration date is not proof that a policy remains in force.

Name matching uses explicit, testable rules. “Inc.” and “Incorporated” are treated as the same by written rule, never because a model judged them similar.

What Jibletto cannot verify

Jibletto does not contact insurers and does not confirm that a policy remains in force. A certificate records what a policy said when it was issued; it cannot show a cancellation the following day, and neither can Jibletto.

When you confirm an auto-liability policy number from a COI, Jibletto also checks FMCSA’s published Motus BI&PD filing data. When a matching filing is returned, Jibletto can compare the policy number, insurer name, filing effective date and published BI&PD amount. That is independent filing corroboration, not insurer confirmation.

FMCSA Motus is not complete enough to make absence a verdict. If a policy is not returned, Jibletto shows that as something to verify independently. It does not say the COI is false or that coverage is absent. Jibletto still does not contact the insurer, authenticate the certificate, confirm cargo coverage or prove that a policy is currently in force.

A source failure is never a carrier finding

If a government source times out or cannot be consulted, the affected field is reported as not established, with the reason. Jibletto does not describe a carrier less favourably because it could not retrieve data.

Comparison is a separate question

“How do we know this?” and “did the sources agree?” are different questions. Jibletto reports that no discrepancy was found only when a comparison actually occurred between two usable sources. One source cannot agree with itself, and an empty discrepancy list is not evidence of agreement.

Point-in-time history

A completed check is never rewritten when the world changes. A later lookup creates a new record, and the two can be compared to show which sourced values differ. A field the newer check did not establish is reported as exactly that, with the reason. It is not evidence that something about the carrier changed.

No score

Why we don’t offer confidence scores

Carrier records and insurance paperwork can tell different stories. Reducing them to one number can hide missing information, conflicting details or something that still needs confirmation. Jibletto shows what was checked, where the information came from and what needs attention, so your team can make a decision with the evidence in view.

Facts you can review. A decision you control.

Jibletto does not score, rank, approve, reject, certify, insure or recommend carriers, and there is no field in its output that means safe or unsafe.

No permanent, unappealable flags

Some carrier-vetting tools let one company file a private complaint or a “do-not-use” note against a carrier’s MC number that other companies then see, often with no way for the carrier to view it, dispute it, or learn it exists at all. Jibletto has no such mechanism, and cannot add one without abandoning §1 above: every fact Jibletto shows traces to a named federal source with a retrieval time, never to another account’s private report about a third party.

A carrier can check its own USDOT or MC number the same way a broker checks it. The free preview below shows the identical facts either would see, because there is nothing subjective to show differently.

Check a carrier