MemoryLane provides a local HTTP API for managing memories and sessions. Start the server with:
memorylane serve --port 3040GET /healthResponse: { "status": "ok", "service": "memorylane", "version": "0.1.0" }
GET /v1/memorylane/healthGET /v1/memorylane/capabilitiesReturns list of all available endpoints.
POST /v1/memorylane/memories
Content-Type: application/json
{
"text": "User prefers short posts",
"tags": ["writing", "preference"],
"source": "chat",
"importance": 8,
"metadata": {},
"sessionId": "ses_..."
}GET /v1/memorylane/memories?limit=10&tags=writing,preferenceGET /v1/memorylane/memories/:idDELETE /v1/memorylane/memories/:idPOST /v1/memorylane/recall
Content-Type: application/json
{
"query": "How should I write X posts?",
"limit": 5,
"tags": ["writing"],
"sessionId": "ses_...",
"minImportance": 3
}POST /v1/memorylane/search
Content-Type: application/json
{
"query": "keyword",
"limit": 10,
"tags": ["writing"]
}POST /v1/memorylane/sessions
Content-Type: application/json
{
"title": "Product Planning",
"source": "cli",
"metadata": {}
}GET /v1/memorylane/sessionsGET /v1/memorylane/sessions/:idReturns session with all associated memories.
POST /v1/memorylane/exportReturns all memories and sessions as JSON.
POST /v1/memorylane/import
Content-Type: application/json
{
"version": "0.1.0",
"memories": [...],
"sessions": [...]
}In cloud mode, protected endpoints require:
Authorization: Bearer <TALOCODE_API_KEY>
or:
X-Api-Key: <TALOCODE_API_KEY>
Health and capabilities endpoints are always public.