Turn the AI subscriptions you already pay for into an API — answered by Revoye Desk

• A subscription and an API are two separate purchases

  A monthly plan buys you a web interface. It does not buy you programmatic access. The moment your code needs an answer, you are on a metered bill with no relationship to the flat fee you are already paying.

• Unattended work is where metered bills grow fastest

  Overnight summaries, spreadsheet runs, content pipelines, scheduled research. The jobs nobody watches are the ones that run up a per-token bill — and the ones that least need an instant answer.

• Every provider is its own integration

  A different SDK, a different auth scheme, a different response shape, another key in another secret store. Trying a second model to compare quality becomes a day of work before it becomes a comparison.

• Keys leak, and a leaked key spends your money

  A provider key in a repository, a log line, or a client bundle is someone else’s usage on your card. The safest key is the one that was never issued.

All four have the same root: the access you already pay for is stuck inside a chat window. Revoye Desk turns it into something your code can call.

• Throughput you scale with agents

  Need more answers at once? Create more agents in Revoye Desk. Prompts are answered in parallel across them, so capacity grows with the agents you run — not with a budget.

• One integration for six providers

  One base URL, one bearer token, one request shape. Switching from ChatGPT to Claude is a string in a field, not a new SDK, a new auth scheme and a new response parser.

• No key to leak

  Revoye holds no provider credential, so there is no provider credential to steal from Revoye. Your Revoye key can be scoped down to write-only or read-only, rotated, and revoked from the dashboard without touching any provider account.

• Work that survives being offline

  Your queue is durable. Close the laptop mid-run and the job is still there when it wakes up. For anything overnight or unattended, this is the difference between a pipeline and a babysitting job.

• It plugs into what you already wrote

  Point an OpenAI SDK at Revoye by changing base_url. revoye/auto lets your routing policy pick the provider; revoye/chatgpt pins one. Your model picker keeps working, because /v1/models answers in the shape it expects.

• One place to see everything

  Every device, every provider, every agent and its live status, your queue depth, and the history of what ran, on which agent, and how long it took. Not six dashboards on six provider sites.

curl https://api.revoye.com/v1/completions \
  -H "Authorization: Bearer $REVOYE_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "prompt": "Summarise the CAP theorem in three sentences.",
    "provider": "chatgpt",
    "wait": true
  }'

{
  "id": "job_01JAY7Q2K8XYZ",
  "status": "succeeded",
  "response": "The CAP theorem states that…",
  "provider": "chatgpt",
  "agent_id": "agt_01JAY7…",
  "attempts": 1,
  "queue_ms": 240,
  "run_ms": 18432
}

curl https://api.revoye.com/v1/completions \
  -H "Authorization: Bearer $REVOYE_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "Write release notes for the attached changelog.",
    "wait": false,
    "callback_url": "https://your-app.example.com/hooks/revoye"
  }'

{ "id": "job_01JAY7Q2K8XYZ", "status": "queued", "created_at": "2026-08-18T09:14:02Z" }

from openai import OpenAI

client = OpenAI(base_url="https://api.revoye.com/v1", api_key=REVOYE_KEY)

answer = client.chat.completions.create(
    model="revoye/chatgpt",          # or revoye/auto to let the router choose
    messages=[{"role": "user", "content": "Summarise the CAP theorem."}],
)

Read the full API reference →·Quickstart·Errors·OpenAPI specification

Integrating with an AI coding agent? Download the Revoye API integration skill — the whole public API in one Markdown file: authentication, every endpoint, the error table, retries, webhooks and a reusable client. Hand it to the agent and it has everything it needs in a single pass.

• Your AI sign-ins stay on your computer

  Revoye has no ChatGPT password, no Claude session and no Gemini token. With the Self Desk Agent you sign in inside Revoye Desk, on the provider’s own page, and the session is kept securely on your machine; with the optional Browser Agent it stays in your browser. There is no provider credential in our database because nothing in Revoye ever needs one.

• Only your paired computer receives work

  Revoye Desk is paired to your account with a one-time code, and only a device you have paired — and not revoked — can receive your prompts. Revoke it from the dashboard and it is disconnected at once.

• Revoye Desk keeps nothing it does not need

  Revoye Desk never keeps your prompts or answers on the computer. Its activity list records whether each job worked and how long it took — never the text. Diagnostics you choose to send us leave your prompts, answers and sign-ins out too.

• Your Revoye key is scoped, revocable, and shown once

  API keys carry scopes: write-only for a key embedded in a client, read-only for a monitor. We store a hash, never the key, so no endpoint exists that could show it again. An API key can never perform an account action — it cannot create another key, revoke a device, or read your audit log. A leaked key cannot become account access.

• Your accounts, at the pace you set

  Revoye answers with accounts you are legitimately signed in to, at a pace you control: hourly limits per agent, per provider and across everything mean an unattended script cannot hammer one account. You remain responsible for using each account in line with its provider’s terms.

API prompts and responses are stored so your job history works, and they are deleted on a retention schedule you set yourself in Settings. If you need one gone sooner, delete the job.