Register at the CARUSO dataplace and create a developer account to access the API catalog and available vehicle data products from connected OEM partners
Browse the marketplace to identify the specific vehicle data packages available for the OEM brands and data types your use case requires, noting pricing and access tier for each
Subscribe to the desired data products and complete the consent or data sharing workflow required for the target OEM's vehicles
Authenticate to the CARUSO API using your account credentials and retrieve an access token for making vehicle data requests
Query the vehicle data endpoints using a vehicle identifier and receive normalized responses in CARUSO's standardized schema, which abstracts OEM-specific field names
Handle consent management: for consumer vehicle data, the vehicle owner must have consented to share their data with your application through the OEM app or CARUSO consent flow
Known gotchas
CARUSO acts as a data broker between OEMs and developers; available data types are bounded by what each participating OEM has agreed to expose through the marketplace — not all OEMs offer the same data points
Consumer vehicle data requires explicit owner consent obtained through the OEM's app ecosystem; CARUSO provides the consent framework but the owner experience is OEM-branded, which may affect conversion rates
The CARUSO marketplace is primarily European-focused; if your use case requires North American OEM data, verify OEM participation and regional coverage before building
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp