API Overview
The Lightfast API provides memory built for teams. Search by meaning across everything your engineering org produces — pull requests, issues, discussions, docs, and deployments.
Search
Base URL
https://lightfast.ai/api/v1
Authentication
All API requests require one header:
The organization is resolved automatically from the API key. See Authentication for details on obtaining API keys.
Quick Start
Make Your First Call
Core Features
Search by Meaning
Unlike keyword search, Lightfast understands intent and context:
Finds:
- Pull requests titled "Email login refactor"
- Issues about "login security improvements"
- Discussions on "user session management"
Multi-Path Retrieval
Search uses four parallel paths for comprehensive results:
- Vector search: Semantic similarity
- Entity search: Shared entities (people, repos, topics)
- Cluster search: Topic cluster membership
- Actor search: Contributor expertise
Search Modes
Control quality vs. latency with the mode parameter:
| Mode | Description | Typical Latency |
|---|---|---|
fast | Vector scores only | ~50ms |
balanced | Cohere reranking | ~130ms |
thorough | LLM-based scoring | ~600ms |
Filtering
Filter results by type, contributor, entity, or date:
See Search for all filter options.
Error Handling
All errors follow a consistent format:
Common Error Codes
| Code | Status | Description |
|---|---|---|
VALIDATION_ERROR | 400 | Invalid request parameters |
UNAUTHORIZED | 401 | Missing or invalid authentication |
FORBIDDEN | 403 | Access denied to organization |
NOT_FOUND | 404 | Resource not found |
INTERNAL_ERROR | 500 | Server error |
See Error Reference for complete list and handling strategies.
What Can Be Searched?
Lightfast searches workspace memory that your organization has loaded into the platform:
- Decision records, runbooks, and documentation
- Engineering observations and incident notes
- Entities such as services, repositories, projects, and people
Create an organization, add an API key, and use the API or MCP server to query the memory available to that organization.
Next Steps
- POST /v1/search — Search by meaning
- Authentication — API key setup
- Errors — Error handling