01
Vendor and subcontractor onboarding
A new sub or supplier record is created with a contact email and a website. That is the whole input a check needs, and it is already being typed.
For platforms
One email address in, one score out of 1,000 back, in about 10 seconds
VendorScore.ai reads the public record behind a vendor’s email address or website and returns a score with every reason named and sourced. This page is for software teams whose users are already typing that email address into a vendor or subcontractor record.
- 46
- Checks run since September 2, 2026
- 21
- Landed outside the clear band
- 5
- Public record types read per check
- v1.4
- Scoring model in production
Counts are live from the production database, not a projection.
Where this fits
Three places a score belongs in a payments workflow
02
A remit-to or bank-detail change
The most expensive moment in accounts payable. A check re-reads the record behind the email that asked for the change and shows what moved.
03
Pay application and invoice approval
Before a draw or an invoice is released, the approver sees the score and the reasons next to the amount instead of opening six browser tabs.
What a call returns
The same result the report page renders
- score
- One integer, 300–1000.
- band
- critical, caution, or clear — the three published thresholds.
- findings[]
- Each with a plain-language label, the reading, a pass / caution / flag / unread status, the record it came from, and when it was read.
- subject
- The email address or web address that was checked.
- model
- The scoring model version that produced the score.
Findings are never withheld by tier. How the score is built.
Stated plainly
What a check reads today, and what it does not
Read on every check
- Domain registration date, registrar, and registrant country, from the registry itself
- Mail configuration on the domain, including sender rules
- Whether the site loads, what it says, and how far its archive goes back
- Near-match spellings against known company names
- Free and disposable inbox detection
Not read, and not claimed
- Carrier operating authority, insurance, or safety history (FMCSA)
- Business registration or filings from any state or national registry
- Bank account or routing verification of any kind
- Credit files, litigation records, or lien data
- Anything inside an invoice document
Integration options
Three ways this could sit inside your product
Hosted link
A link from your record page to a report. Nothing to build, and the fastest way to see whether your users open it.
Embedded panel
The score and findings rendered inside your page, styled to fit. Your users never leave your product.
Direct API
Subject in, score and findings out, so the result can be stored on your vendor record and re-checked on a schedule.
None of these are published endpoints today. They are available on request, scoped in a conversation.
Want to see it against your own vendor list?
Send a note and it reaches one person, usually inside a business day. Run a check first if you want to see the output before you write.