Vectr API Reference

The same job in TypeScript

const API = "https://api.vectr.bot";
const headers = { "X-API-Key": process.env.VECTR_API_KEY!, "Content-Type": "application/json" };

const { jobId } = await fetch(`${API}/agent/job`, {
  method: "POST", headers, body: JSON.stringify({ prompt: "what tokens are trending?" }),
}).then((r) => r.json());

let job;
do {
  await new Promise((r) => setTimeout(r, 1500));
  job = await fetch(`${API}/agent/job/${jobId}`, { headers }).then((r) => r.json());
} while (job.status === "pending" || job.status === "processing");

console.log(job.response, job.richData); // richData: the unsigned transaction, if one was built

And in Python

import os, time, requests

API = "https://api.vectr.bot"
headers = {"X-API-Key": os.environ["VECTR_API_KEY"]}

job = requests.post(f"{API}/agent/job", headers=headers, json={"prompt": "what tokens are trending?"}).json()
while True:
    time.sleep(1.5)
    job = requests.get(f"{API}/agent/job/{job['jobId']}", headers=headers).json()
    if job["status"] not in ("pending", "processing"):
        break

print(job["response"], job["richData"])  # richData: the unsigned transaction, if one was built

Keep going

• CLIThe same API from a shell — vectr agent, price, tokensRead docs
• MCP serverThe same tools inside Claude, Cursor or any MCP clientRead docs
• Fee structureWhat each swap charges and who it settles toRead docs
• SourceBackend, contracts, SDK and toolingVectr git

Read-only endpoints are safe to call from any server or script. Agent jobs only prepare transactions — but a read-write API key can broadcast through /wallet/sign-and-submit, so scope keys down to read-only whenever a key only needs data.