The 360 checks

60 developer and fintech platforms read on Ora's agent-readiness scan, all published on 9 November 2026, the act layer first. The median score is 73 of 100 and the highest is Fly.io at 97; Ora found an MCP server on 6 of the 60. Every page ends with the scan to run on your own surfaces.

Each day one of the platforms developers build on is read on Ora's scanner the day its check is published: payment processors, developer tools, cloud and data platforms, the companies whose APIs agents call most. Each check reads the act layer first, the surfaces an agent acts on, because that is what this directory records; then the door, what an agent can read, and whether the company is found and recommended. The score and the grade are Ora's, the grouping and the verdict are ours, and every page names the day it was read.

How to read a check

Ora scores a public domain out of 100 across four layers with 132 checks in its catalogue (contract 1.38.0, read 5 November 2026); a check that does not apply to a site is left out of its maximum, which is why a platform that sells nothing reads none apply on Payments. Each page shows the layer scores, then every applicable check in four groups with what Ora observed, the directory's own row for the domain where there is one, the fixes worth most points, and the editors' read. The scan is free and needs no account, so a reader can repeat any number the same day.

Machine-readable: reads.json (every read, with each check's status and points) and briefs.json (one short record per company). Every check has a markdown twin at its own path plus index.md.