Base URL
All API requests should be made to:Core Endpoints
1. List Indexes
GET/list-indexes
Retrieve a list of all indexed services (SDKs, CLIs, APIs) available for context retrieval.
- Purpose: Discover available indexed services and their identifiers
- Returns: List of indexed services with
index_id
, name, and type - Use Case: Find available documentation sources before querying for context
- Error codes:
- 404: User account not found
- 401: API key missing or invalid API key
2. Get Context
POST/get-context
Retrieve relevant documentation, code examples, and usage guides from indexed services.
- Purpose: Search indexed services for specific documentation and examples
- Returns: Formatted context string with relevant documentation
- Use Case: Power AI assistants, chatbots, or developer tools with up-to-date documentation
- Error codes:
- 400: Missing index_id parameter
- 404: Index not found or User account not found
- 401: API key missing or invalid API key
Authentication
All endpoints require API key authentication via theAPI-Key
header:
Response Formats
All endpoints return JSON responses with a consistent structure:- HTTP Status Codes: Standard REST conventions (200, 400, 401, 404, etc.)
Rate Limits
- API endpoints: 100 requests per minute per API key
- Context retrieval: Unlimited queries based on your subscription plan
Error Handling
All endpoints return structured error responses:400
: Missing required parameters401
: Invalid or missing API key404
: Resource not found (index, user account)429
: Rate limit exceeded
Getting Started
To start using the API:- Get your API key from the Harvest dashboard
- Call
list-indexes
to discover available indexed services - Use
get-context
with anindex_id
to retrieve documentation and examples
Example Workflow
Use the
index_id
values returned from list-indexes
to query specific services with get-context
.