One POST to generate. Billed in rupees.

Authentication

Every request carries a bearer token. Create keys on your API keys page. A key is shown once and stored only as a hash — if you lose it, revoke it and make another.

Authorization: Bearer ghk_live_xxxxxxxxxxxxxxxxxxxx

Models and prices

You are charged a flat price per output, taken from your GHive wallet when the result exists — never for a job that fails, and never for a retry.

A tier is a contract about the OUTCOME, not about which checkpoint runs. Which weights serve it depends on the GPU that picks your job up — a bigger machine may use a better model for the same tier at the same price. We add tiers; we never repoint an existing one at a worse outcome.
This is deliberate: naming a checkpoint would mean your request failing whenever the one machine holding it went offline.

POST /api/v1/generate

curl https://ghive.co.in/api/v1/generate \
  -H "Authorization: Bearer $GHIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "standard",
    "prompt": "a street food stall at night in Bengaluru, warm lights, rain"
  }'

Responds 202 immediately:

{
  "id": "job_9f3c...",
  "status": "queued",
  "model": "standard",
  "price_paise": 200,
  "poll_url": "/api/v1/jobs/job_9f3c..."
}

GET /api/v1/jobs/{id}

curl https://ghive.co.in/api/v1/jobs/job_9f3c... \
  -H "Authorization: Bearer $GHIVE_API_KEY"

{
  "id": "job_9f3c...",
  "status": "done",
  "model": "standard",
  "price_paise": 200,
  "billed_paise": 200,
  "output_url": "/api/v1/jobs/job_9f3c.../output",
  "deleted": false,
  "error": null
}

status is one of queued, assigned, running, done, failed. Poll every couple of seconds. Fetch output_url with the same bearer token to get the PNG.

Downloading and deleting

Add ?download=1 to output_url and the response comes back as a file attachment instead of an inline image. Same bytes, same auth — only the Content-Disposition changes.

DELETE /api/v1/jobs/{id} removes our copy of the image. It is permanent and there is no undo, so fetch it first if you want it.

# Save it, then delete our copy.
curl "https://ghive.co.in/api/v1/jobs/job_9f3c.../output?download=1"   -H "Authorization: Bearer $GHIVE_API_KEY" -o out.png

curl -X DELETE https://ghive.co.in/api/v1/jobs/job_9f3c...   -H "Authorization: Bearer $GHIVE_API_KEY"

{ "id": "job_9f3c...", "deleted": true }

The job record survives — it is the receipt for what you were charged, and deleting an image must not erase your billing history. Polling a deleted job still works and returns "deleted": true with a null output_url, which is how you tell "I deleted this" from "it never produced an image".

We keep only your most recent 9 images. Generating a new one removes the oldest — its output_url stops resolving and polling it returns "deleted": true. Fetch anything you need as soon as the job is done; this is not storage.

End to end, in Python

import os, time, requests

BASE = "https://ghive.co.in"
H = {"Authorization": f"Bearer {os.environ['GHIVE_API_KEY']}"}

job = requests.post(
    f"{BASE}/api/v1/generate",
    headers=H,
    json={"model": "standard", "prompt": "a red vintage scooter on a Goa beach"},
).json()

while True:
    status = requests.get(f"{BASE}{job['poll_url']}", headers=H).json()
    if status["status"] in ("done", "failed"):
        break
    time.sleep(2)

if status["status"] == "done":
    img = requests.get(f"{BASE}{status['output_url']}", headers=H)
    open("out.png", "wb").write(img.content)

Errors

Every failure returns { "error": { "type", "message" } }. Branch on type, show message.