BUILD
Crawld and REST API
Live: automate scans and read scorecards from your own code.
Status: Available now . Queue a scan, poll it, read the scorecard. Documented in full on the docs page. The API automates the measurement half of the product. It writes nothing to your site.
Delivery mode E · URL only
Verified Advisory. The API reads public HTML and returns a scorecard. Nothing is written on your behalf.
What you can do
- Queue a scan for a URL and poll it to completion
- Read the scorecard: score, category scores, coverage
- Read the findings list once a scan is unlocked
Limits
- The public scan surface is unauthenticated, limited to 3 submissions an hour per caller, and capped at 10 pages
- One real crawl per domain per day; repeat calls return that day's scan
- The authenticated API is not publicly documented yet
Where this sits
| Mode | What we get | How changes arrive | Verified | Status |
|---|---|---|---|---|
| A · Repo write | A repo we can push a branch to | Pull request; you review and merge | Build | In progress |
| B · Read-only repo | Read access plus somewhere to push | Branch or fork you own | Build | In progress |
| C · Cloud mirror | A snapshot or export | Patch or PR from a clone | Build (mirror) | In progress |
| D · CMS drafts | OAuth into a hosted CMS | Unpublished drafts; you publish | Preview | In progress |
| E · URL only | A public URL | Written-out fixes; you apply | Advisory | Live |
Build-verified means a build ran. It applies to A, B and C and nothing else. A hosted CMS has no build, so D is preview-verified and E is advisory. Those labels are never blurred.