Skip to main content
GET
/
v1
/
company
/
{domain}
/
confidence
Confidence band + data-completeness diagnostics for a score.
curl --request GET \
  --url https://api.keplerinsights.us/v1/company/{domain}/confidence \
  --header 'X-API-Key: <api-key>'
import requests

url = "https://api.keplerinsights.us/v1/company/{domain}/confidence"

headers = {"X-API-Key": "<api-key>"}

response = requests.get(url, headers=headers)

print(response.text)
const options = {method: 'GET', headers: {'X-API-Key': '<api-key>'}};

fetch('https://api.keplerinsights.us/v1/company/{domain}/confidence', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));
<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api.keplerinsights.us/v1/company/{domain}/confidence",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => [
    "X-API-Key: <api-key>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}
package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.keplerinsights.us/v1/company/{domain}/confidence"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("X-API-Key", "<api-key>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}
HttpResponse<String> response = Unirest.get("https://api.keplerinsights.us/v1/company/{domain}/confidence")
  .header("X-API-Key", "<api-key>")
  .asString();
require 'uri'
require 'net/http'

url = URI("https://api.keplerinsights.us/v1/company/{domain}/confidence")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Get.new(url)
request["X-API-Key"] = '<api-key>'

response = http.request(request)
puts response.read_body
{
  "mode": "<string>",
  "domain": "<string>",
  "scored_at": "2023-11-07T05:31:56Z",
  "completeness_pct": 50,
  "failed_fetchers": [],
  "data_warnings": [
    "<string>"
  ],
  "missing_signals": [
    "<string>"
  ]
}
{
  "error": "unauthorized",
  "message": "<string>",
  "reason": "<string>"
}
{
  "error": "unauthorized",
  "message": "<string>",
  "reason": "<string>"
}
A composite_score of 67 sounds the same whether it was computed on full data or half-empty fetcher results. This endpoint exposes the difference: data completeness, failed fetchers, and which signals fell back to neutral defaults.

​
When to use it

  • Before trusting a score for a high-stakes decision.
  • To render a “confidence” pill next to the score in your UI.
  • To explain to a stakeholder why a small / private company has a directional rather than precise score.

​
The three bands

BandMeaning
highCompleteness ≥80% and no critical fetcher failures. Trust the number.
medium60–79% completeness, or one non-critical fetcher missing. Use as a directional indicator; cross-check critical buckets.
directional<60% completeness or a critical data fetcher failed. Treat the composite as a rough position, not a precise reading.

​
Response shape

{
  "domain": "stripe.com",
  "scored_at": "2026-05-12T18:30:00Z",
  "band": "high",
  "completeness_pct": 92,
  "failed_fetchers": [],
  "data_warnings": [],
  "missing_signals": ["state_legislative_activity"]
}
For comparison, a thinly-covered domain: 
{
  "domain": "obscurestartup.com",
  "scored_at": "2026-05-12T14:00:00Z",
  "band": "directional",
  "completeness_pct": 51,
  "failed_fetchers": ["people"],
  "data_warnings": ["people_no_founder_data"],
  "missing_signals": [
    "founder_years_experience",
    "founder_prior_exits",
    "cofounder_skill_diversity",
    "domain_expertise_match"
  ]
}

​
missing_signals semantics

A signal is “missing” if it’s currently scoring at the neutral fallback (≈ 50 / 100). This is not the same as a zero — neutral 50 means “we have no real data, so we’re not penalizing or rewarding.” A long missing list pulls the composite toward 50.

​
How completeness is computed

A weighted ratio of “signals with real underlying data” / “signals applicable to the target’s profile”. Established companies have different applicable signals than growth companies (some venture-stage signals are N/A for mature firms), so the denominator is profile-aware.

Authorizations

​
X-API-Key
string
header
required

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

​
domain
string
required

Bare hostname. Strips a leading www. and any URL scheme automatically.

Response

Confidence breakdown.

​
mode
string
​
domain
string
​
scored_at
string<date-time>
​
band
enum<string>
Available options:
high,
medium,
directional
​
completeness_pct
integer
Required range: 0 <= x <= 100
​
failed_fetchers
enum<string>[]
Available options:
firmographic,
people,
web,
news
​
data_warnings
string[]
​
missing_signals
string[]

Signals currently scoring at the neutral 50 fallback.