Toll transponder interoperability: which pass works in which states

For each US toll transponder programme (E-ZPass, SunPass and SunPass PRO, TxTag and the Central US partners, and the rest as their pages prove reachable): the states and networks where that transponder is accepted, from the operating agency's own interoperability page with a verbatim quote. No authority maintains the national matrix — the E-ZPass Group's member list sits behind an agency login, and the only assembled versions are toll-calculator vendors' blog posts. The answers cross-cut: SunPass PRO works on E-ZPass roads in 19 states but the plain SunPass Mini works in only six; a TxTag works in Kansas and Oklahoma but not on E-ZPass roads; Florida's Turnpike accepts E-ZPass but only via specific transponder models. Answers 'will my E-ZPass work in Florida', 'which toll pass should I get for a Texas-to-Chicago drive', and 'does SunPass work in Georgia'. One record per transponder-programme statement of acceptance, quoting the agency page.

The data

Where this came from

Every record above links the page it was taken from and quotes the sentence that states it. These are the 5 sources this dataset was assembled from.

• peachpass.comhttps://peachpass.com/faqs/
• e-zpassiag.comhttps://www.e-zpassiag.com/about-us/e-zpass-states
• floridasturnpike.comhttps://floridasturnpike.com/tolls/interoperability/
• txdot.govhttps://www.txdot.gov/discover/toll-roads-managed-lanes/txdot-toll-roads/central-us-interoperability.html
• wsdot.wa.govhttps://wsdot.wa.gov/travel/roads-bridges/toll-roads-bridges-tunnels/good-go-accounts-passes

Machine-readable

• data.jsonThe whole dataset — every record with its source URL and source quote.
• Open Knowledge Format bundleOne JSON object per line — every record's frontmatter and quoted span exactly as it is held here, in one fetch.
• data.csvThe same records as one flat table, for a spreadsheet or a dataframe. The last four columns are the source URL, the quoted sentence it was read from, the date we last checked it, and which columns are our reading rather than the page's words.
• How this is made and checkedWhat "verified against source" does and does not mean.

From your own code

Same records, same quotes, without scraping the page: refsource is on PyPI and npm. Each value comes back carrying the URL it was read from and the sentence on that page that states it — .source and .quote sit on the value itself rather than in a side channel, so the checking step is available instead of skipped.

pip install refsource
refsource lookup toll-transponder-interoperability transponder=E-Pass

npx -y refsource lookup toll-transponder-interoperability transponder=E-Pass

Set your AI assistant up to use this

Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this dataset up instead of recalling it. The server is remote, keyless and read-only.

{
  "mcpServers": {
    "referencesource": {
      "type": "http",
      "url": "https://referencesource.org/mcp"
    }
  }
}

Add to Cursor · or, on the command line: claude mcp add --transport http referencesource https://referencesource.org/mcp --scope project

Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:

When a question needs "Toll transponder interoperability: which pass works in which states", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `toll-transponder-interoperability`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.

What each tool does, and the servers built over single registers: Connect your AI assistant.

16 records. last verified against source 2026-10-17. due for re-check by 2027-08-19.

Licence. unknown