aigeon-ai/car-api2
car-api2 is hosted online, so all tools can be tested directly either in theInspector tabor in theOnline Client.
If you are the rightful owner of car-api2 and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
Car-API2 is a tool for accessing detailed vehicle information in the US, including a VIN decoder.
Try car-api2 with chat:
Tools
Functions exposed to the LLM to take actions
vindecoder
Decodes Vehicle Identification Numbers. The result will include a list of specifications in the specs property and a list of all possible trims matching the VIN in the trims property. For non-paying users, all VINs for 2015-2020 models (e.g. 1GTG6CEN0L1139305) will be returned, otherwise data is hidden. Paying users have full data access.
years
For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "make", "op": "in", "val": ["Scion", "Tesla"]}] Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed search fields are: year, make, model, trim, make_id, and make_model_id.
makes
Search makes by name and year.
models
Search models by year, make, model, trim or make_id. To include the models make in the description request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: `[{"field": "make", "op": "in", "val": ["Ford", "Acura"]}, {"field": "year", "op": ">=", "val": 2010}] Allowed json operators are: =, !=, >, <, >=, <=, in, not in, like, not like, not null, and is null. Allowed json search fields are: year, make, model, make_id, created, and modified.
trims
To include additional information about the returned body (such as year, make, model and trim) request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "year", "op": ">=", "val": 2010}, {"field": "year", "op": "<=", "val": 2020}] Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed json search fields are: year, make, model, trim, bodies.type, engines.cam_type, engines.cylinders, engines.drive_type, engines.engine_type, engines.fuel_type, engines.transmission, engines.valve_timing, engines.valves, make_id, make_model_id, make_model_trim_id, created, and modified.
bodies
To include additional information about the returned body (such as year, make, model and trim) request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "doors", "op": ">=", "val": 4}, {"field": "type", "op": "in", "val": ["SUV","Van"]}] See /api/vehicle-attributes for a complete list of vehicle attributes. Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed json search fields are: year, make, model, trim, type, doors, make_id, make_model_id, and make_model_trim_id.
engines
To include additional information about the returned body (such as year, make, model and trim) request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "horsepower_hp", "op": ">=", "val": 100}, {"field": "horsepower_hp", "op": "<=", "val": 300}] See /api/vehicle-attributes for a complete list of vehicle attributes. Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed json search fields are: year, make, model, trim, fuel_type, engine_type, transmission, drive_type, cam_type, valve_timing, valves, horsepower_hp, size, cylinders, make_id, make_model_id, and make_model_trim_id.
exterior_colors
To include additional information about the returned body (such as year, make, model and trim) request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "name", "op": "in", "val": ["red", "blue"]}] Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed json search fields are: year, make, model, trim, name, rgb, make_id, make_model_id, and make_model_trim_i
interior_colors
To include additional information about the returned body (such as year, make, model and trim) request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "name", "op": "in", "val": ["red", "blue"]}] Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed json search fields are: year, make, model, trim, name, rgb, make_id, make_model_id, and make_model_trim_i
vehicle_attributes
Returns all options for given attribute.
mileages
To include additional information about the returned body (such as year, make, model and trim) request with the query parameter as verbose=yes. For complex queries you may use the json field to send an array of URL encoded JSON conditions, example: [{"field": "combined_mpg", "op": ">=", "val": 20}, {"field": "combined_mpg", "op": "<=", "val": 30}] Allowed operators are: >, <, >=, <=, in, not in, like, not like, is null and not null. Allowed json search fields are: year, make, model, trim, combined_mpg, epa_city_mpg, epa_highway_mpg, range_city, range_highway, make_id, make_model_id, and make_model_trim_id.
Prompts
Interactive templates invoked by user choice
No prompts
Resources
Contextual data attached and managed by the client