---
title: Plans and the add-on
description: Venom Agents is included in Team and up; what a team without it sees in the app, the API and the MCP tools, how usage is booked, and what an operator sets.
section: agents
order: 20
audience: [user, operator, builder]
sources: [services/nodejs-cloud/lib/billing/addon-catalog.ts, services/nodejs-cloud/lib/billing/addons.ts, services/nodejs-cloud/lib/agents/index.ts, services/nodejs-cloud/components/agents/parts.tsx]
features: []
---

Venom Agents is the add-on `agents`. Like the other workspace products, it is included in the Team, Business and
Enterprise plans, with no charge per seat or per chat ([Pricing](/pricing)). A Community organisation does not have it,
unless it bought the product before plans included it.

## Who has it {#who}

| Situation | Venom Agents |
|---|---|
| Team, Business or Enterprise | Included. |
| Community | Off. An owner or billing member upgrades under Settings → Billing ([Billing](/docs/cloud/console-settings.md#billing)). |
| Billing off (a self-hosted cloud without `STRIPE_SECRET_KEY`) | Every organisation has it. |
| In preview (billing on, `STRIPE_PRICE_AGENTS_SEAT` unset) | Every organisation has it. |

The add-on covers the chats themselves. A [computer chat](/docs/agents/computer-chats.md) also needs Venom Computers, which the
same plans include.

## Without it {#without}

- **The app**: Agents is not on the rail. Opening `/agents` shows **Add Venom Agents to your plan**, with a button to
  the billing page.
- **The API**: every route under `/api/workspace/agents` answers `403`:

  ```json
  {
    "error": {
      "message": "Venom Agents is included in the Team plan and up. Upgrade at https://cloud.example.com/settings/billing.",
      "type": "permission_error",
      "code": "addon_required",
      "param": null,
      "addon": "agents",
      "upgrade_url": "https://cloud.example.com/settings/billing"
    }
  }
  ```

- **MCP and the REST twins**: each `agents_*` tool, and its twin under `/api/v1/agents`, refuses with the same message,
  so an agent can tell the person what to do.

Nothing is deleted when an organisation loses the add-on. Its chats come back when the add-on does.

## What it costs to run {#usage}

The plan covers the app. The model calls an agent makes are usage like any other request: the cloud calls the daemon with
a key minted for the member who started the chat, so the calls are booked to that member, count against their budgets
and follow their model access ([Your usage, your limits](/docs/agents.md#your-usage-your-limits)).

## For operators {#operators}

`STRIPE_PRICE_AGENTS_SEAT` names a legacy per-seat Stripe price. It is read only to recognise an old subscription item
and to tell "in preview" from "sold"; Checkout never sells it. The operator can also turn the product on by hand for one
organisation on any plan (Settings → Billing, as the operator); the change is audited as `billing.addon_changed`.
