Toyota
Toyota Owner's Manuals and Warranty & Maintenance Guides
Use maintenance guide PDFs and owner manuals as the authoritative maintenance interval source.
keepitcorrect.org
Vehicle maintenance, made exact
We are building a maintenance intelligence platform for `2000-2026` vehicles using official manuals, government data, and an interval-first foundation that future services can trust.
First-release focus
26
Years of vehicles in scope13
Seed models ready to normalize13
High-trust source pathsVehicle entry points
Each model below now links into its vehicle coverage page, so you can move from the landing page directly into the parsed maintenance data we have so far.
Toyota
Toyota
Ford
Ford
Honda
Honda
Chevrolet
Nissan
Subaru
Mazda
Volkswagen
Hyundai
Kia
Trusted ingestion
The maintenance interval database should prefer sources that are official, government-backed, or clearly attributable. Dealer blogs and forum posts can help later, but they should not define the truth layer.
Toyota
Use maintenance guide PDFs and owner manuals as the authoritative maintenance interval source.
Ford
Primary source for normal and special operating schedules; scrape by make, model, and year.
Honda
Use manuals plus Maintenance Minder guidance where schedules are usage-based instead of static mileage tables.
General Motors
GM manuals and warranty booklets include brand-specific scheduled service requirements.
Nissan
Owner manuals and supplemental maintenance guides are the source of inspection and replacement intervals.
Subaru
Warranty and maintenance booklets are easier to normalize than full owner manuals for Subaru.
Mazda
Mazda exposes scheduled maintenance PDFs that are ideal for extraction into structured intervals.
Volkswagen
VW service resources centralize manuals and service intervals for later ingestion.
Hyundai
Manual and warranty resources cover schedule intervals, capacities, and severe-use caveats.
Kia
Use manual and guide PDFs to normalize service intervals across trims and powertrains.
Federal
Essential for tying maintenance guidance to safety campaigns, recalls, and active investigations.
Federal
Use VIN decoding to map a user vehicle to platform, engine, drive type, and exact service track.
Cross-brand
Annual and monthly OEM sales releases help decide which nameplates to ingest first for each brand.
Maintenance scope
The product should revolve around maintainable items, not generic specs. Every record should answer the same question: what should be inspected or replaced, at what interval, and under which driving conditions?
Track replacement and inspection intervals for the fluids that directly affect engine, brake, cooling, and drivetrain life.
Fluid neglect is one of the fastest ways to shorten component life, especially on engines, transmissions, and AWD systems.
Surface the wearable items that quietly reduce performance and efficiency long before a failure happens.
These items often look minor, but they affect fuel economy, drivability, emissions, and long-term engine health.
Separate lifetime-marketing language from practical service intervals for transmissions and driveline components.
Transmission and driveline repairs are expensive enough that even conservative service guidance can save owners thousands.
Keep recurring wear items visible so owners can prevent secondary damage and preserve safety.
Wear items compound. A small neglected part often creates a larger repair when its condition is not tracked over time.
API-first foundation
Keep the public shape simple: vehicles, service items, interval rules, operating conditions, and citations.
Pull interval truth from OEM manuals, warranty booklets, and government APIs before trusting community or dealer content.
Decode VINs to resolve platform, engine, drivetrain, and trim so interval guidance maps to the exact vehicle a user owns.
Center the system on service items, mileage/month thresholds, severe-use conditions, and citations that other tools can reuse.
Make the system understandable for non-mechanics with simple service intervals, severe-use warnings, and clearly sourced recommendations.
GET /api/maintenance
GET /api/maintenance?brand=Toyota&model=Camry
GET /api/maintenance?category=Fluids&condition=severe
GET /api/maintenance/categories
GET /api/vehicles
GET /api/vehicles/:brand/:model
GET /api/sources
GET /api/health
{
"vehicle": "Honda Civic",
"year": 2023,
"engine": "2.0L I4",
"schedule": [
{
"item": "Automatic transmission fluid",
"category": "drivetrain",
"intervalMiles": 30000,
"intervalMonths": 36,
"condition": "severe",
"action": "replace",
"source": "official manual",
"citationUrl": "..."
}
]
}Contract shape
The contract is now concrete enough for scrapers to target directly: a service item, an action, a vehicle fitment, a condition, and a citation. That keeps future ingestion and future products pointed at the same truth format.
{
"id": "2020-toyota-camry-coolant",
"brand": "Toyota",
"model": "Camry",
"year": 2020,
"engine": "2.5L I4",
"drivetrain": "FWD",
"itemId": "engine-coolant",
"action": "replace",
"condition": "both",
"intervalMiles": 100000,
"intervalMonths": 120,
"notes": "Preserve manual wording and repeat interval rules.",
"sourceName": "Toyota Owner's Manuals and Warranty & Maintenance Guides",
"citationUrl": "..."
}First seed set
The first release should concentrate on popular vehicles so interval extraction, QA, and API contracts harden on cars people actually own.
Toyota
Toyota
Ford
Ford
Honda
Honda
Chevrolet
Nissan
Subaru
Mazda
Volkswagen
Hyundai
Kia
Build sequence
Start with owner manuals, maintenance booklets, and OEM support portals. Use a per-brand extractor that can turn PDFs and pages into interval records with citations.
Map every interval to a service item, make, model, year, engine, drivetrain, and severe-use condition. VIN decoding becomes the matching layer for real users.
Expose a simple contract for fluids, wear items, transmission service, conditions, and citations so future services can build on top without scraping again.