The dominant technology platform underlying state court systems across the United States is Tyler Technologies' Odyssey suite. Deployed across more than 1,000 counties in over 30 states and covering approximately 55% of the US population, Odyssey is the closest thing state courts have to a unifying standard — and therefore the highest-priority target for any developer building state court monitoring.
This guide explains what Odyssey is, which courts use it, how it differs from PACER and CM/ECF, and what the programmatic access challenges look like in practice.
What is Tyler Technologies?
Tyler Technologies (NYSE: TYL) is the largest provider of integrated software and technology services to the US public sector. Founded in 1966 and headquartered in Plano, Texas, it serves more than 10,000 government clients across all 50 states. In the courts and justice space, Tyler is the dominant vendor — Odyssey is the most widely deployed court case management system in the country.
What is Odyssey?
Odyssey is Tyler's flagship court case management platform — a comprehensive, integrated suite of software modules that courts use to manage every aspect of their operations from the moment a case is filed through final disposition. All modules share a common database and are tightly integrated.
Odyssey Case Manager
Central case management. Docket entries, party records, document storage, calendaring, and workflow automation. This is where the data that DocketLayer surfaces lives.
Odyssey File & Serve
Electronic filing portal for attorneys and self-represented litigants. Filed documents appear on the docket in near real time via integration with Case Manager.
Odyssey Portal
Public-facing web portal for case search and docket access. The primary interface through which docket data is accessed today — and the access point DocketLayer targets.
Odyssey Financial Manager
Fee assessment, payment processing, and fund distribution. Not a data target for monitoring workflows but part of the integrated platform.
Key state deployments
How Odyssey differs from PACER
Developers familiar with PACER and CM/ECF will find Odyssey both similar in concept and meaningfully harder to access in practice.
No unified login. PACER provides a single login that works across all 94 federal district courts. There is no equivalent for Odyssey. Each Odyssey-powered court runs its own instance with its own URL, its own public portal, and its own access model.
No standardized API. Federal courts offer PACER's documented data model. Odyssey's public-facing access is primarily through web portals — Odyssey Portal, re:SearchTX, and similar interfaces — designed for human users, not programmatic consumption.
No per-page fee model. PACER charges $0.10 per page. Odyssey portals are typically free for basic case information access, though some jurisdictions require paid subscriptions for certain data or document types.
Wider range of case types. Federal courts handle civil, criminal, and bankruptcy cases. Odyssey courts handle all of those plus family law, probate, landlord-tenant, small claims, juvenile, and traffic matters.
Programmatic access challenges
Portal-based access with browser automation requirements
Most Odyssey public portals are built as modern web applications with JavaScript rendering, session management, and CAPTCHA protections. Simple HTTP requests are insufficient — scraping requires browser automation (Playwright, Puppeteer) rather than the requests-based approach that works against CM/ECF.
No standardized data schema
Despite running the same underlying Odyssey platform, courts across different states and counties have customized field names, case type codes, party role labels, and document categories. A parser that works for Texas courts requires significant adaptation for California or Kansas courts.
Inconsistent data exposure
Not all Odyssey courts expose the same data through their public portals. Some courts provide full docket entry text; others provide only filing dates and document counts. Document access policies vary widely and change without notice.
Rate limiting and CAPTCHA
Many Odyssey portals implement CAPTCHA challenges, IP-based rate limiting, or session-based access restrictions to prevent automated scraping. These protections are more aggressive than what PACER implements and require more sophisticated circumvention approaches.
Authentication for certain data
While basic case search is typically public, some portal features — including certain document types or bulk access — require attorney or registered user credentials that commercial monitoring services cannot easily obtain at scale.
Public access portals: the key interfaces
re:SearchTX is Texas's statewide case search portal, powered by Tyler Technologies. It covers the majority of Texas courts through a unified search interface — more comprehensive than most state portals given Texas's statewide Odyssey deployment. This is the primary access point for DocketLayer's Texas state court integration.
State-specific portals cover California, Washington, Kansas, and others — each with distinct portal implementations, varying levels of data completeness, and different access controls layered on top of the shared Odyssey platform.
Case types in Odyssey courts
For commercial AI agent use cases — debt collection, compliance, credit risk, insurance, M&A due diligence — the most relevant Odyssey case types are civil cases (contract disputes, commercial litigation, judgments), bankruptcy-adjacent proceedings (state insolvency and assignment actions), criminal cases (relevant for compliance and background screening workflows), and landlord-tenant proceedings (evictions relevant to property management agents).
Family law, probate, juvenile, and traffic cases are high-volume but lower priority for most commercial monitoring workflows, and many jurisdictions restrict access to sensitive family and juvenile records regardless.
DocketLayer's approach
DocketLayer's Phase 2 state court expansion targets Odyssey courts in Texas and California first. Texas and California together represent the largest Odyssey deployments in the country and cover a combined population exceeding 60 million people. Both states have relatively consistent county-level Odyssey implementations, making AI normalization more tractable than states with more fragmented technology landscapes.
Agents querying DocketLayer for state court data will use the same endpoint structure and payment model as agents querying federal court data. A case ID, a jurisdiction code, an x402 payment, and a structured JSON response — regardless of whether the underlying court runs CM/ECF, Odyssey, or any other system. The platform complexity is invisible to the caller.