Bill Commons

OH HB 628

in committee

License artificial intelligence risk mitigation organizations

Ohio · 2025-2026 Regular Session (136th General Assembly) · lower

Quick answers

Did OH HB 628 pass?

Not yet. OH HB 628 is in committee as of 2026-02-04 and has not come to a final vote. Latest recorded action (2026-02-04): Referred to committee

What is OH HB 628 about?

To enact sections 3755.01, 3755.02, 3755.03, 3755.04, 3755.041, 3755.05, 3755.06, 3755.07, 3755.08, 3755.09, 3755.091, 3755.10, 3755.11, and 3755.12 of the Revised Code to create an independent verification organization license for verifying artificial intelligence risk mitigation.

Who sponsors OH HB 628?

Ty D. Mathews is the primary sponsor of OH HB 628, joined by 4 cosponsors.

Description

To enact sections 3755.01, 3755.02, 3755.03, 3755.04, 3755.041, 3755.05, 3755.06, 3755.07, 3755.08, 3755.09, 3755.091, 3755.10, 3755.11, and 3755.12 of the Revised Code to create an independent verification organization license for verifying artificial intelligence risk mitigation.

Introduced
2025-12-11
Latest action
2026-02-04 — Referred to committee
Bill type
bill
Last updated

Subjects

Sponsors

  • Ty D. Mathewsprimary
  • Kevin Rittercosponsor
  • Thomas Hallcosponsor
  • Tex Fischercosponsor
  • Kellie Deetercosponsor

Committees

Not provided by source.

Action timeline

  1. 2025-12-11

    Introduced

    introduction

  2. 2026-02-04

    Referred to committee

    referral-committee

Versions

Documents

Votes

Not provided by source.

Related bills

No related bills recorded for this bill.

Official source

Attribution

Data from openstates_bulk_csv, retrieved 2026-07-24T05:30:02.217700Z

Inspect retained evidence for changes recorded after evidence tracking began:

Use this data

Every field on this page is available from the free public API — no key or licence required. Fetch this bill as JSON: GET /api/v1/bills?jurisdiction=OH&identifier=HB 628. See the API docs or the MCP server for AI assistants.

Known limitations

  • Sponsor party and chamber affiliation are not yet captured by this API.
  • Committee referrals are not yet captured.

See the methodology page for data sources and limitations.