In an Australian vehicle workflow, a registration plate is often the first identifier a user has. A plate-based lookup pairs it with a state or territory and asks a data provider for a vehicle match. CSNB exposes that lookup as structured JSON for applications and agents.
What the CSNB lookup returns
When available, the result includes year, make, model, VIN, body type and transmission. The description field may contain additional provider text, while _meta describes the result source, confidence and any empty-result reason.
These are vehicle identity facts. The current response does not include owner contact details, a vehicle valuation, a comprehensive history report or proof that registration is current. Reserved valuation fields are null.
Why the state matters
The plate lookup requires a state or territory code. Use NSW, VIC, QLD, WA, SA, TAS, ACT or NT. If you already hold a 17-character VIN, the same lookup core accepts it without a state requirement.
Make missing fields part of your interface
A match does not guarantee every field will be populated. Let users review prefilled data, show unavailable values explicitly and preserve a manual-entry path. An empty result can reflect an input problem, incomplete coverage or an unavailable upstream provider; it is not proof that the vehicle does not exist.
Check freshness and confidence
Responses can use catalogue data or identity parsed from a provider description. Inspect _meta.source and _meta.confidence instead of treating every match as equally complete. Cached identity data also should not be used as a current registration-status certificate. Read the data scope and freshness notes.
Choose your access route
For an application, use RapidAPI with a subscription key and send the plate or VIN in regoOrVin. Agents can use MCP with a CSNB key or x402 with a compatible wallet. Authentication, parameters and error handling differ by route.