Kepler API — Developer Console

API Keys

Programmatic access · v1

Your keys

Keys are shown once at creation — copy and store securely. Use as the X-API-Key header on requests to https://api.keplerinsights.us/v1/*.

Usage

Current billing period

Loading…

How counts work

Counters reset on the 1st of each month, UTC. The X-API-Key header on each request determines which user's counters move.

Cold calls trigger fetcher fan-out + scoring engine. Billable, count against your tier's cold-call allowance.
Cached calls return the latest stored score within your tier's freshness window. Cheap, count against the larger cached allowance.
ki_test_ (sandbox) keys never increment these counters.

Quickstart

Score your first domain in <5 minutes

1 · Create a key

Open the API Keys tab and create a ki_live_ key. Copy it — it'll only show once.

2 · Score a domain

# POST a domain to the score endpoint:
curl -X POST https://api.keplerinsights.us/v1/score \
  -H "X-API-Key: ki_live_..." \
  -H "Content-Type: application/json" \
  -d '{"domain": "stripe.com"}'

3 · Read it back

# Subsequent reads hit cache (cheap):
curl https://api.keplerinsights.us/v1/score/stripe.com \
  -H "X-API-Key: ki_live_..."

Cold vs cached

Cold calls trigger fetcher fan-out (slow, billable). Cached calls return the latest stored score (fast, cheap). Each tier sets a cache freshness window — within that window, repeat scores are free.

Use ki_test_ keys to hit the sandbox: canned responses, no fetcher calls, no billing. Full pricing detail in the Docs tab once it ships (Phase D).

Developer console