Skip to main content
ForgeMeshLive on Base mainnet · x402 + MPP

Vehicle Intelligence Pack. One VIN in, the whole car's history out.

The used-car due-diligence stack for agents. One VIN in — specs, recalls, crash ratings, real-world failure patterns, and running costs out. Six x402-paid endpoints, every one of them auto-identifying the vehicle from the VIN and chaining the decode server-side, so an agent never has to call two endpoints to get one answer.

All data comes from official public-domain sources, fetched live with a 30-minute cache — always current, no licensing risk. Built for car-shopping agents, marketplace and listing-enrichment tools, insurance quoting, fleet software, and mechanic triage bots. From half a cent a call, in USDC on Base.

Six endpoints, half a cent to a cent

RouteWhat it answersPrice
POST/vin-decodeVIN → full specs: make, model, year, trim, engine, transmission, plant
aliases: /decode-vin, /vin-lookup, /vin-decoder
$0.005
POST/vehicle-recallsOfficial safety recalls by VIN or year/make/model, with park-it / park-outside fire-risk flags
aliases: /car-recalls, /recalls-by-vin, /vehicle-recall-check
$0.005
POST/vehicle-safety-ratingsGovernment 5-star crash-test ratings — overall, front, side, rollover — plus safety features
aliases: /car-safety-ratings, /crash-test-ratings, /vehicle-crash-ratings
$0.005
POST/vehicle-complaintsConsumer defect complaints, filterable by component
aliases: /car-complaints, /vehicle-complaint-search, /car-problem-reports
$0.005
POST/vehicle-top-failuresThe full complaint file ranked into "what actually breaks on this car" — component share % plus crash/fire/injury/death totals
aliases: /car-reliability-report, /top-failure-components, /common-car-problems
$0.01
POST/vehicle-fuel-economyOfficial MPG, annual fuel cost, and CO2 for 1984+ vehicles
aliases: /car-mpg-lookup, /fuel-cost-lookup, /gas-mileage-lookup
$0.005

Try it: the payment, VIN to what actually breaks

/vehicle-top-failures is the headliner: it aggregates the full complaint file into a ranked report of what actually breaks on that car. Here it is against a real VIN, unpaid first, then paid:

curl -X POST https://x402.forgemesh.io/vehicle-top-failures \
  -H 'Content-Type: application/json' \
  -d '{"vin":"1HGCM82633A004352"}'

# → HTTP 402 Payment Required
# → PAYMENT-REQUIRED header (x402) or WWW-Authenticate: Payment (MPP)
# → price $0.01, network base, asset USDC, worked example, input schema

# agent constructs the payment from the challenge, settles in USDC on Base,
# and retries the same request with payment credentials attached

curl -X POST https://x402.forgemesh.io/vehicle-top-failures \
  -H 'Content-Type: application/json' \
  -H 'X-PAYMENT: <settled payment payload>' \
  -d '{"vin":"1HGCM82633A004352"}'

# → HTTP 200 OK
# → 2003 Honda Accord — 2,013 complaints on file
# → POWER TRAIN 46% · AIR BAGS 16.1% · SERVICE BRAKES 8.7%
# → crash / fire / injury / death totals by component

Every route answers the same 402 challenge in both x402 and Stripe's MPP format on the same response — one endpoint, two payment rails, no separate integration for either agent stack.

Part of the Utility Grid

These six routes live on the ForgeMesh Utility Grid alongside dozens of other paid utilities. The open-source MCP server @forgemeshlabs/utility-grid-mcp exposes all grid routes as agent tools. Without a wallet key it returns the structured x402 challenge and spends nothing — safe to install and explore. Discovery metadata is published at /.well-known/x402.json for the standard agent indexes.