Back to skills
SKILL.md
076 Api C439af5f
ASecurityThis document lists the primary API endpoints and examples. All JSON responses include `status` and primary payload fields for LLM-friendliness. Authentication - All endpoints except `/health` require authentication via one of: - `Authorization: Bearer <AUTOMEM_API_TOKEN>` header (recommended) - `X-API-Key: <AUTOMEM_API_TOKEN>` header - `?api_key=<AUTOMEM_API_TOKEN>` query parameter - Admin endpoints additionally require `X-Admin-Token: <ADMIN_API_TOKEN>` header. Health - GET `/health` - Retu...
- 9 stars
- 0 votes
- 0 copies
- 0 views
- Added October 11, 2026
Works with
Security analysis
100/100npx -y skills add tools-only/X-Skills --skill 076-api_c439af5f --agent claude-codeAre you the author of 076 Api C439af5f?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tools-only-076-api-c439af5f)# AutoMem API Reference
This document lists the primary API endpoints and examples. All JSON responses include `status` and primary payload fields for LLM-friendliness.
Authentication
- All endpoints except `/health` require authentication via one of:
- `Authorization: Bearer <AUTOMEM_API_TOKEN>` header (recommended)
- `X-API-Key: <AUTOMEM_API_TOKEN>` header
- `?api_key=<AUTOMEM_API_TOKEN>` query parameter
- Admin endpoints additionally require `X-Admin-Token: <ADMIN_API_TOKEN>` header.
Health
- GET `/health`
- Returns overall status and service connectivity.
Memory
- POST `/memory`
- Body: `{ "content": "...", "tags": ["tag"], "importance": 0.7, "metadata": {} }`
- Response: `{ "status": "success", "memory_id": "...", ... }`
- GET `/memory/{id}`
- Response: `{ "status": "success", "memory": { ... } }`
- Errors: `404` if memory is missing, `500` on query failure, `503` if graph database is unavailable.
- PATCH `/memory/{id}`
- Body: any subset of fields (`content`, `tags`, `importance`, `type`, `confidence`, `timestamp`, `metadata`)
- Response: `{ "status": "success", "memory_id": "..." }`
- DELETE `/memory/{id}`
- Response: `{ "status": "success", "memory_id": "..." }`
- GET `/memory/by-tag?tags=foo&tags=bar&limit=20`
- Response: `{ "status": "success", "tags": ["foo","bar"], "count": N, "memories": [...] }`
- POST `/associate`
- Body: `{ "memory1_id": "...", "memory2_id": "...", "type": "RELATES_TO", "strength": 0.9 }`
- Response: `{ "status": "success", ... }`
Recall
- GET `/recall`
- **Basic parameters**: `query`, `limit`, `tags`, `exclude_tags`, `tag_mode` (any|all), `tag_match` (prefix|exact), `time_query` (e.g. "last week"), `start`, `end`, `embedding`
- `exclude_tags` - Comma-separated list or multiple params to exclude memories containing ANY of these tags. Supports both exact and prefix matching (independent of `tag_match`). Example: `exclude_tags=conversation_5` or `exclude_tags=temp,draft`
- **Ordering**: `sort` (or `order_by`) supports:
- `score` (default) - hybrid relevance/importance ranking
- `time_desc` / `time_asc` - chronological ordering by `updated_at`/`timestamp` within the filter window (use for "what happened since X")
- `updated_desc` / `updated_asc` - explicit alias (same ordering key as time\_\*)
- **Context hints**: `context`, `language`, `active_path`, `context_tags`, `context_types`, `priority_ids`
- **Graph expansion**:
- `expand_relations` - Follow graph edges from seed results to related memories
- `expand_entities` - Multi-hop reasoning via entity tags (finds "Amanda → Rachel" then "Rachel's job")
- `relation_limit` - Max relations per seed (default: 5)
- `expansion_limit` - Total max expanded memories (default: 25)
- **Expansion filtering** (reduce noise in expanded results):
- `expand_min_importance` - Minimum importance (0-1) for expanded memories. Seed results are never filtered, only expanded ones. Recommended: 0.3-0.5 for broad context, 0.6+ for focused results.
- `expand_min_strength` - Minimum relation strength (0-1) to traverse during graph expansion. Only edges above this threshold are followed. Recommended: 0.3 for exploratory, 0.6+ for high-confidence connections.
- Response: `{ "status": "success", "results": [...], "count": M, "context_priority": {...} }`
- Echoed filters (for debugging): `tags`, `exclude_tags`, `tag_mode`, `tag_match`
- When `expand_entities=true`: includes `entity_expansion: { enabled, expanded_count, entities_found }`
- When `expand_relations=true`: includes `expansion: { enabled, seed_count, expanded_count, relation_limit }`
**Expansion Filtering Example:**
```bash
# Get architecture decisions with related context, but filter out low-importance noise
GET /recall?query=database%20architecture&expand_relations=true&expand_min_importance=0.5&expand_min_strength=0.3
```
**Exclude Tags Example:**
```bash
# Get long-term memories from all conversations EXCEPT the current one
GET /recall?tags=user_1&exclude_tags=conversation_5&limit=3
# Exclude multiple conversations
GET /recall?tags=user_1&exclude_tags=conversation_5,conversation_6&limit=5
# Exclude temporary/draft memories
GET /recall?query=project%20plan&exclude_tags=temp,draft&limit=10
```
- GET `/memories/{id}/related`
- Query: `relationship_types`, `max_depth` (1..3), `limit` (<=200)
- Response: `{ "status": "success", "related_memories": [...] }`
- GET `/startup-recall`
- Returns critical lessons and system rules.
- GET `/analyze`
- Returns analytics (type counts, preferences, temporal insights, entities, confidence distribution).
Enrichment
- GET `/enrichment/status`
- Response: queue size, inflight/pending, stats.
- POST `/enrichment/reprocess`
- Body: `{ "ids": ["..."] }` or query `?ids=a,b,c`
- Response: `{ "status": "queued", "count": N }`
Admin
- POST `/admin/reembed`
- Headers: requires both API and Admin tokens.
- Body: `{ "batch_size": 32, "limit": 100, "force": false }`
- Response: `{ "status": "complete", "processed": N, "failed": K }`
Consolidation
- POST `/consolidate`
- Body: `{ "mode": "full"|"decay"|"creative"|"cluster"|"forget", "dry_run": true }`
- Response: `{ "status": "success", "consolidation": {...} }`
- GET `/consolidate/status`
- Response: `{ "status": "success", "next_runs": {...}, "history": [...] }`
Notes
- Tag matching supports exact and prefix semantics; vector searches are filtered by tag conditions when provided.
- Exclusion filtering (`exclude_tags`) removes any memory containing ANY of the excluded tags, supporting both exact and prefix matching.
- Time filtering accepts ISO timestamps (`start`, `end`) or a natural expression via `time_query`.
- Context hints boost matching preferences (e.g., Python coding style) and guarantee at least one anchor memory when applicable; responses echo what was applied via `context_priority`.
Attribution
Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.