74trust / 100
Vin Decode
by x402-service-production-e242.up.railway.app in AI models & inference
x402 APIPassing, checked 2 h ago
Single VIN decode via NHTSA vPIC: make, model, year, trim, engine, transmission, drivetrain, GVWR, plant country. Spec data only -- no accident/title/odometer history.
GET
https://x402-service-production-e242.up.railway.app/vin-decode- Price
- n/a
- per call
- Uptime
- 100%
- last 30 days
- Response time
- 283 ms
- 341 ms slowest 5%
- Last check
- Passed
- 2 h ago, next any minute now
Reliability
All checks passedSome failedAll failedNot checked
How to call it
GET https://x402-service-production-e242.up.railway.app/vin-decode
Each call is paid with the request over x402. We can't price the token it asks for: see Payment terms.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://x402-service-production-e242.up.railway.app/vin-decode?vin=1HGCM82633A004352Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
vin | string | Yes | 17-character Vehicle Identification Number |
Example response
The provider's example. We can't check it without paying.
{
"bodyClass": "Sedan",
"drivetrain": "FWD",
"gvwr": "Class 1: 6,000 lb or less",
"make": "Honda",
"model": "Accord",
"plantCountry": "USA",
"recalls": [],
"transmission": "Automatic",
"trim": "EX-L",
"year": 2020
}Call it from code
The curl command shows the payment challenge.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://x402-service-production-e242.up.railway.app/vin-decode?vin=1HGCM82633A004352'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://x402-service-production-e242.up.railway.app/vin-decode?vin=1HGCM82633A004352' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeWe don't show code that pays this service: it asks for a token we don't recognise.
Security scan
1 finding
- Asks for an unrecognised token in payment
EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v on solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 278 ms | - |
| 6 h ago | Passed | 402 | 279 ms | - |
| 10 h ago | Passed | 402 | 315 ms | - |
| 14 h ago | Passed | 402 | 302 ms | - |
| 18 h ago | Passed | 402 | 280 ms | - |
Show 10 older checks
| 22 h ago | Passed | 402 | 351 ms | - |
| 25 h ago | Passed | 402 | 284 ms | - |
| 29 h ago | Passed | 402 | 282 ms | - |
| 33 h ago | Passed | 402 | 317 ms | - |
| 37 h ago | Passed | 402 | 277 ms | - |
| 40 h ago | Passed | 402 | 328 ms | - |
| 44 h ago | Passed | 402 | 268 ms | - |
| 47 h ago | Passed | 402 | 128 ms | - |
| 2 days ago | Passed | 402 | 341 ms | - |
| 2 days ago | Passed | 402 | 136 ms | - |