API Reference
The brinicle HTTP server provides a RESTful API for managing indexes, ingesting data, and performing searches. The server runs on port 1984 by default and accepts JSON requests with binary protocols for high-throughput operations.Base URL
Authentication
The current version of the brinicle HTTP server does not implement authentication. For production deployments, it is recommended to place the server behind a reverse proxy that handles authentication and TLS termination.Content Types
The API uses two content types:application/json— For most operations (create, init, finalize, delete, etc.)application/octet-stream— For binary operations (batch ingest, search)
Response Format
Most endpoints return a JSON response with the following common structure:detail field:
HTTP Status Codes
| Status Code | Meaning |
|---|---|
| 200 | Success |
| 400 | Bad request (invalid parameters, operation failed) |
| 404 | Index not found |
| 409 | Conflict (index already exists) |
| 503 | Service unavailable (engine module not loaded) |
Quick Reference
| Method | Endpoint | Description |
|---|---|---|
| GET | / | Health check |
| GET | /indexes | List all indexes |
| POST | /indexes | Create a new index |
| DELETE | /indexes/{name} | Delete or close an index |
| GET | /indexes/{name}/status | Get index status |
| POST | /indexes/load | Load an existing index |
| POST | /init | Initialize an ingest session |
| POST | /ingest | Ingest a single vector |
| POST | /ingest/batch | Batch ingest (binary) |
| POST | /finalize | Finalize an ingest session |
| POST | /delete | Delete items from an index |
| POST | /rebuild | Rebuild an index compact |
| POST | /search.bin | Search (binary) |
| POST | /optimize | Optimize the HNSW graph |