check-vehicle-registration

dmv.ca.gov/check-if-a-vehicle-is-registered-zgg414 · updated May 21, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$browse install dmv.ca.gov/check-if-a-vehicle-is-registered-zgg414
0 commentsdiscussion
summary

Look up the current California DMV registration status, expiration date, fees owed, and holds for a CA license plate plus one secondary identifier (last 5 of VIN, owner's last name, or company name). Read-only — never advances into renewal payment.

skill.md
name
check-vehicle-registration
title
California Vehicle Registration Status Check
description
>- Look up the current California DMV registration status, expiration date, fees owed, and holds for a CA license plate plus one secondary identifier (last 5 of VIN, owner's last name, or company name). Read-only — never advances into renewal payment.
website
dmv.ca.gov
category
government
tags
- government - dmv - vehicle - registration - california - read-only - aws-waf
source
'browserbase: agent-runtime 2026-05-18'
updated
'2026-05-18'
recommended_method
browser
alternative_methods
- method: api rationale: >- No public JSON/GraphQL API for registration status exists on dmv.ca.gov. The `/wasapp/ipp2/initRegInfoInquiry.do` endpoint sometimes cited online returns 404. Only the server-rendered Struts form at `/wasapp/rsrc/vrapplication.do` works.
verified
true
proxies
true

California Vehicle Registration Status Check

Purpose

Given a California license plate plus one secondary identifier (last 5 of the VIN, the registered owner's last name, or the company/lessor name), return the vehicle's current California DMV registration status, expiration date, fees owed, and any holds. Read-only — the skill stops at the results page; it never advances into the renewal-payment flow.

The lookup is the CA DMV's free public "Vehicle Registration Status" service, a server-rendered Java/Struts (.do) flow gated by AWS WAF + CloudFront. It works without an account and is the only first-party way to verify CA registration status without making a Public Records Request.

When to Use

  • A driver/owner agent verifying whether their plate is currently registered before a road trip or smog check.
  • A fleet/lessor agent reconciling registration status across multiple CA plates.
  • A used-car-buying agent confirming a seller's claim that the registration is "current" before exchanging money.
  • Any agent that needs "registered? yes/no + expiration date" for one CA plate without paying for a commercial VIN service.

Do not use this skill for:

  • Out-of-state plates (CA-only).
  • Title status, lienholder info, or registered-owner identity disclosure — those require a formal Vehicle Record Request (different skill, fees apply, requires a justified purpose under CA Vehicle Code).
  • Driver's-license status — separate DMV tool.

Workflow

The flow is a three-step server-rendered form. There is no public JSON API for registration status — confirmed by surveying the dmv.ca.gov surface. Everything goes through wasapp/rsrc/vrapplication.do. Use a remote Browserbase session with --proxies --verified because the WAF is sensitive to datacenter IPs and missing browser fingerprints.

1. Open a Verified + residential-proxy session

SID=$(browse cloud sessions create --keep-alive --proxies --verified | jq -r .id)
export BROWSE_SESSION="$SID"

A bare session (no --proxies) regularly trips the AWS WAF banner ("Your request has been blocked...") on the first POST. The --verified flag (Verified browsers) is what passes the fingerprint check during form submission. Both are required — do not omit either.

2. Navigate directly to step 1 (license-plate form)

browse open --remote "https://www.dmv.ca.gov/wasapp/rsrc/vrapplication.do"
browse wait load --remote
browse snapshot --remote

Skip the marketing portal page (/portal/vehicle-registration/vehicle-registration-status/) — its only useful link is /wasapp/rsrc/vrapplication.do, so going direct saves one navigation and one cookie round-trip.

The form has a single visible input:

FieldSelectorConstraint
License plateinput#licensePlateNumber (name licensePlateNumber)maxlength 8, pattern [a-zA-Z0-9]*, no spaces / special chars

Fill it and submit:

browse fill --remote "input#licensePlateNumber" "8ABC123"
browse click --remote 'button[value="Continue"]'   # name="method" value="Continue"
browse wait load --remote

The form POSTs to itself (action="/wasapp/rsrc/vrapplication.do", method=post) with method=Continue and licensePlateNumber=<value>. The backend issues a 302 to step 2.

3. Step 2 — secondary identifier

Step 2 asks for one of:

  • Last 5 digits of the VIN (or HIN for vessels)
  • Registered owner's last name (private ownership)
  • Company / lessor name (leased or company-owned)

Pick whichever the user supplied. The form is a radio-group + single text input. Snapshot and use refs:

browse snapshot --remote                                  # find the radio for the chosen identifier
browse click  --remote '@<radio-ref>'                    # select identifier type
browse fill   --remote 'input[type="text"]' "12345"      # the secondary value
browse click  --remote 'button[value="Continue"]'
browse wait load --remote

If the user gives "last 5 of VIN", strip dashes/spaces and uppercase. The DMV accepts only alphanumerics here.

4. Step 3 — extract status

The results page is keyed off plate + identifier match. Read the page text:

browse get markdown body --remote
browse screenshot --remote --path screenshots/04-results.png

Map the visible content to the output schema in §Expected Output. Don't click "Renew Registration" / "Pay Now" / any forward CTA — read-only.

5. Release the session

browse cloud sessions update "$SID" --status REQUEST_RELEASE

Site-Specific Gotchas

  • No public JSON/GraphQL API exists. Surveyed dmv.ca.gov and wasapp/* paths — every registration-status route is server-rendered Struts. Confirmed wasapp/ipp2/initRegInfoInquiry.do (a sometimes-cited "alt" endpoint) returns 404 as of the build date. Don't waste time looking for a faster surface; the only path is the form flow.
  • The form is two pages, not one. Step 1 takes only the license plate (input#licensePlateNumber, maxlength 8). Step 2 asks for one secondary identifier. New agents commonly stub a one-shot POST with both fields — that returns the step-1 page again because the secondary input doesn't exist in the step-1 form bean.
  • Submit-button selector. The Continue button is button[name="method"][value="Continue"] — the button is the form's only name="method" element, and its value is what drives Struts dispatch. Targeting button[type="submit"] works too but is less specific.
  • CloudFront / WAF behavior. The pages are fronted by CloudFront with x-frame-options: SAMEORIGIN and an active AWS WAF rule (AWSALB, AWSALBCORS, PD_STATEFUL_*, TS01dc4fc6 cookies are issued on every visit and must be preserved across the multi-step flow). Browserbase's session model handles this automatically; if you're rolling your own HTTP client you must keep the cookie jar.
  • No CAPTCHA observed on step 1. The form has no visible CAPTCHA on initial load. Aggressive POST repetition (>~5 within a minute from the same fingerprint) trips a WAF block page with "Your request has been blocked..." — back off and let the residential proxy rotate.
  • autocomplete="off" everywhere. The form sets autocomplete off; if you browse fill and the input still appears empty on snapshot, the page may be using a non-standard CA-DMV input wrapper. Use browse press Tab after fill to force the blur event before clicking Continue.
  • Plate format. California plates are 1–7 chars (modern: 7 alphanumeric, older: shorter). Max 8 is just the input maxlength. Strip dashes, spaces, and any special chars before filling. Kid-plate symbols (heart, star, hand, plus) are not enterable here — the DMV portal warns "For Kids Plates, please leave out any symbols."
  • Step-2 invalid-secondary path. If the plate exists but the secondary identifier doesn't match, the result page renders a generic "We could not locate a record matching the information provided" — this is not_found from the user's perspective, but it is not proof the plate is unregistered (could be a typo in the secondary). Surface this distinction in the output.
  • Cross-jurisdiction. Non-CA plates always render not_found. There is no way to look up registration status for a non-CA vehicle on dmv.ca.gov. For non-CA plates, the agent should refuse and recommend the relevant state's DMV.
  • Don't follow the "Renew" CTA. The success page includes a "Renew Registration Now" link that goes to /wasapp/vrir/start.do (the renewal flow). Read-only skill — stop at the status page.
  • Spanish locale. dmv.ca.gov/portal/es/vehicle-registration/vehicle-registration-status/ exists, but the actual /wasapp/rsrc/vrapplication.do form is English-only. Localization happens only on the portal page, not the underlying app.

Expected Output

Return a JSON object with one of the following shapes.

Success — current registration

{
  "success": true,
  "license_plate": "8ABC123",
  "registration_status": "current",
  "expiration_date": "2026-08-31",
  "fees_due_usd": 0,
  "holds": [],
  "raw_status_text": "Your vehicle registration is current. Expires: 08/31/2026.",
  "renewal_available": false,
  "source_url": "https://www.dmv.ca.gov/wasapp/rsrc/vrapplication.do"
}

Success — expired or pending renewal

{
  "success": true,
  "license_plate": "8ABC123",
  "registration_status": "expired",
  "expiration_date": "2025-04-30",
  "fees_due_usd": 312.00,
  "holds": [
    {"type": "smog_certification_required", "detail": "Smog certification is required to renew."}
  ],
  "raw_status_text": "Your registration expired on 04/30/2025. Renewal fees: $312.00. Smog certification required.",
  "renewal_available": true,
  "source_url": "https://www.dmv.ca.gov/wasapp/rsrc/vrapplication.do"
}

Not found — plate / secondary mismatch

{
  "success": true,
  "license_plate": "8ABC123",
  "registration_status": "not_found",
  "expiration_date": null,
  "fees_due_usd": null,
  "holds": [],
  "raw_status_text": "We could not locate a record matching the information provided.",
  "renewal_available": false,
  "source_url": "https://www.dmv.ca.gov/wasapp/rsrc/vrapplication.do",
  "note": "Plate may exist but the secondary identifier (VIN-last-5 / last-name / company-name) didn't match. Re-prompt the user."
}

Site-blocked / WAF wall

{
  "success": false,
  "error_reasoning": "waf_blocked",
  "raw_status_text": "Your request has been blocked. ... Request ID: <hex>",
  "source_url": "https://www.dmv.ca.gov/wasapp/rsrc/vrapplication.do",
  "remediation": "Rotate the residential proxy and retry once after 60s. Confirm `--verified` Verified browsers is enabled."
}

Tool offline / maintenance

{
  "success": false,
  "error_reasoning": "service_unavailable",
  "raw_status_text": "<verbatim DMV maintenance banner>",
  "source_url": "https://www.dmv.ca.gov/wasapp/rsrc/vrapplication.do"
}

Out-of-state plate (user error)

{
  "success": false,
  "error_reasoning": "non_ca_plate",
  "raw_status_text": null,
  "remediation": "This skill only checks California plates. For other states use that state's DMV registration lookup."
}
how to use check-vehicle-registration

How to use check-vehicle-registration on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add check-vehicle-registration
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$browse install dmv.ca.gov/check-if-a-vehicle-is-registered-zgg414

The skills CLI fetches check-vehicle-registration from GitHub repository dmv.ca.gov/check-if-a-vehicle-is-registered-zgg414 and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/check-vehicle-registration

Reload or restart Cursor to activate check-vehicle-registration. Access the skill through slash commands (e.g., /check-vehicle-registration) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.630 reviews
  • Kaira Martinez· Dec 8, 2024

    Useful defaults in check-vehicle-registration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kaira Diallo· Nov 27, 2024

    check-vehicle-registration has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Dev Gill· Nov 15, 2024

    check-vehicle-registration fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Lucas Abebe· Oct 18, 2024

    Solid pick for teams standardizing on skills: check-vehicle-registration is focused, and the summary matches what you get after install.

  • Kaira Gill· Oct 6, 2024

    We added check-vehicle-registration from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Kabir Malhotra· Sep 25, 2024

    Keeps context tight: check-vehicle-registration is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Yash Thakker· Sep 13, 2024

    I recommend check-vehicle-registration for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Diego Choi· Sep 9, 2024

    check-vehicle-registration is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Noah Ghosh· Aug 28, 2024

    Keeps context tight: check-vehicle-registration is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Soo Nasser· Aug 16, 2024

    check-vehicle-registration is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 30

1 / 3