> ## Documentation Index > Fetch the complete documentation index at: https://docs.keplerinsights.us/llms.txt > Use this file to discover all available pages before exploring further. # GET /v1/score/{domain}/history > Time-series of every score Kepler has ever produced for a company. Returns every stored scoring run for `domain`, DESC by `scored_at`. Paginated. ## When to use it * Plot a score trajectory chart. * Detect rating changes (`KI-2+` → `KI-1`). * Inspect how a particular event (funding round, leadership change, press coverage) moved the buckets. ## Pagination Default `limit=100`, max `500`. Responses include `next_cursor` when more pages exist: ```bash theme={null} curl "https://api.keplerinsights.us/v1/score/stripe.com/history?limit=50" \ -H "X-API-Key: ki_live_..." ``` ```json theme={null} { "domain": "stripe.com", "records": [ { "scored_at": "2026-05-12T18:30:00Z", "composite_score": 78.2, "ki_rating": "KI-1+", ... }, { "scored_at": "2026-05-11T18:30:00Z", "composite_score": 77.9, "ki_rating": "KI-1+", ... } ], "next_cursor": "MjAyNi0wNS0xMVQxODozMDowMFo=" } ``` Pass the cursor back: ``` GET /v1/score/stripe.com/history?limit=50&cursor=MjAyNi0wNS0xMVQxODozMDowMFo= ``` When there's no `next_cursor` in the response, you've reached the end. ## What's in a record Each entry is a **curated** subset of the internal score record — the time-series core only. Notably absent vs the portal: * ❌ `top_signals` (with guidance cards) * ❌ `executive_summary` * ❌ `signal_movers` / `curated_signals` These are portal-rendered narrative fields, not core scoring data. If you need them, use the portal-side surfaces — they're a different SKU. What you do get on every record: * `scored_at`, `composite_score`, `scale_premium`, `ki_rating`, `momentum_index` * Full `buckets` block (4 floats) * `data_completeness_pct` ## Volume note A company scored daily for 12 months has \~365 records, each \<1KB after curation. The full table for a single domain fits comfortably in one or two pages of `limit=500`. Don't worry about volume. ## Stale → fresh promotion If you want the **current** score, don't paginate to the head of the list — call `GET /v1/score/{domain}` instead. It's a single-shot lookup and counts against your cached quota the same way. ## OpenAPI ````yaml GET /v1/score/{domain}/history openapi: 3.1.0 info: title: Kepler Insights API version: 1.0.0 summary: Curated company-scoring intelligence over a 67-signal engine. description: > The Kepler Insights API exposes a curated subset of the Kepler scoring engine over a stable REST surface. Every score is a composite over 67 signals organized into 4 buckets (Team & Structure, Market Position, Momentum & Tailwinds, Financial Health), with a separate scale premium that lifts established companies whose underlying fundamentals justify a higher tier. **Authentication.** All requests require a single header: `X-API-Key`. Keys are issued from the developer console at `https://console.keplerinsights.us`. **Sandbox.** Test keys prefixed `ki_test_` accept only the four canned domains (`acme.test`, `unicorn.test`, `struggling.test`, `cohort.test`), never invoke fetchers, and return deterministic responses tagged with `mode: sandbox`. Live keys prefixed `ki_live_` reject test domains and run against the real engine. **Cold vs cached.** `GET /v1/score/{domain}` is always cached (404 if no recent record exists). `POST /v1/score` decides per-call based on your tier's freshness window: a fresh record returns inline (`200`), a stale or missing one queues a cold pipeline run and returns `202` with a `job_id` to poll. Cold spend is bounded by per-tier monthly caps + circuit breakers. contact: name: Kepler Insights API support email: noah@keplerinsights.us license: name: Proprietary servers: - url: https://api.keplerinsights.us description: Production security: - apiKey: [] tags: - name: scoring description: Score a company and retrieve the latest result. - name: history description: Time-series of past scoring runs for a single company. - name: company description: Per-company analytics (cohort, confidence). - name: universe description: Distribution + movers across the full scored universe. - name: meta description: Signal manifest + caller usage + async job tracking. paths: /v1/score/{domain}/history: get: tags: - history summary: Time-series of past scores for a company. operationId: getHistory parameters: - $ref: '#/components/parameters/DomainPath' - in: query name: limit schema: type: integer minimum: 1 maximum: 500 default: 100 - in: query name: cursor schema: type: string description: >- Opaque pagination cursor. Pass back `next_cursor` from the previous response. responses: '200': description: Paginated history (DESC by scored_at). content: application/json: schema: type: object required: - domain - records properties: mode: type: string description: Present and = `sandbox` only when using a ki_test_ key. domain: type: string records: type: array items: $ref: '#/components/schemas/HistoryRecord' next_cursor: type: string description: >- Set when more pages exist. Pass into `cursor` on the next call. '401': $ref: '#/components/responses/Unauthorized' components: parameters: DomainPath: in: path name: domain required: true schema: type: string example: stripe.com description: Bare hostname. Strips a leading `www.` and any URL scheme automatically. schemas: HistoryRecord: type: object properties: scored_at: type: string format: date-time composite_score: type: number format: float scale_premium: type: number format: float ki_rating: type: string momentum_index: type: number format: float description: Smoothed rate-of-change indicator over the last few scoring runs. buckets: $ref: '#/components/schemas/Buckets' data_completeness_pct: type: integer minimum: 0 maximum: 100 Buckets: type: object description: The 4 KI buckets. Each is 0–100. properties: team_structure: type: number format: float minimum: 0 maximum: 100 market_position: type: number format: float minimum: 0 maximum: 100 momentum_tailwinds: type: number format: float minimum: 0 maximum: 100 financial_health: type: number format: float minimum: 0 maximum: 100 ErrorResponse: type: object properties: error: type: string example: unauthorized message: type: string reason: type: string description: Additional context for rate-limit responses. responses: Unauthorized: description: Missing or invalid `X-API-Key`. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: apiKey: type: apiKey in: header name: X-API-Key description: > 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. ````