Get latest cached score for a company.
Endpoints
GET /v1/score/{domain}
Read the latest cached score for a company. Never triggers a cold run.
GET
Get latest cached score for a company.
Cached-only score lookup. Returns the freshest stored record, or
404 if Kepler has never scored this domain.
When to use it
- After a
202fromPOST /v1/score— onceGET /v1/jobs/{job_id}reportsstatus: "complete", call this endpoint (or use thescore_urlthe job response hands you) to fetch the fresh score. The Python and TypeScript SDKs do this automatically insideKepler.score(). - To re-render an existing UI without using a cold-call slot — calls to this endpoint count against your cached quota, not cold.
What it does NOT do
- Trigger a cold run. Even with no cached record, you get
404, never a 60-second wait. - Respect the freshness window. It returns the latest record regardless of age. If you care about freshness, check the
scored_attimestamp yourself or usePOST /v1/score.
Example
Authorizations
Live keys are prefixed ki_live_, test keys ki_test_. Issue + revoke
keys at https://console.keplerinsights.us. Never embed a key in client-side
code — every endpoint is backend-to-API only.
Path Parameters
Bare hostname. Strips a leading www. and any URL scheme automatically.
Response
Latest score.
Available options:
KI-1+, KI-1, KI-2+, KI-2, KI-3, KI-4, KI-5 Required range:
0 <= x <= 100The 4 KI buckets. Each is 0–100.
Present and = sandbox only with a ki_test_ key.
Up to ~12 pts for established mega-caps; up to ~6 pts for growth profile.
Required range:
0 <= x <= 12Caller-facing metadata. Stable across versions.

