VIvieneu
Public API v1

List engines, what each can do, and what each costs

Changed on

The engine registry as it is configured right now: which engines are live, which one you get when you omit engine, and the BILLING MULTIPLIER applied to each. Until this endpoint existed the multipliers lived only in prose, so a caller sizing a budget had to trust a table that could go stale the moment pricing changed. features tells you what each engine may be asked to do — note that stream appears on v4 only, which is why every stream is charged at the v4 rate regardless of what you send. A second factor sits above all of them: globalMultiplier, a platform-wide lever. The charge for a request is characters × engine multiplier × globalMultiplier, so sizing a budget from the per-engine number alone understates it whenever the global lever is not 1. No authentication required.

get/api/v1/engines

Request

  • Base URL
    https://api.vieneu.io
  • Auth
    • API key in header X-API-Key
    • or HTTP bearer
    • or none

Response

One entry per enabled engine, in display order.

globalMultipliernumber

Platform-wide multiplier applied on top of the engine multiplier — a traffic-control lever, normally 1. Multiply it in when converting a token allotment to characters, or the answer is short by exactly this factor.

Example response

{
  "globalMultiplier": 1,
  "engines": [
    {
      "key": "v4",
      "label": "V4 — Nhân bản (48kHz)",
      "sampleRate": 48000,
      "billingMultiplier": 3.4,
      "features": [
        "generate",
        "clone",
        "dialogue",
        "stream",
        "dub",
        "srt"
      ]
    }
  ]
}

Changes

  • 98838c7c0e72Revision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

  • 01d3ff3ac74fRevision changes
    • info

      added the optional property to the response with the status