ChatGPT Plugin

AURIA Garage

Your car's history, in chat

Brand: Unknown

Category: Pending
Primary Subcategory: Auto Parts, Service & Vehicle Tools

Integration details

Description

AURIA Garage keeps a car's whole maintenance life in one place: service history, reminders, issues, parts and mods, fuel, mileage and diagnostic codes. This plugin brings it into ChatGPT. Ask plain questions and get answers from your own records: what is due or overdue on a car, worked out from its current mileage and today's date; what the car has cost this year, by service type, part category and month; how far you drive and what fuel costs you; whether a check-engine code has come back; or the full timeline of a car's history. Log work the way you would describe it. Say "I had the oil changed at the dealer at 84,200 miles" and ChatGPT adds the service record and the odometer reading. Log fill-ups by spending, quantity, tank level or range, record a scanner's codes, open an issue when something sounds wrong and resolve it when it is fixed, or set a reminder for the next service. You stay in control. You approve exactly what ChatGPT may do on AURIA's own consent screen, and you can disconnect it at any time from your Garage profile. Every entry it adds is permanently labelled as written by an AI assistant. It cannot delete anything: it adds new entries, and the only change it makes to an existing one is marking an issue resolved. Approvals last 30 days, and changing your password, signing out of all devices or changing how you sign in disconnects it within 15 minutes. To use it you need an AURIA account with at least one vehicle in your Garage.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Auto Parts, Service & Vehicle Tools
Secondary Subcategories: None listed
Brand: Unknown
Access: Account required
First tracked: 2026-11-05
Tool count: 19
Market: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Auto Parts, Service & Vehicle Tools

View Category

Listed in alphabetical order

Primary Subcategory

AnyRegComing soonGet notified

ARC Battery DiscoveryComing soonGet notified

AURIA GarageComing soonGet notified

AutoMotionComing soonGet notified

BookMyGarageComing soonGet notified

Tools

19 tools agents can invoke

Add an upcoming maintenance reminder, due on a date, at an odometer reading, or both. Unlike the other write tools this records nothing about the car's history — it is a to-do, so it creates no timeline entry.
add_reminder
Record work performed on the vehicle. This becomes a permanent entry in the car's history — it cannot be edited or removed through this server, and it may later be shown to a buyer. Only log work the owner has told you actually happened; do not infer it from a reminder being due. If the reading is higher than the vehicle's current odometer, the vehicle is updated to match. Pass codeReading when codes were read or cleared during the work, e.g. P0301 cleared after new plugs.
add_service_record
What one vehicle has cost: totals split between service and parts, a breakdown by service type and part category, and monthly spend. Amounts are in the vehicle's currency. Records logged without a cost are excluded and counted separately, so a low total can be read correctly rather than mistaken for a cheap car.
get_cost_summary
The life of each diagnostic code on one vehicle, derived from its readings: present, cleared with a tool, or went away on its own — and whether it came back. Answers questions like "has P0301 come back since the plugs were changed?".
get_code_history
How far one vehicle is driven and what fuel costs. Readings are merged from odometer logs, service records and refills into one series, so this works even if the owner never logs the odometer directly. Distances are in the vehicle's distanceUnit.
get_mileage_summary
One vehicle in full, with its open issues, reminders that are due or overdue, its most recent service, and any diagnostic codes still present. Read this before writing anything to the vehicle: it reports the distanceUnit and currency that every value you write must use.
get_vehicle
The vehicle's audit trail, newest first: every service, part, refill, issue and odometer reading as a single ordered history, including entries for records that were later edited or deleted. This is the best single view of what has happened to a car.
get_timeline
Every diagnostic reading for one vehicle, newest first: the trouble codes a scanner reported (with any freeze-frame values), or the warning lights that were on. A reading may be linked to an issue or a service record. For whether a code is still present, use get_code_history.
list_code_scans
Fuel purchases for one vehicle, newest first. Use get_mileage_summary for economy figures.
list_fuel_refills
Problems logged against one vehicle — symptoms and faults, as opposed to work done.
list_issues
Parts and modifications fitted to one vehicle, installed or since removed.
list_mods
Upcoming maintenance for one vehicle. Each reminder's status (overdue / due_soon / upcoming) is derived from the vehicle's current odometer and today's date, not stored.
list_reminders
Service and repair history for one vehicle, newest first by the date the work was performed. Costs come back both as the stored integer (costMinor) and formatted.
list_service_records
Every vehicle in the signed-in user's AURIA garage. Start here: all other tools take a vehicleId from this list. Archived vehicles and ones transferred to a new owner are not included. Note each vehicle's distanceUnit and currency — they define how odometer and cost values are interpreted everywhere else.
list_vehicles
Record what a scanner reported — the trouble codes — or, with method "dashboard", which warning lights were on. Link it to an issue or a service record when it belongs to one. Whether a code is present, cleared or gone is worked out from the readings, so a reading after a repair is how a code is shown to be gone. Appends a permanent timeline entry and does not change the vehicle's odometer. Record only codes a scanner reported or the owner read out to you. Never infer a code from a symptom — a misfire is not P0300 unless a scanner said so. Copy each code exactly as given; never translate a manufacturer code into a generic one. Use the description the scanner or the owner gave, and leave it empty otherwise — do not look one up. You may explain a code in conversation, but do not write your own definition into this permanent record. A scanner reading is the complete list of what the scanner showed: list every code it reported, not only the one being discussed. An active code the scan could see that you leave out is recorded as gone, so leaving one out is refused unless you pass it in confirmGoneCodes.
add_code_scan
Record a fuel purchase. Every entry needs the date and the total paid; entryMode says what else was measured: "volume_price" (the default) — the amount of fuel from the pump or receipt; "volume" — the amount of fuel added; "cost" — only the amount charged, e.g. from a bank statement; "tank_percentage" — the fuel gauge before and after; "remaining_range" — the dashboard's distance to empty before and after. Never turn a gauge or range reading into a volume. Volume unit is independent of the vehicle's distance unit — pass what was actually on the pump. Omit odometer when the owner does not know it rather than guessing; a reading higher than the vehicle's current odometer updates the vehicle. Appends a permanent timeline entry.
add_fuel_refill
Record the vehicle's current mileage. The vehicle's odometer only ever moves forward to the highest reading seen, so logging an older, lower reading records the reading without winding the car back. Appends a permanent timeline entry.
log_odometer
Log a problem the owner has noticed — a noise, a warning light, a fault. This is for symptoms, not for work done; use add_service_record for repairs. Appends a permanent timeline entry. Pass codeReading when a scanner was read, or a warning light seen, at the same time — it is saved as a reading linked to this issue.
open_issue
Mark an open issue as resolved. If a service record fixed it, pass its id so the fix is linked to the problem. Appends a permanent timeline entry. Resolving an issue does not change any diagnostic code's status: if a code went away, also log a scanner reading with add_code_scan that no longer lists it. A warning light going out is not enough — a dashboard-only reading never shows a code gone.
resolve_issue

FAQs

AURIA Garage ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve AURIA Garage's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are AURIA Garage alternatives on ChatGPT?

As of 2026-11-05, AURIA Garage competes with AnyReg, ARC Battery Discovery, AutoMotion, BookMyGarage, Calculadora de Combustível, Carparts.com, CarVault, CarWhere and 19 more in ChatGPT Auto Parts, Service & Vehicle Tools, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.