is-agentic & the essentials score

We partnered with Vercel on is-agentic.com: a scanner tailored for the sites builders ship on Vercel, powered by the ora ranking. Every scan on is-agentic is run by ora.

The full ranker measures products agents transact with: API surfaces, MCP servers, payment rails. Most websites do not need half of that catalog. A content or marketing site’s job is to be found, read, and used - there is no API to gate and no checkout to wire. The essentials score reads the same scan through that lens: a small set of essential checks shares a fixed 80 points, recommended checks share 20, and forward-looking signals only ever add, capped at +5.

One scan, two readings

Nothing is scanned twice and nothing changes in the canonical score. The essentials reading is computed from the same check results at response time, so fixing a check can lift both numbers. Your grade, the leaderboard, and stored results are untouched.

Run it yourself by adding one query flag to a scan or a cached score read:

Get the essentials reading

curl -X POST "https://ora.ai/api/scan?include=essentials" \
  -H "Content-Type: application/json" \
  -d '{"url": "your-site.com"}'

The response gains one top-level essentials object beside score: its own 0-100 score and label, the required and recommended buckets, an ordered issues list, and a per-check map with each check’s essentials tier and the points a fix earns. The same flag works on GET /api/score/{domain} and on GET /api/checks, where it annotates the catalog with each check’s essentials tier. Which one to run: is-agentic gives you the essentials fast and in plain language; the full scan goes deeper. The launch post has the full story.