Ask your AI who sponsors your role.
Redeem your code and Claude or ChatGPT can name the companies that sponsor your job title, then check any posting you find against 7.6 million real DOL filings.
One tap. We only use it to tie the connector to you. Free, no card.
What the code unlocks
H1B data, just ask
The connector gives your assistant direct access to U.S. Department of Labor H-1B and LCA disclosure records: real petitions filed by real employers, not job ads.
Sponsors for your exact role
"Which companies sponsor H-1B for product managers?" answered from real filings, ranked by petition volume.
Verify any job posting
Found a role online? Check whether that company truly sponsors that title before you spend an hour applying.
Entry-level reality check
Every result carries the seniority mix, so you do not chase listings that only ever go to eight-year veterans.
7.6 million filings
Roughly 198,000 employers, current through the latest published disclosure. Works in both Claude and ChatGPT.
See it in action
H1B data inside your Claude chat
Ask Claude anything about an employer's H1B history. It queries SponsorStats automatically and returns real data in seconds.
Video not loading? Watch on YouTube
How it works
No commands, no syntax
Once connected, Claude or ChatGPT uses SponsorStats automatically whenever you ask about an employer or a role.
Activate your connector
Sign in with Google above and enter your access code. You get a connector URL that is yours.
Paste it into Claude or ChatGPT
Add it once as a custom connector. The three steps below walk through it.
Start a new chat
Open Claude.ai, the desktop app or ChatGPT and start any conversation.
Ask and get real data
Petition counts, salary ranges and seniority breakdowns come back in seconds.
Things you can ask
Try these first
Tap to copy a prompt
Paste any of these into a new chat once your connector is added.
Get started
Connect in 3 steps
Takes under a minute. Activate once with your access code, then use the same URL in Claude or ChatGPT.
Get your personal connector URL
Sign in with Google at the top of this page and enter the access code you were given. You get a connector URL that is yours.
Paste it into Claude and save
Open Claude's Add custom connector dialog, give it any name, paste your URL from step 1, then click Add.
The plain /mcp address still connects, but returns no data until it carries your key.
Start a new chat and ask anything
Claude queries SponsorStats automatically whenever you ask about H1B data. Existing conversations do not pick up a newly added connector, so start a fresh one.
Using ChatGPT instead?
Same connector, same URL. In ChatGPT go to Settings then Connectors, choose Create or Add custom connector, paste your personal URL from step 1, set authentication to No authentication, and save. Then start a new chat.
Custom connectors need a ChatGPT plan that includes them (Plus, Pro, Business or Enterprise), and on some plans they appear only in developer mode. If you do not see the option, that is a ChatGPT account setting rather than a problem with the URL.
Available tools
What Claude and ChatGPT can look up
Five tools, used automatically based on your question. The first two answer "tell me about this company"; the last three answer "find me companies for this role, and check whether these specific openings are really sponsored".
Returns year-by-year H1B petition totals, average salary across all years, and the latest filing year for a given employer. Use this for company-level sponsorship trends.
| Parameter | Type | Required | Description |
|---|---|---|---|
| employer_name | string | Required | Employer to search. Fuzzy and case insensitive, so "Google" matches "GOOGLE LLC". |
Searches individual H1B petition filings with optional filters. Returns petition counts and average salaries broken down by wage level (seniority) and by year.
| Parameter | Type | Required | Description |
|---|---|---|---|
| employer_name | string | Required | Employer to search. Fuzzy, case insensitive matching applied automatically. |
| job_title | string | Optional | Filter by job title. Fuzzy match, so "product manager" matches "Senior Product Manager II". |
| pw_wage_level | I · II · III · IV | Optional | Filter by prevailing wage level. I is entry level, II qualified, III experienced, IV senior. |
| year | integer | Optional | Filter to a specific filing year derived from the DOL decision date. Example: 2023. |
Starts from a role rather than a company. Returns employers with a filing track record for that job title, ranked by petition volume, with recent activity, filing trend, seniority mix, and how entry friendly the role is.
| Parameter | Type | Required | Description |
|---|---|---|---|
| role_title | string | Required | Role to search. Job posting style titles work, so "Senior Product Manager, Growth" resolves to Product Manager automatically. |
| wage_level | I · II · III · IV | Optional | Restrict to a seniority band. I is entry level, IV is senior or expert. |
| active_only | boolean | Optional | Only employers that filed for this role in the most recent 12 months of available data. |
| min_petitions · limit | integer | Optional | Volume floor, and how many employers to return (default 25, max 50). |
The verification step. Give it real job postings, company plus title, and it says whether each employer actually sponsors that specific role, not just whether they sponsor at all. Checks up to 25 postings in one pass.
| Parameter | Type | Required | Description |
|---|---|---|---|
| checks | array | Required | Up to 25 {employer_name, job_title} pairs. Paste posting titles verbatim, no cleanup needed. |
Each posting comes back with one of five verdicts: core sponsored role (a top 3 title at that employer), regularly sponsored, occasionally sponsored, sponsors but not this role, or no sponsorship record, plus petition count, how the title ranks inside that company, and its entry level share.
Translates a job board title into the titles employers actually write on DOL filings, with petition volume and sponsoring employer counts for each. Used automatically when a title needs disambiguating.
| Parameter | Type | Required | Description |
|---|---|---|---|
| query | string | Required | Title or phrase to resolve. Abbreviations are expanded, so "SWE II" finds Software Engineer and "Senior PM" finds Product Manager. |
Troubleshooting
Common issues and fixes
Claude says it can't find the connector, or doesn't use H1B data
After adding the connector you must start a new chat. Existing
conversations do not pick up newly added connectors. Also confirm the URL is exactly
the one from the top of this page. If you set this up before and used the older
/mcp/sse address, delete that connector and re-add it.
It found sponsors but no actual job openings
SponsorStats holds historic DOL filing records. It knows who has sponsored, not what is hiring today. Finding live openings is your assistant's own web search. Make sure web search is enabled in Claude or ChatGPT, then ask it to look up current roles at the companies SponsorStats returned and check those postings back against the connector.
ChatGPT doesn't show a way to add a connector
Custom connectors require a ChatGPT plan that supports them (Plus, Pro, Business or Enterprise), and on some plans they are only visible once developer mode is turned on in settings. This is a ChatGPT account limitation, not a problem with the connector URL.
No data found for a company I know exists
Try a shorter or more generic version of the name. Use Google instead of
Google LLC, or Amazon instead of
Amazon.com Services LLC. The search is fuzzy but works best with the core
company name.
The connector shows as "connected" but Claude never calls it
Make sure your question explicitly mentions H1B, visa sponsorship, or an employer. Claude invokes the connector automatically when the context matches. Try phrasing like "Does [Company] sponsor H1B visas?" or "What are [Company]'s H1B filings?"
I see a connection error
The connector answers each request on its own, so there is no long lived stream to drop.
A one off error is usually a cold start on our side and clears on retry. If it persists,
remove and re-add the connector at
claude.ai,
and check the URL has no /sse on the end.
Data looks outdated
SponsorStats is sourced from U.S. Department of Labor public records. The database was last updated with data accessed on October 2, 2025. Filings from after that date are not yet reflected.
Data is U.S. Department of Labor H-1B and LCA disclosure records: real petitions filed, not job ads.
Works on Claude.ai, the Claude desktop app, and ChatGPT · Free with an access code