ConduitScore API access, explained simply
ConduitScore's API lets another piece of software use the scoring engine automatically. Scale customers receive an API key they can use to run scans, fetch scan history, and connect ConduitScore to their own dashboards or workflows.
Customers get controlled access, not your backend
Scale customers do not receive ConduitScore's code or infrastructure. They receive an API key. That key authorizes specific API requests so their own software can send domains to ConduitScore and get structured results back. See every check the API runs across 7 categories.
Why customers would want it
API access matters when ConduitScore needs to fit into a workflow, not just be used manually in the browser. See how agencies scale audits across client portfolios.
One endpoint anyone can understand
ConduitScore also exposes a simple public score lookup endpoint. This shows what the API returns, while keeping Scale-only authenticated access behind API keys. The score reflects signals like structured data and crawler access — see our methodology for the full breakdown.
Public endpoint
GET /api/public/domain/{domain}/score
curl "https://conduitscore.com/api/public/domain/example.com/score"
{
"domain": "example.com",
"score": 67,
"grade": "B",
"scanned_at": "2026-03-26T00:00:00.000Z"
}Where Scale customers get the real integration details
The public page explains what the API is and why it exists. Scale customers get API keys from Billing, plus the authenticated examples and operational details they need to actually connect their systems.
Scale flow
- 1. Upgrade to Scale.
- 2. Open Billing and create an API key.
- 3. Use that key to authenticate your scan requests.
- 4. Manage keys and examples from inside the app.