Why rental history stays invisible
Peer-to-peer rental platforms operate outside the insurance reporting system. Trips are not accidents, so nothing flows into Carfax or AutoCheck. There is no mechanism for it, by design. A vehicle with 800 rental trips has 800 cold starts, 800 unfamiliar drivers, and a maintenance history nobody vouches for. The odometer does not capture that. The trip count does.
The registry
Rennsic holds a registry of peer-to-peer rental listings: the vehicle each one offered, the trips it recorded, the photos and market it showed, and the reviews renters left. A listing's trip count is the highest figure it ever showed, so a car that was later delisted keeps its history. The registry is rebuilt on a schedule and its aggregate figures are published on the insights page. A VIN search is the only way to check a specific car.
What a report contains
Submit a VIN and Rennsic decodes it against NHTSA data first, so you confirm the year, make, model, and trim before a credit is spent. A match returns the record:
- 1 Rental histories. Every listing of the VIN, grouped by owner, with the trips each carried and the potential distance those trips imply.
- 2 The listing. Market, first listing date, and the photos on file.
- 3 Usage comparison. Where the trip count ranks against the same make and model and against the whole fleet, from the registry's own statistics.
- 4 Renter-reported condition. The reviews behind the listing, read for mechanical and condition issues, presented as the count of distinct issues, the evidence behind it, and short quotes. No grade, by decision: the evidence is the answer.
The record lives on your console, exports as a PDF, and can be shared as a public page, so it can sit in an appraisal, go to a seller, or stay in the deal file.
What a result means
A match is documentary: the VIN appeared in a rental listing in the registry, with the trip count the listing showed. A no-match means the VIN does not appear in the registry as of the report date, within its coverage; the report still names the car so you can confirm the VIN was read correctly. Both results are charged. Both are answers. A VIN you have paid for re-runs free, for as long as you hold the account.
Console, API, agents
The console is the product for one VIN at a time. Pro and Dealer plans add a REST API, CSV export of your records, and the same checks for AI agents: a remote MCP server that Claude, ChatGPT, Cursor, and other MCP clients connect to with your account, and an agent skill that teaches an agent to spend credits carefully and read a result correctly. Every route draws on the same credit balance and obeys the same limits, so an agent cannot do anything your console could not. Details are on the API reference.
What we keep
Your searches are yours. They are never sold or shared, and they stay on your account for your plan's retention window. From renter reviews the report holds only the short excerpt that supports a finding, never a full review and never anything that identifies its author. The privacy policy has the rest.
Who uses it
Buyers running one VIN before an offer. Dealers screening trade-ins. Auction houses writing disclosures. Insurers and lenders pricing vehicles whose commercial use never made it into the file. Developers and agents pulling the same checks through the API.