API Keys & the Public API

Make a vyro_ API key under Profile → API keys and call VyroAI.vip from your own code, or from a plugin on your Minecraft server through a chat command.

What it is for

VyroAI has a public HTTP API. With a key, your own software can ask VyroAI to do things — the headline example being a plugin on your Minecraft server that talks to VyroAI from a chat command.

Making a key

Open Profile → API keys and press New key. Give it a name (something like survival-server so you know which one to revoke later) and the key is shown to you once — copy it there and then, because it is never displayed again. The list only ever shows the first ten characters.

The same page shows the exact endpoint for your account, the header to send and a ready-to-paste example request. Every key starts with vyro_.

If you remember two key pages

There used to be a second page at /settings/api-keys that made vk_live_ keys with a different header. That page is gone — the address now takes you to Profile → API keys. A vk_live_ key you made there still works with the request below, still shows in your list and can still be revoked from it. New keys are vyro_ only.

Using a key

POST /functions/v1/public-api HTTP/1.1
Authorization: Bearer vyro_...
Content-Type: application/json

{ "action": "chat", "prompt": "Explain Bukkit events" }

What you can ask for

Action	What you send	What comes back
`me`	nothing else	who the key belongs to, `balance_tokens` and `balance_credits` — the quickest way to check a key works
`chat`	a `prompt`, or a `messages` list of user and assistant turns; optionally `model`	the reply text

Add model to pick one of the models VyroAI offers; leave it out for the default. Anything else comes back as an error naming those two actions. Calls share the same rate limit as the chat in the app.

"Rate limit exceeded" and "Daily request limit exceeded"

The request above shares one limit with your chat in the app: 150 requests in any 60 minutes for your whole account — every key and your own chatting together. Past that, the answer is Rate limit exceeded. Please try again later., with the time it frees up again.

Daily request limit exceeded. comes from somewhere else: the older address /functions/v1/user-api, which some vk_live_ keys were set up with, sending the key in an X-VyroAI-Key header. That address counts each key on its own — 1.440 requests a day — and starts the count again at midnight UTC. This page does not show that count. If your server hits it, switch it to the request above: a vk_live_ key works there too, and it has no daily cap of its own.

Revoking a key

Press Revoke next to the key in the list. It stops working straight away and stays in the list with its name crossed out. Its Last used column then reads Revoked instead of a date — so if you think a key has leaked, look at when it was last used before you revoke it, because that date is not shown afterwards. Revoking cannot be undone — make a new key instead.

Anything done with your key spends your credits. Nothing is charged until a key is actually used. Treat a key like a password: never commit it, never paste it in a public channel, and revoke it the moment you suspect it has leaked.

Also in Power User

Next in Power User: Secret Vault
Telling it how to work: Skills — Skills are reusable instructions the AI follows on every prompt in a project. How to write one, apply it per project, publish it or import one from GitHub.
Telling it how to work: Chat vs Build Mode — Chat mode talks and plans without writing a file; Build mode writes the code. How to switch, and why Execute plan runs exactly the plan you read.
Picking the model: Choosing an AI Model — Which model runs your chat and your code, and where you can change it.
Picking the model: The Model Benchmark — How the public Model Benchmark ranks AI models on the same plugin and bot tasks with the same grading, and how to read the score, value and speed cards.

6 of 7 in Power User · Last checked 11 September 2026 · Previous: Auto-Fix