API

eave developer docs

Base URL: https://eave-api.wittygrass-f001bb5e.canadacentral.azurecontainerapps.io

Authentication

Machine API calls use an API key as a Bearer token (or X-API-Key). Portal sessions use HttpOnly cookies and are never valid as API credentials.

Authorization: Bearer eave_sk_sand_…

POST /api/v1/classify

Classify a transcript snippet. Primary sandbox endpoint.

curl -X POST "$API/api/v1/classify" \
  -H "Authorization: Bearer $EAVE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"Please buy Google Play cards and read me the codes.","use_ai":true,"depth":"fast"}'
{
  "ok": true,
  "environment": "sandbox",
  "session_id": "…",
  "use_ai": true,
  "depth": "fast",
  "is_scam": true,
  "confidence": 0.91,
  "reason": "…",
  "tactics": ["gift_card"],
  "call_state": { },
  "model": "…",
  "alerted": false,
  "timings": { "triage": 210, "fast_model": 1840, "total": 2090 }
}

use_ai (default true):

depth (default "fast", ignored when use_ai is false):

Every AI response carries a timings object of per-stage milliseconds (triage, fast_model, full_model, total) so you can see where the wall-clock went.

Sandbox vs live

Advanced endpoints

Errors

Open developer portal Platform overview