Skip to main content

Overview

The Hindsight API provides access to competitive intelligence, win-loss insights, and deal data through two integration methods:
  1. REST API - either receive a complete, cited AI response or call supported Hindsight tools directly
  2. Model Context Protocol (MCP) - Individual tools your AI assistant orchestrates directly
This page covers the REST API. Direct REST tool calls and MCP calls use the same authorization, validation, limits, and underlying tool execution.

When to Use Each

  • REST API responses: For Glean, Slack bots, and search interfaces that want a finished, synthesized answer
  • REST API tools: For server-side applications that need structured search or retrieval results without an LLM-generated response
  • MCP: For Claude, ChatGPT, Cursor, or other MCP clients that orchestrate tools themselves

Authentication

All API requests require authentication using an API key in the header:
Get your API keys from the Hindsight dashboard. API Keys

REST API

The REST API has two surfaces. Use Responses when you want Hindsight’s AI to orchestrate multiple searches and return a synthesized, cited answer. Use Tools when your application needs structured results and controls the workflow itself. Best for: Glean, Slack bots, search interfaces, custom applications

Endpoint

Request Format

Response Format

Streaming Support

Enable streaming for real-time responses:
Stream format follows SSE (Server-Sent Events):

Direct Tool API

Direct tool endpoints accept JSON input and return structured JSON. They are useful when you know the retrieval step you need and want to compose the workflow in your own service. The recommended deal-research flow is:
  1. Call select-deal to filter and triage analyzed deals.
  2. Pass the returned deal_id values to get-deal for summaries and competitor positioning.
See the Direct Tool API reference for the complete list of available deal research, competitive intelligence, web research, and data-analysis tools. For a client-side AI assistant that should choose and sequence tools itself, use MCP instead.

Document Upload API

Upload documents to your Hindsight knowledge base or associate them with specific deals.

Upload to Knowledge Base

Upload competitive intelligence documents, assets, and other files to your library.

Request Format

Send as multipart/form-data:

Parameters

*Either file_url or file is required
**Either competitor_id or competitor_name is required

Response


Upload to Deal

Associate documents with specific deals for win-loss analysis.

Request Format

Send as multipart/form-data:

Parameters

*Either file_url or file is required
**One of deal_id, salesforce_id, or hubspot_id is required

Supported File Types

  • Documents: PDF, Word, PowerPoint, Excel, Markdown, plain text
  • Audio: MP3, WAV, M4A (automatically transcribed)
  • Video: MP4 (automatically transcribed)

Response

Example Usage

Once configured, you can ask Claude questions like:
  • “Find deals where we lost to Competitor X in the last quarter”
  • “What are the top security objections we’ve encountered?”
  • “Search for pricing discussions in enterprise deals”
  • “Show me competitor intel on Salesforce’s integration strategy”
Claude will automatically call the appropriate Hindsight tools and synthesize the results

Common Use Cases

Use Case 1: Glean Integration

Integrate Hindsight as a data source in Glean to answer competitive intelligence and win-loss questions. REST API Example:
Best for: When you want comprehensive, cited answers in Glean search results.

Use Case 2: Claude Desktop for Sales Prep

Use Claude with Hindsight tools to prepare for sales calls, analyze deals, and get competitive intel. Example Conversation:
Best for: Sales reps preparing for calls, analyzing win/loss patterns, researching competitors.

Use Case 3: Custom Slack Bot

Build a Slack bot that answers team questions about deals and competitors. REST API Example:
Best for: Team-wide access to competitive intelligence and deal insights.

Rate Limits

All API and MCP calls are limited per organization, not per user, API key, or endpoint. The per-minute limit is shared across the organization’s API and MCP traffic and uses a 60-second sliding window. select-deal and get-deal each consume one read from the shared monthly reads bucket after authorization and input validation succeed. That bucket is also shared with other read-class Hindsight tools, whether called over REST or MCP. Organization-specific allowances may differ from the plan defaults. Successful direct-tool responses include these headers: On a 429, inspect the same headers and retry after the stated reset time. A rate-limited call does not consume monthly usage.

Error Handling

All errors follow this format:

Error Codes

  • 400 - Bad Request (invalid parameters)
  • 401 - Unauthorized (invalid API key)
  • 403 - Forbidden (insufficient permissions)
  • 404 - Not Found (resource doesn’t exist)
  • 429 - Too Many Requests (rate limit or monthly usage quota exceeded)
  • 500 - Internal Server Error

Next Steps

Get API Key

Generate your API key from the dashboard

MCP Setup Guide

Detailed MCP configuration and the full tool reference

AI Responses

Full reference for the responses endpoint

Direct Tool API

Browse every structured-search and analysis tool

Platform Overview

How the verified deal layer is built