PricingSign In
    Kubeez Logo

    REST API overview

    Kubeez exposes a public HTTP API for the same generation features you use in the app: media (images and videos), music, ads, and account reads. It is separate from the MCP integration (OAuth + tools for AI clients). Use the REST API when you have a server or script and want API key authentication.

    #When to use the REST API

    • Backend services, CI jobs, or mobile apps that should not run an MCP client.
    • API keys from API Keys Settings (sk_live_…).
    • Standard HTTPS + JSON (and multipart for file upload).

    #When to use MCP instead

    • ChatGPT, Cursor, Claude Desktop, or other MCP hosts.
    • Browser-based OAuth and scoped capabilities instead of long-lived API keys.
    • See MCP overview and Quick start.

    #Base URL

    https://api.kubeez.com/v1

    #Documentation in this section

    PageWhat it covers
    REST APIAuthentication, upload, rate limits, Swagger link.
    REST API model requirementsPer-model prompt limits, inputs, duration, flags (generated from server defaults).

    Interactive reference: Swagger UI.

    #Typical flow (media)

    1. GET /v1/models — pick a model_id, check capabilities and usage_notes.
    2. If you have local files, POST /v1/upload/media — use returned URLs as source_media_urls.
    3. POST /v1/generate/media — start the job; poll GET /v1/generate/media/{id} until completed.

    Next: REST API for headers, scopes, and limits.