fittings-nhtsa-safety-ratings

Original：🇺🇸 English

Translated

1 scripts

NCAP five-star crash ratings for a model year, make and model: overall, frontal, side and rollover, with recall, complaint and investigation counts. Called as GET /v1/nhtsa/safety-ratings, it takes modelYear, make, model and returns found, variants, truncated. Crash-test scores are per body style and drivetrain, not per model, so an agent comparing vehicles needs the tested variant rather than a remembered headline number. Reading this schema and dry-running the call are free and need no wallet; a real call costs $0.004, paid in USDC on Base over x402.

1installs

Sourcefittings-sh/fittings

Added on2026-08-17

NPX Install

npx skill4agent add fittings-sh/fittings fittings-nhtsa-safety-ratings

SKILL.md Content

View Translation Comparison →

NHTSA NCAP safety ratings

nhtsa.safety-ratings

on

https://fittings.sh

. One endpoint, government and civic.

NCAP five-star crash ratings for a model year, make and model: overall, frontal, side and rollover, with recall, complaint and investigation counts.

The call

GET https://fittings.sh/v1/nhtsa/safety-ratings

Field	Type	Required	Notes
`modelYear`	number	yes	Model year, e.g. 2015
`make`	string	yes	Make, e.g. Honda
`model`	string	yes	Model, e.g. Accord

Example input:

json

{
  "modelYear": 2015,
  "make": "Honda",
  "model": "Accord"
}

Cost and provenance


Price	$0.004
Source	NHTSA SafetyRatings API (api.nhtsa.gov), public domain
Licence	public-domain

Why call it rather than answer from memory

Crash-test scores are per body style and drivetrain, not per model, so an agent comparing vehicles needs the tested variant rather than a remembered headline number.

Calling it

A skill is loaded on its own, so this document has to be enough by itself. It does not assume the general

fittings

skill is also loaded.

call.mjs

ships alongside this file; if it is missing (this document reached you without the rest of the skill), fetch it once with

curl -sO https://fittings.sh/skill/call.mjs

.

Free, and needs no wallet. Read the schema and see what a call would cost:

bash

curl -s https://fittings.sh/catalog/nhtsa.safety-ratings | jq

Paying. The endpoint answers

402 Payment Required

with a signed quote, you sign an authorization, and a facilitator settles it — you never send a transaction and never pay gas. Before it spends anything, the client checks its own hash against the gateway and refuses rather than sign with logic the gateway has moved past:

bash

# Dry run. Prints the quote and pays nothing, because no key is set.
node call.mjs nhtsa.safety-ratings modelYear=2015 make=Honda model=Accord

# For real: a wallet holding USDC on Base, and nothing else.
export FITTINGS_PRIVATE_KEY=0x...
node call.mjs nhtsa.safety-ratings modelYear=2015 make=Honda model=Accord

Spending is never a side effect of curiosity: with no

FITTINGS_PRIVATE_KEY

the client fetches the quote and stops.

FITTINGS_MAX_PRICE

caps what it will pay without asking, and defaults to $0.05.

Use a throwaway wallet holding a few dollars, not a main one. The key sits in plaintext wherever the agent runs, and the whole cost of entry is USDC on Base — no account, no API key, and no ETH, because the payer signs off-chain and the facilitator broadcasts and pays the gas.

Writing your own client instead of using this one?

@x402/core

and

@x402/evm

on npm, and the

fittings

skill records the two things that cost real debugging time: the challenge is in a response header rather than the body, and it must be re-signed from the exact request being retried.

If this is not the right service,

https://fittings.sh/catalog/search?q=...

searches all of them for free.