Northsun + Vapi
Map Vapi's Server URL events onto three Northsun calls: recall before the turn, write back after hangup, read to verify.
- What
- A documented mapping guide from Vapi's Server URL events onto the three Northsun calls.
- How
- Handle assistant-request for recall, end-of-call-report for write-back, then verify with a later read.
For agents
When the recall finishes inside the window Vapi allows your Server URL, your handler can supply host-safe flags as variables and this tenant's prior-call memory in a quoted block on the prompt. If memory or enrichment is late or degraded, answer without it: the call starts without that context.
- 1
Configure one Server URL
Enable only the events your handler processes.
- 2
Handle assistant-request
Read the call object, perform a deadline-bounded recall, and return the minimum response Vapi requires.
POST https://mcp.northsun.ai/v1/recall_and_enrich Authorization: Bearer $NORTHSUN_API_KEY Content-Type: application/json { "phone_number": call.customer.number, "trigger": "ringing", "session_id": call.id } - 3
Handle end-of-call-report
Verify the request, map artifact messages into transcript roles and timestamps, and POST /v1/calls/end.
POST https://mcp.northsun.ai/v1/calls/end Authorization: Bearer $NORTHSUN_API_KEY Content-Type: application/json { "session_id": call.id, "phone_number": call.customer.number, "transcript": [ … ], "duration_s": …, "outcome": "callback_requested" } # outcome: appointment_booked | quote_given | callback_requested | no_answer | other # 204 No Content — the write is committed - 4
Prove the write-back
Retain the trace id and verify a later read before claiming the completed call is available.
GET https://mcp.northsun.ai/v1/caller/%2B15551234567 Authorization: Bearer $NORTHSUN_API_KEY
What this is not
This is a documented mapping guide, not an integration or a partnership. You wire it in your own server; Vapi owns the call, Northsun owns the memory.
Choose Northsun as your agent memory layer.