Safe House API reference
The Safe House API covers six functional areas: configuration, quarantine management, observability and metrics, pattern and intelligence management, canary credentials, and compliance exports. All endpoints require a Bearer token or API key unless otherwise noted. Base URL:https://api.mnemom.ai
Configuration
Safe House behavior is configured through the protection card — a per-agent manifest of mode, score thresholds, screened surfaces, and trusted sources, composed across platform → org → agent scopes. Control it globally for the org (via the org protection template), per-agent, or in bulk.
The granular sub-resource paths (
/mode, /thresholds, /screen_surfaces, /trusted_sources) accept PUT or PATCH and exist at every scope (/protection/agent/:id, /protection/org/:id, /protection/team/:id, /protection/platform/:id).
Retrieve the org-scope manifest:
PUT /v1/protection/agent/:agent_id with a full protection card.
Bulk-apply a config to many agents:
Quarantine management
Quarantined turns are held pending human review. Reviewers can release (with or without a false-positive flag) or confirm as a genuine threat.
List open quarantine items:
Query & observability
Query the full evaluation history, aggregate metrics, and access a live SSE stream for real-time monitoring.
Query evaluations with filters:
safe_house.evaluation.*, safe_house.canary.*, safe_house.session.*, and safe_house.campaign.* events as they occur. Reconnect with Last-Event-ID to replay missed events (replays up to 10 minutes back).
Patterns & intelligence
Manage the threat pattern library and retrieve adaptive threshold recommendations.
List active patterns for a threat type:
candidate status. The arena evaluation pipeline tests them against labeled benign and malicious message sets. Patterns that exceed precision/recall thresholds are promoted to active.
Canary credentials
Canary credentials are honeypot API keys, tokens, or other secrets deliberately planted in the agent’s context. If an attacker extracts and uses them, Safe House detects the use and fires asafe_house.canary.triggered event.
Create a canary:
credential value is returned only at creation time. Safe House monitors for its appearance in outbound requests or inbound message content.
Check canary status:
Special endpoints
Cross-Agent campaign detection
List detected attack campaigns — groups of related attacks targeting multiple agents from the same infrastructure.EU AI Act compliance export
Export Safe House evaluation data in EU AI Act Article 50 compliance format.Accept: text/csv for spreadsheet-compatible export.
Error responses
All Safe House endpoints return standard Mnemom error objects:See also
- Safe House Threat Model — What each threat type means and how detection works
- Safe House Webhooks — React to Safe House events in real-time
- Safe House Monitoring — Security Observatory and alert management
- Policy Overview — Policy enforcement runs alongside Safe House