vehicle.profile

Vehicle 360 — decode a VIN and get its full safety picture in one call. Returns the decoded vehicle (make, model, year, trim, engine, plant, body class, drivetrain — NHTSA vPIC) plus that exact make/model/year's open safety recalls (with park-it / park-outside / over-the-air-update flags) and NHTSA owner complaints (crash/fire/injury/death flags). recalls and complaints are keyed to the decoded make+model+year, so they describe THIS vehicle, not a generic feed. Each section reports found/error independently. Pass vin (17 chars); optional modelYear disambiguates pre-1980 VINs. Used for used-car due diligence, fleet safety, insurance. Individual sources: /api/vehicle/vin-decode, /api/vehicle/recalls, /api/vehicle/complaints.

price
$0.0058 USDC per call
method
GET/api/vehicle/profile
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The profile API is a pay-per-call vehicle endpoint built for AI agents and autonomous software. Vehicle 360 — decode a VIN and get its full safety picture in one call.

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in profile data source for an agent tool-use loop, an MCP host, or a backend that needs vehicle data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
vinrequiredstring
min 17 chars · max 17 chars
modelYearinteger
min 1949 · max 2099

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/vehicle/profile?vin=xxxxxxxxxxxxxxxxx&modelYear=1949'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/vehicle/profile?vin=xxxxxxxxxxxxxxxxx&modelYear=1949' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>'

# Or use the canonical runner (handles probe → sign → retry):
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/vehicle/profile?vin=xxxxxxxxxxxxxxxxx&modelYear=1949'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.vehicle.profile({
  "vin": "xxxxxxxxxxxxxxxxx",
  "modelYear": 1949
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.vehicle.profile(vin="xxxxxxxxxxxxxxxxx", modelYear=1949)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "vehicle.profile",
    "arguments": {
      "vin": "xxxxxxxxxxxxxxxxx",
      "modelYear": 1949
    }
  }
}

Response

FieldTypeDescription
vinstring
vehicleobject
recallsobject
complaintsobject
sourcesarray
Example response datajson
{
  "vin": "example",
  "vehicle": {
    "found": false,
    "error": "example"
  },
  "recalls": {
    "found": false,
    "error": "example",
    "count": 1,
    "recalls": [
      {}
    ]
  },
  "complaints": {
    "found": false,
    "error": "example",
    "count": 1
  },
  "sources": [
    {}
  ]
}

FAQ

Do I need an API key to use the profile API?
No. vehicle.profile is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the profile API cost?
$0.00576 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the profile API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call vehicle.profile from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: profile api · vehicle profile api · profile api for ai agents · x402 vehicle api · profile api no api key · pay per call profile api · vehicle api