CertScore.ai Pulse API beta

Agent-readable beta fallback

This page is a plain browser-readable fallback for agents or review tools whose JSON fetch layer cannot retrieve API endpoints. This is beta software. The current Pulse API beta version is 0.5.3. The canonical Pulse API remains /api/v1/pulse.

CertScore.ai Pulse uses automated runtime analysis of public websites to detect review signals around pre-consent tracking, third-party requests, consent enforcement gaps, cookie activity, accessibility issues, and disclosure inconsistencies.

Agent quick start

Basic HTTP agents

If you do not support OpenAPI actions, call https://certscore.ai/api/v1/pulse?url=<public URL>&format=markdown&detail=standard.
Pulse reuses an eligible completed scan from the prior 24 hours before queueing a new scan when freshness=latest. Use freshness=refresh to request a new scan when eligible. forceNewScan=true is a compatibility override; neither option bypasses validation or throttles.
Use scanFrom or geo to select the scan location. Accepted values are eu_ie.
For a quick check, use format=markdown and detail=tiny.
For structured evidence, use format=json and detail=evidence.
If you receive HTTP 202, read the returned statusUrl or poll /api/v1/pulse/status/<jobId>.
If API fetch fails before headers, body, or status are visible, do not infer CertScore.ai returned an error.

Recommended calls

GPT Action beta summary

GET /api/v1/pulse/gpt?url=https://kbdlab.io&format=markdown&detail=standard&wait=35

User-facing summary

GET /api/v1/pulse?url=https://kbdlab.io&format=markdown&detail=standard

Quick machine triage

GET /api/v1/pulse?url=https://kbdlab.io&detail=tiny

Evidence/deeper review

GET /api/v1/pulse?url=https://kbdlab.io&detail=evidence

Connectivity check

GET /api/v1/pulse-self-test

Health check

GET /api/v1/pulse-health

Summary JSON is best for concise agent output. Markdown is best for conversational summaries. Tiny is best for badges, triage, and routing. Evidence JSON is best for evidence review and coverage diagnostics. Self-test is best for deployment and agent connectivity checks.

OpenAPI / GPT Action beta agents

If you support OpenAPI actions or tools, import https://certscore.ai/api/v1/openapi.chatgpt.json.
Call getPulseForUrl with url, format=markdown, and detail=standard, optional scanFrom, and wait=35.
Use detail=tiny for quick checks.
Public GPT Action beta access uses latest-mode summaries. Use Evidence JSON or link users to the CertScore.ai report when they need more support.

How to interpret fetch failures

A successful CertScore.ai Pulse response includes the diagnostic headers below. If a checker reports an internal fetch error and cannot show these headers, it did not successfully evaluate the CertScore.ai application response.

Agent fetch limitations: Some agent environments may fail before receiving an HTTP response because of DNS, sandbox, TLS, proxy, or fetch-layer limitations. If a request fails before exposing an HTTP status, response body, or x-certscore-* diagnostic headers, do not conclude CertScore.ai Pulse is unavailable. First try /api/v1/pulse-self-test, /api/v1/pulse-health, /api-pulse-agent-guide.txt, /.well-known/certscore-pulse, and /api/v1/openapi.chatgpt.json. If those also fail without HTTP status or CertScore.ai diagnostic headers, report it as a client/network fetch limitation rather than a CertScore.ai API result.

x-certscore-pulse: v1
x-certscore-route: pulse-self-test | pulse-health | openapi | openapi-chatgpt | discovery | pulse | pulse-status
x-certscore-request-id: <uuid>

Canonical endpoints

Plain text guide

https://certscore.ai/api-pulse-agent-guide.txt

Self-test canary

https://certscore.ai/api/v1/pulse-self-test

Health canary

https://certscore.ai/api/v1/pulse-health

OpenAPI JSON

https://certscore.ai/api/v1/openapi.json

ChatGPT Action beta schema

https://certscore.ai/api/v1/openapi.chatgpt.json

Universal AI/API discovery JSON

https://certscore.ai/.well-known/certscore-ai.json

Discovery JSON

https://certscore.ai/.well-known/certscore-pulse

Full LLM guide

https://certscore.ai/llms-full.txt

Tiny Pulse JSON

https://certscore.ai/api/v1/pulse?url=https://kbdlab.io&detail=tiny

Summary Pulse JSON

https://certscore.ai/api/v1/pulse?url=https://kbdlab.io&detail=summary

Evidence Pulse JSON

https://certscore.ai/api/v1/pulse?url=https://kbdlab.io&detail=evidence

Pulse markdown

https://certscore.ai/api/v1/pulse?url=https://kbdlab.io&format=markdown

Invalid URL contract

https://certscore.ai/api/v1/pulse?url=%3A%3A%3A%3A

Missing job contract

https://certscore.ai/api/v1/pulse/status/pulse_job_nonexistent_test

Expected public contract

Health, OpenAPI, and discovery endpoints return HTTP 200 with JSON.
Valid Pulse URL requests return a documented 200, 202, or 429 response.
Markdown requests may return HTTP 200 with text/markdown, or a documented JSON status/error shape.
Invalid URL input returns HTTP 400 JSON with error code invalid_url.
Unknown status jobs return HTTP 404 JSON with error code not_found.

Fallback workflow

Open the health canary first and confirm the CertScore.ai diagnostic headers.
If the health canary is unavailable only inside one tool, treat that as a tool fetch/DNS failure.
Use the Pulse markdown endpoint when a tool prefers readable text over JSON.
Use the ChatGPT Action beta schema when configuring a Custom GPT beta action.
Use the Evidence JSON endpoint when structured finding, evidence, and review context are needed.

CertScore.ai outputs are automated public-web observations for review. They are not legal advice, certification, or a compliance determination. Always review the underlying evidence and consult qualified experts where appropriate.

Pulse API docs Plain text guide ChatGPT Action beta schema llms.txt llms-full.txt AI discovery manifest Findings reference