Migration guide

​

Why migrate?

• A stable base URL shared by every version (https://api.aurigin.ai)
• A richer prediction payload with global + per-segment insights
• New endpoints for larger uploads and storage management
• Backwards-compatible timelines so you can cut over safely

​

Base URL changes

- const BASE_URL = "https://aurigin.ai/api-ext";
+ const BASE_URL = "https://api.aurigin.ai/v1";

- await fetch(`${BASE_URL}/predict`, …)
+ await fetch(`${BASE_URL}/predict`, …)

​

Response payload differences

​

v0 (chunk arrays)

{
  "predictions": ["fake", "fake", "real"],
  "global_probability": [0.9912, 0.9889, 0.9824],
  "error": [null, null, null],
  "model": "apollo-4-2025-10-20",
  "processing_time": 1.35,
  "audio_duration": 69.91
}

​

v1 (rich objects)

{
  "prediction_id": "pred_abc123def456",
  "global": {
    "confidence": 0.9921,
    "result": "spoofed",
    "reason": null
  },
  "segments": [
    {
      "index": 0,
      "start": 0.0,
      "end": 5.0,
      "confidence": 0.9898,
      "result": "spoofed"
    }
  ],
  "model": "apollo-4-2025-10-20",
  "processing_time": 1.23,
  "audio_duration": 10.0,
  "warnings": []
}

• v0 returns parallel arrays (predictions, global_probability, error).
• v1 wraps results into structured objects: a global verdict and a segments array with timing metadata.
• v1 responses always include a prediction_id you can use for auditing or async lookups.
• The warnings array replaces per-chunk error strings.

​

Request changes

• Upload formats: both versions accept multipart/form-data uploads. v1 also accepts a JSON payload with a presigned_url.
• Device + model metadata: v1 adds optional device and model fields for tagging requests. model currently only accepts apollo-4-2025-10-20 and can be omitted.
• Large files: v1 introduces POST /predict/large-file for 5–100 MB uploads without switching to async workflows.

​

Endpoint mapping

Async uploads via pre-signed URLs are now handled outside of the public v1 spec. Reach out to support if you depend on the old async flow.

​

Migration checklist

1. Switch base URL to https://api.aurigin.ai/v1.
2. Update response parsing:
   • Map predictions[n] -> segments[n].result
   • Map global_probability[n] -> segments[n].confidence
   • Use global.confidence / global.result for overall status.
3. Handle prediction_id for logging or follow-up status checks.
4. Adopt new endpoints if you need medium-sized uploads (/predict/large-file).
5. Retire deprecated fields:
   • error[] is replaced by warnings[].
   • global_probability[] is no longer returned.

​

Rollout tips

• Dual-write strategy: call both v0 and v1 in parallel, compare outputs, then flip traffic once results align.
• Monitor warnings: v1 warnings highlight partial failures that used to surface as error[i] entries.
• SDK regeneration: regenerate clients from the v1 OpenAPI spec to pick up the new response schema automatically.