---
title: "Corrections log | Agent Readiness Compare"
description: "How to report an error on Agent Readiness Compare, how it is checked and fixed, how published data conflicts are shown, and the dated corrections log."
canonical: https://agentreadinesscompare.com/corrections/
site: "Agent Readiness Compare"
last_updated: 2026-11-05
section: "Reference"
---

# Corrections log | Agent Readiness Compare

> How to report an error on Agent Readiness Compare, how it is checked and fixed, how published data conflicts are shown, and the dated corrections log.

Source: https://agentreadinesscompare.com/corrections/
Site: Agent Readiness Compare
Last reviewed: 2026-11-05

# Corrections

How to report an error, what happens next, and a log of every change made after publication.

In short

To report an error, use the contact form and choose the topic Correction to vendor or data information. We check the claim against the primary source, fix the page, date the fix and list it in the log below. Where two primary sources disagree, the site shows the conflict instead of correcting it.

## 1. Report an error through the contact form

Use the [contact form](https://agentreadinesscompare.com/contact/) and choose the topic Correction to vendor or data information. Give the URL of the page, the statement you think is wrong, and the primary source that shows it. A vendor can report an error about its own entry in the same way.

## 2. Each report goes through the same four steps

1.  We check the statement against the primary source, not against another summary.
2.  If the statement is wrong, we fix the page and show the date of the fix on the page.
3.  We list the change in the corrections log below.
4.  If the source has changed since our read date, we update the read date and say so. If we cannot confirm the report, we say that too.

A vendor's statement about itself is treated as a vendor claim until a primary page shows it. Replies go to the address you give in the form.

## 3. Conflicts between primary sources are published, not corrected

Sometimes two primary pages from the same vendor disagree. The site does not pick one and hide the other. It shows both, with each source and read date, and says that they conflict. Two examples read on 2026-11-04:

-   Ora's check count is 132 in its API catalog at contract 1.38.0 and 126 on its methodology page. The gap is in the Usability layer, listed as 68 checks in the API and 62 on the methodology page.
-   The agentready.org header lists its partner organisations without MIT, while the repository README states the MIT licence.

If a vendor resolves such a conflict, we update the page and the read date. That is an update, not a correction.

## 4. The corrections log lists every change after publication

| Date | Page | What changed |
| --- | --- | --- |
| 2026-11-04 | Whole site | First edition of the rebuilt site: no corrections yet |

We never backdate. Each row carries the day the change was made.

## 5. Related

-   [Editorial policy](https://agentreadinesscompare.com/editorial-policy/)
-   [Contact](https://agentreadinesscompare.com/contact/)
-   [About](https://agentreadinesscompare.com/about/)
-   [Method](https://agentreadinesscompare.com/method/)

## 6. Sources

1.  Ora, check catalog. [https://ora.ai/api/checks](https://ora.ai/api/checks?utm_source=agentreadinesscompare.com&utm_medium=referral&utm_campaign=page), read 2026-11-04.
2.  Ora, methodology. [https://ora.ai/methodology](https://ora.ai/methodology?utm_source=agentreadinesscompare.com&utm_medium=referral&utm_campaign=page), read 2026-11-04.
3.  AgentReady.org. [https://agentready.org/](https://agentready.org/?utm_source=agentreadinesscompare.com&utm_medium=referral&utm_campaign=page), read 2026-11-04.
4.  AgentReady.org repository README. [https://github.com/agentready-org/standard/blob/main/README.md](https://github.com/agentready-org/standard/blob/main/README.md), read 2026-11-04.

Last reviewed 2026-11-05
