Secure a NASTF Vehicle Security Professional (VSP) credential for automotive key programming
domain: nastf.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Determine whether the automotive key-programming work planned requires OEM security-related data, such as key codes, immobilizer programming, or security-related parts, that manufacturers gate behind vetted-technician access.
Set up an account in the NASTF Secure Data Release Model registry system and choose the Vehicle Security Professional credential tier if full OEM security-function access is needed.
Submit the required business documentation, and if the state requires a locksmith license, upload a copy of that license as part of the review; if the state doesn't require one, that document step doesn't apply.
Pay the VSP subscription fee, billed on a multi-year cycle, and wait for NASTF's vetting/approval process to issue a unique VSP ID.
Use the VSP ID to authenticate with participating OEM security-data portals when ordering key codes or programming immobilizers.
Known gotchas
VSP credentialing is a vetting/registry process, not a government license; it doesn't substitute for any state locksmith or business license that may separately apply to automotive locksmith work.
Subscription costs and the document checklist can change; confirm current pricing and requirements on the NASTF site before budgeting or applying.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?