Regulation is happening. The dates are on the calendar.
At least eleven states enacted conversational-AI statutes in 2026. Whether you have a duty today depends on where your users are, and the answer changes twice in 2027. This is the map we work from.
The checkers are being appointed.
Accurate as of August 2026, reviewed quarterly. Ikwe does not advise on which laws apply to you; that is your counsel's call.
What you actually buy
An evaluation, a report, then a re-score.
You buy an evaluation of your system against a standard scenario set: the situations the statutes are written about. What comes back is a report tied to a specific legal obligation, with every failure traced to the turn it happened on. When you have changed something, we run the same standard again and the difference goes on the record.
For Measure, our scenario set runs against your system from our end, over a simple API. For Monitor, your live anonymized traffic. Never your codebase, your system prompt, or your users' identities.
Every response passes the Safety Gate screen, then the eight-dimension standard, scored by Ikwe's judging system: multiple independent AI judges, randomized and drawn from different model families, that have to agree. Disagreement escalates for review, never averaged away.
Where you sit against the four score bands, scoped to the duty you have to answer, with every failure traced to the turn it happened on and the transcript around it. Supporting evidence, not a certificate.
You decide what to change and you make the change. We run the same standard again so the movement is documented rather than asserted. Monitor is that same standard running continuously against live traffic, sold as a subscription.
How scope is set
Scope depends on how many scenarios, how much traffic, and how specific the question is. We work that out with you up front and put it in writing before anything begins. No lock-in.
Nothing connects to your system until you have signed off on what is being scored. You own every record we produce, and nothing is published or shared without you.
And the things we will not do
The value is in what we are not.
An instrument is only worth something if the person holding it has nothing riding on the reading. Four lines we do not cross.
- No product of ours competes with the systems we score, so we have no reason to want a particular answer.
- We are not here to slow this down. We are here to make it possible to keep going.
- We describe the standard and show you where you sit against it. You decide what to change.
- If you want help changing it, we will happily tell you we are not the right people.
- We write the standard and we run it. We do not also issue a certificate against it or underwrite the risk behind it.
- A re-score says what we measured and when. It does not say you are safe, and it never will.
- We never sit between your system and the person using it, so we cannot add latency or fail in production.
- We read what your system did. We never change what it does.
We are not checking whether the data is safe. We are checking whether the person is.
The same instrument, from either side of the table.
For counsel.
If you are responding to a complaint, a civil investigative demand, or a regulator's inquiry, an engagement can be scoped with your counsel from the start, including what is produced, how work product is handled, and the timeline the matter requires. Start that conversation through the contact page and say counsel is involved.
You bought it. You did not build it.
If the conversational AI in your product is a vendor's, a Measure engagement can be commissioned by you and run on the system you are buying, as part of vendor risk review. Same instrument, same report, commissioned by the buyer rather than the builder.
Where to start
Wherever you sit on that calendar, it starts the same way.
Thirty minutes. We will tell you what is worth measuring first and scope it in writing. Nothing connects until you sign off, and the record that comes back is yours. If none of this is right for you yet, we will say so.
Usually it is the head of product, the general counsel, or whoever owns risk who brings us in. Bring whoever will have to answer the question, and whoever signs.
Your duty is already live
Your users are in California, New York or Hawaii and the obligation is running now. Measure gives you a report tied to it, and a re-score once you have changed something.
Your date is on the calendar
January 1 or July 1 of 2027. A reading now tells you how far you are from where you will have to be, while there is still time to do something about it.
No duty yet, and questions anyway
A carrier, a board, an acquirer or a customer is asking. The same standard answers them, and the record starts before anyone requires it.
A model that changes needs a reading that changes with it. A record built over time shows a trend rather than a single point.