Agents
Connectors
Other software — n8n, Claude Desktop, Grok, custom MCP clients — can operate this vault over REST or the Model Context Protocol. Mint a key in Ops → Connectors. Send it as Authorization: Bearer or X-Api-Key.
REST
/api/v1
JSON over HTTPS. OpenAPI at /api/v1/openapi.json.
MCP
/api/mcp
JSON-RPC 2.0, protocol 2025-03-26, Streamable HTTP + SSE.
REST map
- GET /api/v1/healthLiveness
- GET /api/v1/catalogLadders
- GET /api/v1/ladders/{slug}One ladder + shots
- GET /api/v1/analyticsRevenue / conversion
- GET / PUT /api/v1/dialsPsychology dials
- GET / POST /api/v1/modelsMuses (POST auto-builds 2257 pack)
- GET /api/v1/legalLegal hub
- POST /api/v1/legal/regenerateRebuild templates
- POST /api/v1/transporter{ ladderId } — Grok rewrite
- POST /api/v1/shotsAppend a shot
- GET /api/v1/openapi.jsonOpenAPI 3.1
MCP tools
initialize, tools/list, tools/call, resources/list, resources/read, prompts/list. Tools mirror the REST operations (list_ladders, set_dials, upsert_model, write_ladder_copy…).
n8n
HTTP Request node
Method: GET
URL: {{vault}}/api/v1/catalog
Header: Authorization = Bearer {{SHE_KEY}}
MCP Client node
SSE / HTTP URL: {{vault}}/api/mcp
Header: Authorization = Bearer {{SHE_KEY}}Claude / MCP config
{
"mcpServers": {
"she-undresses": {
"url": "https://YOUR-VAULT/api/mcp",
"headers": { "Authorization": "Bearer she_…" }
}
}
}