from drivly
Access Auto.dev vehicle data (VIN decode, listings, photos, specs, recalls, payments) via MCP tools, CLI, SDK or API with guidance on surface detection and usag
Provides patterns and helpers for working with Auto.dev automotive data across multiple surfaces: MCP tools, CLI, SDK, or direct API. Explains detection order (prefer MCP tools, then CLI/SDK, then Direct API), available endpoints (vin decode, listings, photos, specs, build, recalls, payments, taxes), and practical rules for batching, exports (CSV/JSON), and mapping common parameter gotchas. Includes plan/pricing notes and command examples for the CLI and MCP usage.
Intended for agents integrating vehicle-data workflows; provides conservative rules to avoid malformed API calls and to recommend fallbacks when MCP/CLI surfaces are unavailable.
This skill has not been reviewed by our automated audit pipeline yet.
