Apibara Vehicle Auction Data

Search auction vehicles

search_auction_vehicles

Read-onlyIdempotent

Use for broad inventory discovery, filtering and incremental synchronization across supported Copart and IAA / IAAI records. For one known VIN or lot use get_vehicle; for retained auction appearances use get_vehicle_history.

Input Schema

TableJSON Schema

Name	Required	Description
`s`	No	Search by VIN, lot number or vehicle title/model text.
`zip`	No	ZIP/postal code used with radius for supported proximity search.
`make`	No	Make filter for GET /vehicles.
`type`	No	Vehicle type filter for GET /vehicles.
`color`	No	Color filter for GET /vehicles.
`model`	No	Model filter for GET /vehicles.
`units`	No	Distance and odometer unit system: mi or km.
`cursor`	No	Opaque pagination cursor returned by the API. Send next_cursor back unchanged; do not decode or synthesize it.
`damage`	No	Primary damage category filter.
`radius`	No	Search radius around zip, interpreted using the selected units.
`series`	No	Series / model family filter for GET /vehicles.
`has_key`	No	Key-availability filter using the documented values No, All or With.
`year_to`	No	Year to filter for GET /vehicles.
`per_page`	No	Requested page size. Effective maximum is subscription-plan dependent; common public plan limits are 20, 30 or 40 and custom plans may differ.
`platform`	No	Readable auction-source selector: copart or iaai. Omit for combined supported sources.
`run_cond`	No	Normalized run-condition filter.
`upcoming`	No	Upcoming selector: all=no upcoming restriction, only=upcoming eligible lots only, without=exclude upcoming lots.
`body_type`	No	Deprecated compatibility alias for body_style. A string or array is accepted; prefer body_style for new integrations.
`cylinders`	No	Cylinders filter for GET /vehicles.
`fuel_type`	No	Fuel type filter for GET /vehicles.
`loc_state`	No	Auction location state or region, for example FL.
`price_max`	No	Price max filter for GET /vehicles.
`price_min`	No	Price min filter for GET /vehicles.
`year_from`	No	Year from filter for GET /vehicles.
`body_style`	No	Filter by vehicle_specs.body_style. A string or array is accepted; multiple values are OR-ed. IAAI uses VehicleClass and Copart uses the source-backed Body Style field.
`drive_type`	No	Drive type filter for GET /vehicles.
`generation`	No	Generation filter for GET /vehicles.
`lot_status`	No	Auction mode filter: All, Timed or Buy Now.
`today_only`	No	When true, restrict results to the endpoint current-day auction logic.
`engine_type`	No	Engine type filter for GET /vehicles.
`facility_id`	No	Auction facility identifier used to restrict results to one supported facility.
`odometer_to`	No	Odometer to filter for GET /vehicles.
`office_name`	No	Auction office or branch name filter.
`seller_type`	No	Normalized seller type: dealer, finance, insurance or non_insurance.
`auction_type`	No	Numeric compatibility source selector: 0=all, 1=Copart, 2=IAAI. If both auction_type and platform are supplied, auction_type takes precedence; prefer platform for new integrations.
`transmission`	No	Transmission filter for GET /vehicles.
`generation_id`	No	Generation ID filter for GET /vehicles.
`include_total`	No	Include exact total filter for GET /vehicles.
`odometer_from`	No	Odometer from filter for GET /vehicles.
`engine_size_to`	No	Engine size to filter for GET /vehicles.
`lot_sub_status`	No	Normalized auction state: Open for active/open lots, Live for currently live supported lots, Ended for closed/ended lots.
`auction_date_to`	No	End auction date in YYYY-MM-DD format.
`engine_size_from`	No	Engine size from filter for GET /vehicles.
`auction_date_from`	No	Start auction date in YYYY-MM-DD format.
`has_shipping_price`	No	When true, return only vehicles with supported shipping-price data.
`sale_document_type`	No	Sale/title document type filter; values are source-backed and can vary.
`sale_document_pending`	No	When true, restrict results to records with a pending sale document state when supported.
`updated_within_minutes`	No	Incremental-sync window. Return records whose updated_at changed within this many minutes; supported range is 1..525600. Use with cursor pagination and an overlap window.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`meta`	No	Pagination metadata. Treat cursor values as opaque.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 28, 2026

addedInput schema / properties / body_style

Added value: +{
+  "description": "Filter by vehicle_specs.body_style. A string or array is accepted; multiple values are OR-ed. IAAI uses VehicleClass and Copart uses the source-backed Body Style field.",
+  "oneOf": [
+    {
+      "type": "string"
+    },
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  ]
+}

addedInput schema / properties / body_type

Added value: +{
+  "description": "Deprecated compatibility alias for body_style. A string or array is accepted; prefer body_style for new integrations.",
+  "oneOf": [
+    {
+      "type": "string"
+    },
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  ]
+}

Changed4 schema fields changedSep 25, 2026

removedInput schema / properties / engine_hp_from

Removed value: -{
-  "description": "Engine HP from filter for GET /vehicles.",
-  "type": "string"
-}

removedInput schema / properties / engine_hp_to

Removed value: -{
-  "description": "Engine HP to filter for GET /vehicles.",
-  "type": "string"
-}

addedInput schema / properties / engine_type

Added value: +{
+  "description": "Engine type filter for GET /vehicles.",
+  "enum": [
+    "I",
+    "V",
+    "W",
+    "B"
+  ],
+  "type": "string"
+}

addedInput schema / properties / include_total

Added value: +{
+  "description": "Include exact total filter for GET /vehicles.",
+  "type": "boolean"
+}

Changed2 schema fields changedSep 25, 2026
- changedInput schema / properties / engine_hp_from / type
```
Previous value: -"number"New value: +"string"
```
- changedInput schema / properties / engine_hp_to / type
```
Previous value: -"number"New value: +"string"
```

Changed1 schema field changedSep 24, 2026

addedInput schema / properties / series

Added value: +{
+  "description": "Series / model family filter for GET /vehicles.",
+  "type": "string"
+}

Changed2 schema fields changedSep 23, 2026

addedInput schema / properties / generation

Added value: +{
+  "description": "Generation filter for GET /vehicles.",
+  "type": "string"
+}

addedInput schema / properties / generation_id

Added value: +{
+  "description": "Generation ID filter for GET /vehicles.",
+  "type": "string"
+}

Changed45 schema fields changedSep 22, 2026

addedInput schema / properties / auction_date_from

Added value: +{
+  "description": "Start auction date in YYYY-MM-DD format.",
+  "format": "date",
+  "type": "string"
+}

addedInput schema / properties / auction_date_to

Added value: +{
+  "description": "End auction date in YYYY-MM-DD format.",
+  "format": "date",
+  "type": "string"
+}

addedInput schema / properties / auction_type

Added value: +{
+  "description": "Numeric compatibility source selector: 0=all, 1=Copart, 2=IAAI. If both auction_type and platform are supplied, auction_type takes precedence; prefer platform for new integrations.",
+  "enum": [
+    0,
+    1,
+    2
+  ],
+  "type": "integer"
+}

addedInput schema / properties / color

Added value: +{
+  "description": "Color filter for GET /vehicles.",
+  "type": "string"
+}

addedInput schema / properties / cursor / description

Added value: +"Opaque pagination cursor returned by the API. Send next_cursor back unchanged; do not decode or synthesize it."

addedInput schema / properties / cylinders

Added value: +{
+  "description": "Cylinders filter for GET /vehicles.",
+  "type": "integer"
+}

addedInput schema / properties / damage

Added value: +{
+  "description": "Primary damage category filter.",
+  "enum": [
+    "Fire",
+    "Hail",
+    "Theft",
+    "Water",
+    "Chemical",
+    "Rollover",
+    "Mechanical",
+    "Vandalized",
+    "Repossession"
+  ],
+  "type": "string"
+}

addedInput schema / properties / drive_type

Added value: +{
+  "description": "Drive type filter for GET /vehicles.",
+  "enum": [
+    "AWD",
+    "FWD",
+    "RWD"
+  ],
+  "type": "string"
+}

addedInput schema / properties / engine_hp_from

Added value: +{
+  "description": "Engine HP from filter for GET /vehicles.",
+  "type": "number"
+}

addedInput schema / properties / engine_hp_to

Added value: +{
+  "description": "Engine HP to filter for GET /vehicles.",
+  "type": "number"
+}

addedInput schema / properties / engine_size_from

Added value: +{
+  "description": "Engine size from filter for GET /vehicles.",
+  "type": "number"
+}

addedInput schema / properties / engine_size_to

Added value: +{
+  "description": "Engine size to filter for GET /vehicles.",
+  "type": "number"
+}

addedInput schema / properties / facility_id / description

Added value: +"Auction facility identifier used to restrict results to one supported facility."

changedInput schema / properties / facility_id / type

Previous value: -[
-  "integer",
-  "string"
-]New value: +"string"

addedInput schema / properties / fuel_type

Added value: +{
+  "description": "Fuel type filter for GET /vehicles.",
+  "enum": [
+    "Diesel",
+    "Hybrid",
+    "Electric",
+    "Flexible",
+    "Gasoline",
+    "All others"
+  ],
+  "type": "string"
+}

addedInput schema / properties / has_key

Added value: +{
+  "description": "Key-availability filter using the documented values No, All or With.",
+  "enum": [
+    "No",
+    "All",
+    "With"
+  ],
+  "type": "string"
+}

addedInput schema / properties / has_shipping_price / description

Added value: +"When true, return only vehicles with supported shipping-price data."

addedInput schema / properties / loc_state / description

Added value: +"Auction location state or region, for example FL."

addedInput schema / properties / lot_status / description

Added value: +"Auction mode filter: All, Timed or Buy Now."

addedInput schema / properties / lot_sub_status / description

Added value: +"Normalized auction state: Open for active/open lots, Live for currently live supported lots, Ended for closed/ended lots."

addedInput schema / properties / make / description
```
Added value: +"Make filter for GET /vehicles."
```
addedInput schema / properties / model / description
```
Added value: +"Model filter for GET /vehicles."
```

addedInput schema / properties / odometer_from

Added value: +{
+  "description": "Odometer from filter for GET /vehicles.",
+  "type": "number"
+}

addedInput schema / properties / odometer_to

Added value: +{
+  "description": "Odometer to filter for GET /vehicles.",
+  "type": "number"
+}

addedInput schema / properties / office_name

Added value: +{
+  "description": "Auction office or branch name filter.",
+  "type": "string"
+}

addedInput schema / properties / per_page / description

Added value: +"Requested page size. Effective maximum is subscription-plan dependent; common public plan limits are 20, 30 or 40 and custom plans may differ."

addedInput schema / properties / platform / description

Added value: +"Readable auction-source selector: copart or iaai. Omit for combined supported sources."

addedInput schema / properties / price_max / description
```
Added value: +"Price max filter for GET /vehicles."
```
addedInput schema / properties / price_min / description
```
Added value: +"Price min filter for GET /vehicles."
```

addedInput schema / properties / radius

Added value: +{
+  "description": "Search radius around zip, interpreted using the selected units.",
+  "type": "integer"
+}

addedInput schema / properties / run_cond

Added value: +{
+  "description": "Normalized run-condition filter.",
+  "enum": [
+    "STATIONARY",
+    "NO INFORMATION",
+    "RUNS AND DRIVES",
+    "ENGINE START PROGRAM"
+  ],
+  "type": "string"
+}

changedInput schema / properties / s / description

Previous value: -"VIN, lot number or title search."New value: +"Search by VIN, lot number or vehicle title/model text."

addedInput schema / properties / sale_document_pending

Added value: +{
+  "description": "When true, restrict results to records with a pending sale document state when supported.",
+  "type": "boolean"
+}

addedInput schema / properties / sale_document_type

Added value: +{
+  "description": "Sale/title document type filter; values are source-backed and can vary.",
+  "type": "string"
+}

addedInput schema / properties / seller_type

Added value: +{
+  "description": "Normalized seller type: dealer, finance, insurance or non_insurance.",
+  "enum": [
+    "dealer",
+    "finance",
+    "insurance",
+    "non_insurance"
+  ],
+  "type": "string"
+}

addedInput schema / properties / today_only / description

Added value: +"When true, restrict results to the endpoint current-day auction logic."

addedInput schema / properties / transmission

Added value: +{
+  "description": "Transmission filter for GET /vehicles.",
+  "enum": [
+    "Manual",
+    "Unknown",
+    "Automatic"
+  ],
+  "type": "string"
+}

addedInput schema / properties / type

Added value: +{
+  "description": "Vehicle type filter for GET /vehicles.",
+  "type": "string"
+}

addedInput schema / properties / units

Added value: +{
+  "description": "Distance and odometer unit system: mi or km.",
+  "enum": [
+    "mi",
+    "km"
+  ],
+  "type": "string"
+}

addedInput schema / properties / upcoming / description

Added value: +"Upcoming selector: all=no upcoming restriction, only=upcoming eligible lots only, without=exclude upcoming lots."

addedInput schema / properties / updated_within_minutes / description

Added value: +"Incremental-sync window. Return records whose updated_at changed within this many minutes; supported range is 1..525600. Use with cursor pagination and an overlap window."

addedInput schema / properties / year_from / description
```
Added value: +"Year from filter for GET /vehicles."
```
addedInput schema / properties / year_to / description
```
Added value: +"Year to filter for GET /vehicles."
```

addedInput schema / properties / zip

Added value: +{
+  "description": "ZIP/postal code used with radius for supported proximity search.",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured JSON returned by the canonical Apibara Vehicle Auction Data API. Source-dependent fields may be null or absent.",
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "meta": {
+      "additionalProperties": true,
+      "description": "Pagination metadata. Treat cursor values as opaque.",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedSep 18, 2026

TDQS

A4.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds the incremental-synchronization use case (which pairs with updated_within_minutes and cursor paging) and the multi-source scope, but discloses no rate limits, plan-dependent result caps, or pagination caveats for what is a heavy 48-parameter query.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the primary use case front-loaded and the sibling-routing guidance second. It reads as fully earned content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full schema coverage, the description need not explain returns or filter formats; it covers purpose, source scope, and routing well. It does not hint at the paging/incremental-sync workflow (cursor plus overlap window, plan-dependent per_page) that dominates correct usage of this endpoint, which is the only material gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter including the deprecated auction_type/body_type aliases and the updated_within_minutes overlap-window guidance is already documented in the schema. The description adds no parameter-level meaning beyond restating the Copart/IAAI scope, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb set (discovery, filtering, incremental synchronization) over a specific resource (Copart and IAA/IAAI auction records), and the scope word 'broad' distinguishes it from single-record lookups. An agent can tell it apart from get_vehicle without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'For one known VIN or lot use get_vehicle; for retained auction appearances use get_vehicle_history.' Both alternatives are named with the condition that selects each, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Apibara Vehicle Auction Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?