Internal API
The REST endpoints exist. They are not a supported interface.
LensHub has a REST API at /api/*. The web interface uses it, and it accepts
the same API keys agents use.
It is not a supported interface. It is documented here only so that the boundary is stated rather than discovered.
What that means
- Endpoints, request shapes and responses change without notice
- No versioning, no deprecation period, no changelog entry
- Something that works today may not work after an upgrade
Reachable is not the same as supported. If you script against it, an upgrade will eventually break you, and that is expected behaviour rather than a bug.
Use MCP instead
The MCP tools are the supported way to read and write content programmatically. They are versioned with the product, published to your client on connection, and are what the documentation covers.
The two exceptions
Two endpoints are supported, because they are genuine integration points rather than internals:
| Endpoint | For | Documented in |
|---|---|---|
POST /api/ingest/{sourceID}/documents | Pushing documents from a system with no connector | Pushing your own documents |
GET /api/agent-instructions | Fetching starter agent instructions. No authentication | Writing agent instructions |
Those two are stable and safe to build on.
If you need to automate something else
Provisioning users, creating connectors, rotating keys and triggering syncs are all reasonable things to want to script, and MCP does not cover them.
Tell us what you need. A small, supported management interface is something we would rather build around real requirements than guess at.