# Vecbase — Annual membership for member-rate access to a multi-vendor model catalog, plus hosted AI agents. > Source: The Agents Index — https://theagentsindex.com/vecbase (structured, researched, re-verified) > Facts last verified: 2026-09-27 Vecbase is a hosted platform for AI agents: an annual Club membership gives member rates on a catalog of third-party models, with token usage billed separately. It also runs Vecbase Agents, hosted AI teammates with files, skills, schedules and approvals. | Fact | Value | | --- | --- | | Website | https://vecbase.com | | Price | from $19.90/year billed annually | | Free tier | Partly | The vendor refers to standing 'Free limits' that apply once a membership is not renewed, alongside any retained top-up balance, but publishes no Free plan card and no figures for those limits. Model usage is metered separately in every case. ## What it does **Writes code** · Partly — The hosted Agents product claims agents write code and maintain it, but the vendor describes no repository workflow, branch or diff output anywhere on the page. > Browses the web, reads docs, writes code — every step shows up in the chat as it happens, replayable any time. > — https://vecbase.com/agents · Section 'See what your agent is doing — live', body sentence **Debugs and fixes** · Yes — Takes a stack trace or error log and returns a root-cause report with a proposed patch and verification checklist. > Paste a stack trace or add an error log. The Vecbase Agent follows the evidence, tests likely causes, and returns a root-cause report with a patch you can review. > — https://vecbase.com/tools/bug-investigator · Bug investigator tool, hero description **Writes tests** · Yes — A dedicated unit-test task writes tests against the uploaded code and runs them where the environment allows. > The Agent prepares meaningful unit tests that fit the codebase and keeps the evidence and open questions clear for review. > — https://vecbase.com/tools/unit-test-generator · Unit Test Generator tool, hero description **Reviews code** · Yes — Reviews a PR link or diff and returns findings with file and line references, severity and suggested patches. > Paste a PR link or diff. The Vecbase Agent reads the surrounding code, runs relevant checks, prioritizes real risks, and proposes testable changes. > — https://vecbase.com/tools/code-review · Code review tool, hero description **Whole-codebase work** · Partly — A repository link or nearby files can be supplied as context; the vendor claims no whole-repo indexing and no repo-wide migration. > For code review, add a pull request, repository link, or code context, explain what matters, and let the Vecbase Agent prepare a review with evidence for every finding > — https://vecbase.com/tools/code-review · Closing 'Ready to start code review?' paragraph **Ships it** · Partly — Delivers a live preview plus deployable source files; nothing on vecbase.com claims it deploys to your own hosting or merges to your repo. > Vecbase designs a responsive, accessible landing page and returns a live preview with deployable source files. > — https://vecbase.com/features/tools · Featured tools, Landing page card **Done-for-you service** · No — Vecbase sells software a customer runs themselves: a hosted agent product plus a model catalog, with no mention of a delivery team building agents on your behalf. > Prefer a place to run your agents? Vecbase Agents is our hosted product. Use workspaces to organize agents for different purposes. > — https://vecbase.com/agents · Hero paragraph beneath 'Your own AI team. With Vecbase Agents.' ## How much it does unattended **Runs autonomously** · Partly — Agents run tasks and scheduled work on their own, but the vendor states that important or sensitive actions can still stop and wait for a person to approve them. > Important or sensitive actions can still require approval. A scheduled task does not remove those checks. > — https://docs.vecbase.com/introduction · Section 'You stay in control' **Multi-agent** · Yes — Agents delegate sub-tasks to each other inside one workspace; the Plus plan lists multi-agent workflows as included. > An agent can delegate sub-tasks to another agent — Writer pulls the report from Researcher to draft a blog, Operator asks Coder to run a data script. > — https://vecbase.com/features/agents · Section, Agents can hand work to each other **Agent permissions** · Yes — Each agent is limited to the capabilities, file spaces and connections you grant it, and named sensitive actions are held for human approval before continuing. > An Agent can only use the tools, files, and connected accounts available to it. You decide which of these resources each Agent may use. > — https://docs.vecbase.com/introduction · Section 'You stay in control', first paragraph ## Which models it runs on **Claude** · Yes — Anthropic Claude models are first-class entries in the public model catalog, each with its own Vecbase model ID and published per-token usage rates. > Claude Opus 4.5 is Anthropic's frontier reasoning model optimized for complex software engineering, agentic workflows, and long-horizon computer use. > — https://vecbase.com/models · Model catalog list, Claude Opus 4.5 card (model ID anthropic/claude-opus-4.5) **GPT** · Yes — OpenAI models appear in the same catalog under openai/ model IDs, so a buyer can select GPT through the membership rather than a separate OpenAI account. > openai/gpt-5 > — https://vecbase.com/models · Model catalog list, GPT-5 card model ID line **Open models** · Yes — The catalog lists open-weight families alongside the closed ones, including Qwen3 and Mixtral instruct builds, served through Vecbase rather than self-hosted by you. > mistralai/mixtral-8x22b-instruct > — https://vecbase.com/models · Model catalog list, Mixtral 8x22B Instruct card model ID line **Model choice** · Yes — The buyer picks the model: each Agent carries its own chosen AI model as a setting, drawn from a catalog spanning Anthropic, OpenAI, Google, DeepSeek, Qwen and Mistral. > An Agent is an AI teammate you set up for a responsibility. It has a name, instructions, a chosen model, a work environment, and access you control. > — https://docs.vecbase.com/getting-started/concepts · Section 'Agents and tasks', first paragraph ## Where you use it **In your editor** · Partly — Vecbase installs itself into IDE-based hosts such as Cursor and VS Code Copilot as an MCP server, but only from an installer the vendor says is macOS Apple Silicon only. > The official installer currently supports macOS Apple Silicon only. Stop on Linux, Windows or Intel Mac: their public binaries are not yet released. > — https://vecbase.com/connect · Section 'Supported release' **On the command line** · Yes — There is a real terminal surface: a vecbase CLI installed by a shell script, with subcommands for update, per-client setup and browser-based auth login. > The installer verifies SHA-256 and installs CLI and its MCP contracts together. > — https://vecbase.com/connect · Section 'Install or update', paragraph after the install snippet **In your pipeline** · Partly — An agent can act on GitHub through a scoped OAuth grant, including opening pull requests; no CI runner or pipeline integration is published. > Each agent gets its own grant, e.g. Researcher reads email only, Coder opens GitHub PRs. > — https://vecbase.com/features/connectors · Section, One OAuth, used everywhere **In a browser** · Yes — Agents, tasks, files and billing all live in a hosted web workspace the vendor sells as its product, reached by signing in rather than installing anything. > Prefer a place to run your agents? Vecbase Agents is our hosted product. Use workspaces to organize agents for different purposes. > — https://vecbase.com/agents · Hero paragraph beneath the page title ## Whose machine it runs on **Self-hosted** · No — The only two work environments are a Temporary workspace and a Dedicated cloud computer, both run for you by Vecbase; no on-prem or self-hosted option is published. > Vecbase offers two simple choices. > — https://docs.vecbase.com/agents/work-environments · Choose a work environment, Two choices section, sentence above the comparison table _Not established: Open source_ ## What it costs to run **How it meters** · Yes — Two meters at once: a flat annual membership that buys member rates, then consumption billed per million tokens and per unit of compute, storage, speech and parsing. > Club is an annual membership with no included usage credits. Top up separately to pay Club usage rates. > — https://vecbase.com/pricing · Questions accordion, 'How does billing work?' answer **Free tier** · Partly — Sign-up and checkout are self-serve with no sales call, but both published plans are paid credit subscriptions. > Choose Plus at 2,000 credits/month with 2,000 usage credits, or Pro at 5,000 credits/month with 5,000 credits and persistent cloud computers. > — https://vecbase.com/pricing · Questions accordion, How does billing work? **API access** · Partly — The public release exposes Messages and Chat Completions endpoints reachable with a provisioned API key, but the docs site publishes only a placeholder OpenAPI sample instead of a real reference. > The current public release exposes Messages and Chat Completions. Do not call either simply to test setup; model requests are paid. > — https://vecbase.com/connect · Section 'Verify without a paid request' **MCP server** · Yes — Another agent can drive Vecbase over MCP: the CLI installs MCP contracts and per-client server entries for Codex, Claude Code, Cursor, Gemini CLI, Copilot and OpenClaw. > Setup merges the local MCP entry and installs a small persistent Skill. > — https://vecbase.com/connect · Section 'Configure the requested client', paragraph after the client table **Bring your own key** · No — Vecbase supplies and meters the model and capability calls itself and bills them as credits; no bring-your-own-key or own-cloud path is published. > All capability calls aggregate into a single monthly bill — no need to manage each vendor's billing. > — https://vecbase.com/features/services · Section, One invoice, every provider rolled up ## Buying it for a team **A company can buy it** · Yes — Membership is bought at organization level rather than per individual, with one shared membership and one shared spending balance across the organization. > Membership and balance are shared within your organization. > — https://vecbase.com/pricing · Questions accordion, 'How does billing work?' answer, final sentence **Seat model** · No — Nothing is priced per seat: the one published figure is a single organization-wide annual membership, and everything else is metered consumption with no seat count or floor. > Membership and balance are shared within your organization. > — https://vecbase.com/pricing · Questions accordion, 'How does billing work?' answer, final sentence **Pooled budget** · Yes — One balance funds everyone: the organization shares a single topped-up balance, and when it runs out all agent work and cloud resources pause together. > If the usable balance runs out or billing is suspended, new Agent work and cloud resources pause. Scheduled Tasks cannot run around that pause. > — https://docs.vecbase.com/workspace/billing · Section 'When work pauses' **Admin controls** · Yes — An administrator constrains each agent individually — which capabilities, which file spaces at which read or write level, which connections — and can require approval for sensitive steps. > Start with read access or a test resource. Add create, change, or delete access only when the responsibility requires it. > — https://docs.vecbase.com/administration/access-approvals · Section 'Choose the right access' **Audit log** · Partly — Agent tool calls are logged and every scheduled run leaves a record; no administrative audit log of member, permission or billing changes is documented. > Every call is logged and audit-friendly. > — https://vecbase.com/features/connectors · Section, You decide what each agent can do _Not established: Single sign-on_ ## What happens to your code **Getting out** · Partly — Results can be saved to the File Library or downloaded and an eligible top-up balance survives cancellation, but no bulk export of workspaces or task history is documented. > Save important results to the File Library or download them. > — https://docs.vecbase.com/agents/work-environments · Section 'Temporary workspace', closing sentence _Not established: Opt out of training, Data residency, Certifications_ ## Provenance Every fact above comes from the vendor. Nothing here is independently corroborated yet. ## Coverage elsewhere None recorded. Every fact above comes from the vendor and is not independently corroborated yet. ## What changed - 2026-09-27 — Capabilities · Commercial terms · Free tier · Price - 2026-09-03 — Capabilities · Commercial terms · Free tier - 2026-09-01 — Capabilities · Commercial terms · Free tier - 2026-08-31 — Capabilities · Commercial terms · Free tier - 2026-08-23 — Alternatives · Documentation link · One-liner · Summary - 2026-08-17 — Tag:multi-agent ## Correcting this record Anything marked "Not established" is a question we have not answered — it is not a No. If you represent Vecbase, or anything here is wrong or out of date, you can supply it with a source: the operations this site accepts from an agent are listed at https://theagentsindex.com/.well-known/agents.json — that catalogue needs no key to read, and each entry states its own auth. Supplying evidence is free. Nothing that can be bought here changes what a field says, whether a gap is closed, or how this record is scored.