Web Check · feature

Website audit API (53 checks in one JSON call, or one check at a time)

The website audit API of Web Check hands a script or a service the same engine that draws the report pages. You send a GET request with a page address and receive JSON. Every check has its own endpoint, and one more call runs the full audit. It is meant for developers who want audit data in a pipeline, a dashboard or an internal tool.

Website audit API: a GET request to audit-full and the JSON response with score and issues

What the website audit API gives you

One engine serves two kinds of output: report pages in the browser and an HTTP API. Anything you see on a report page can be read as JSON.

Every check is a separate endpoint: GET https://webcheck.asibots.pro/api/<check>?url=<address> returns JSON.
Documentation with the list of endpoints, examples and the response schema lives at /web-check-api and /web-check-api/spec.
The full audit has 53 check sections, so a single call can cover security, SEO, speed and AI readiness together.

The 53 sections are: ai-lite, engagement, ai-access, archives, block-lists, canonical, carbon, cookies, crux, delivery, dns, dns-server, dnssec, firewall, geo-readiness, headers, hreflang, hsts, http-security, image-seo, js-render, link-health, linked-pages, llms-txt, llms-validate, location, mail-config, mixed-content, onpage-seo, ports, privacy, pwa, quality, rank, readability, redirects, robots-txt, schema-org, security-txt, shodan, sitemap, sitemap-deep, social-tags, ssl, status, subdomains, tech-stack, threats, tls-connection, tls-labs, trace-route, txt-records, whois.

Calls and the shape of the response

Four calls cover most uses of the website audit API.

audit-full runs the whole audit and returns the total score, the group (band), counters, the remarks in issues sorted from important to minor, and the data of every section in checks.
ai-lite returns the five AI signals and a score within seconds.
engagement returns the page structure review; with &llm=1 it adds the deep model review.
page-audit scores a single page against the page criteria.

GET https://webcheck.asibots.pro/api/audit-full?url=PAGE_URL
GET https://webcheck.asibots.pro/api/ai-lite?url=PAGE_URL
GET https://webcheck.asibots.pro/api/engagement?url=PAGE_URL&llm=1
GET https://webcheck.asibots.pro/api/page-audit?url=PAGE_URL

How a call goes, step by step

A request to the website audit API takes five steps.

You pick a check, or audit-full for everything.
You send GET with the page address in the url parameter.
The service refuses an address inside an internal network with a 400 answer and otherwise runs the check.
In the full audit, slow sections drop out by timeout and do not hold up the others. The whole run takes around 40 seconds.
You get JSON in which the section keys match the names of the checks. CORS is open, so a script on a web page can read the answer directly.

History and the score badge

The nightly auto-audit of ASI Bots' own sites runs on Monday, Wednesday and Friday and writes its results to a database with history. The history is public: you read it through the functions site_audits_latest and site_audits_history (Supabase RPC).

The same history feeds a badge. The script score-badge.js, served from bugfix.asibots.pro, shows a live circle with the score on any site and is connected with one tag.

Where it helps in practice

After a deployment. A script uses the website audit API to call audit-full for the key pages and reads the score and the top of issues.
In a dashboard. The history functions give a series of scores that you can plot next to your own metrics.
In an internal tool. Take only the section you need, for example http-security or delivery, and skip the rest.

The report pages and the API run on one engine, so the numbers in your tool and on the page come from the same checks.

Errors, limits and honest gates

The website audit API answers an internal address with 400. Exceeding the limits gets 429 with a clear text.
The API accepts 2 requests per second. Heavy checks with a browser (screenshot, cookies, tech-stack, audit-full) run at most 4 at a time for all visitors together and 12 per minute for one visitor. Port scanning and trace-route allow 6 per minute.
A response through Cloudflare is capped at 100 seconds, and a full audit needs around 40.
The active chatbot test, ai-agent-security, is a separate endpoint and is not among the 53 sections.

Frequently asked questions

Is there one call that returns everything?

Yes: GET /api/audit-full?url=… returns the total score, the group, the counters, the issues sorted by importance and the data of all sections under checks . It takes around 40 seconds.

Can I call the website audit API from a browser script?

Yes. The answer is JSON and CORS is open, so a script on a web page can read it. Keep in mind the limits: 2 requests per second, and 429 with a text when they are exceeded.

Where do I find the list of endpoints and the response schema?

On /web-check-api and /web-check-api/spec . There you see the endpoints, call examples and the schema of the response.

Open the API docs