aisplice

API reference

Model list

GET/v1/models

Lists every model this key is allowed to call — clients like Cursor use it to validate the connection. Keys with a model whitelist see only their whitelist.

#Request example

curl https://www.aisplice.store/v1/models \
  -H "Authorization: Bearer sk-YOUR_KEY"

#Response

response.json
{
  "object": "list",
  "data": [
    {"id": "gpt-5.6-luna", "object": "model", "owned_by": "openai"},
    {"id": "gpt-5.6-terra", "object": "model", "owned_by": "openai"},
    {"id": "gpt-5.6-sol", "object": "model", "owned_by": "openai"},
    {"id": "claude-opus-5-5", "object": "model", "owned_by": "anthropic"},
    {"id": "qwen3.7-max", "object": "model", "owned_by": "alibaba"}
  ]
}

Prices are not in this payload — the models page carries live per-model pricing, tiers and capability tags.

#Reading the model catalogue

Which catalogue fields tell you what a model supports, and which belong in your UI.

  • supported_endpoint_types
    Expose when
    Read this first when deciding which endpoint shape the model belongs to.
    Recommended default
    Treat it as the routing signal, not a UI control.
    Why it matters
    It tells you whether the model should be called through /images, /images/tasks, /videos, /audio, or chat-style endpoints.
  • pricing_tiers.size / quality / resolution / duration
    Expose when
    Read when deciding which knobs deserve to appear in the product UI.
    Recommended default
    If a tier map is empty, keep that control hidden.
    Why it matters
    These maps are the clearest proof that a model actually supports that pricing dimension.
  • pricing_tiers.reference
    Expose when
    Read when you need to know whether image or video reference media is allowed or required.
    Recommended default
    Hide reference upload controls unless this object says they exist.
    Why it matters
    It determines whether the workflow is prompt-only or reference-driven, and whether public URLs are required.
  • quota_type
    Expose when
    Read when explaining price semantics to users or operators.
    Recommended default
    Show as read-only metadata on model detail pages.
    Why it matters
    It distinguishes token billing from per-request billing and changes how users reason about cost.
  • tags / capability
    Expose when
    Use as supporting hints when endpoint types are too generic.
    Recommended default
    Do not rely on them as the only source of truth.
    Why it matters
    They help classify chat vs image vs video vs audio, but they are weaker than explicit endpoint or tier fields.

Still stuck?

Send us the request ID or the error message and we will look into it.

PreviousBalanceNextGoogle Play verification