Skip to content
Docs menu

Venom Cloud

What Venom Cloud is, how its console is laid out, which role opens which page, and where the console and API guides start.

View .md

Venom Cloud is a hosted control plane in front of the models your organisation uses. It gives every member and every app one OpenAI-compatible endpoint (https://cloud.usevenom.dev/v1) with its own vck_… key, and routes each request to one of three kinds of capacity:

  • your own daemons: the venom orchestrator running on your machines in mesh mode. They dial out to the cloud and keep their provider keys local;
  • your provider keys: OpenAI, Anthropic, Mistral, MiniMax and the other providers the cloud supports, stored sealed in the cloud's vault;
  • public nodes: trusted daemons other people run, when your routing allows them.

On top of routing it keeps per-key and per-key-group usage, budgets, logs, sessions, guardrails and an audit trail. The venom CLI, venom serve and any OpenAI SDK talk to it the same way; a new account takes four steps (see Venom Cloud quickstart).

This section has two halves:

  • Console guides (console-* pages): what each page of the web console at https://cloud.usevenom.dev shows and does, who may use it, and what its errors mean.
  • API guides (api-* pages): the cloud's HTTP surface for scripts and apps: /v1/*, the admin API under /api/admin/v1/* and the mesh endpoints daemons use. The generated reference of every /v1 route lives at /docs/api/cloud.

Organisations, roles and permissions

Everything in the console belongs to an organisation. A person can belong to several and switches between them from the organisation menu in the top bar; a new one is made on /orgs/new. Each membership has one role, and each role is a fixed set of permissions:

Role Permissions
owner every permission
admin every permission except billing:manage and sso:manage
developer the read set, plus keys:write, daemons:enroll, daemons:manage, routing:write, content:read, audit:read
billing org:read, members:read, usage:read, billing:read, billing:manage
viewer the read set: org:read, members:read, keys:read, providers:read, daemons:read, routing:read, logs:read, usage:read

The sidebar shows a page only when your role may open it, and the API behind it checks the same permission, so a link you don't see is a page you can't use. Changing things on a page often needs more than reading it (for example, anyone with routing:read reads /gears, but creating a gear needs org:manage); each console guide lists both. The cloud's operator (the people who run the deployment) sees every organisation and a few pages no organisation has, such as /settings/teams.

The console map

The sidebar groups pages by what you do there. The permission is what opening the page needs.

Sidebar section Page Path Needs
(top) Overview /dashboard any member
Live request feed /live logs:read
Get started /get-started keys:read
Usage & cost Usage /usage usage:read
Cost per task /usage/tasks usage:read
Projects /usage/projects usage:read
Budgets /budgets usage:read
Pricing /prices providers:read
Model lifecycle /lifecycle providers:read
Savings plan /usage/savings usage:read
Key group savings /usage/team-savings usage:read
Chargeback /usage/chargeback usage:read
Reconcile invoices /prices/reconcile usage:read
Routing & models Routing /routing routing:read
Gears /gears routing:read
Providers /providers providers:read
Provider status /providers/status usage:read
Model quality /quality routing:read
Experiments /experiments routing:read
Shadow tests /shadow routing:read
Failover drill /routing/drill routing:read
Local autopilot /autopilot routing:read
Compute Daemons /daemons daemons:read
Nodes /nodes routing:read
Autoscaling /autoscaling daemons:read
Jobs /jobs logs:read
Activity /activity daemons:read
Quality & debugging Requests /requests logs:read
Sessions /sessions logs:read
Fleet /fleet logs:read
Failures /failures logs:read
Scorecard /scorecard usage:read
Evals /evals routing:read
Safety & policy Guardrails /guardrails audit:read
My guardrails /me/guardrails org:read
Red team /redteam audit:read
Filters /filters audit:read
Permissions /permissions routing:read
Alerts /alerts audit:read
Team Library /library routing:read
Ask /ask routing:read
Memory /memory routing:read
Onboarding /onboarding-paths routing:read
Marketplace /marketplace routing:read
MCP servers /mcp routing:read
Integrations /integrations org:read
Issue intake /integrations/intake logs:read
Business Customers /customers billing:read
Invoices /customers/invoices billing:read
Pricing simulator /customers/simulator billing:read
SLAs /customers/sla billing:read
Clients (MSP) /msp org:read
Starter packs /packs routing:read
Status page /settings/status-page org:read
Admin Members /settings/members members:read
Single sign-on /settings/sso sso:read
API keys /settings/keys keys:read
Join tokens /join-tokens daemons:read
Audit /audit audit:read
Backup & restore /settings/backup org:manage
Settings /settings org:read

Not in the sidebar: the bell in the top bar opens /notifications (spend alerts, usage:read); a blocked request links to its guardrail code's page /g/{code} (any member); /settings has its own sub-navigation for the other settings pages.

Press ⌘K (Ctrl+K on Windows and Linux) anywhere in the console to jump to a page or start a common task, such as creating an API key (/settings/keys?new=1), adding a provider key (/providers/new), connecting a daemon (/daemons/new) or inviting a member (/settings/members?invite=1). The menu lists only what your role can do.

Old console URLs keep working: /keys, for example, redirects to /settings/keys with its query string kept.

For app builders

Venom Cloud is also a back end for apps built on venom. A typical app:

  1. creates an organisation and a vck_… key per environment (or per end customer, with Customers);
  2. sends OpenAI-shaped requests to https://cloud.usevenom.dev/v1 with that key, naming a gear or model;
  3. reads usage, logs and spend back through the admin API, and lets the console hold budgets, guardrails and routing so they change without a redeploy.

The console guides tell you what each setting does; the API guides tell you how to drive the same settings from code.

Troubleshooting

Symptom Cause and fix
A page from this section is missing from your sidebar Your role lacks the permission in the console map. Ask an owner to change your role on /settings/members.
A page says you have no access Same cause: you opened it by URL. The page never calls the API for a role that can't read it.
The operator's sidebar lacks Members, Billing or other organisation pages Those pages belong to one organisation: pick one in the organisation filter first.

In this section

  • The Venom workspace, search and shortcuts: Move between Notes, Tasks, Flags, Experiments and Admin with the app rail, find anything with one ⌘K search, and learn the keyboard shortcuts that work in every app.
  • Quick search (⌘K) across every app: How ⌘K finds notes, issues, people, deals, flags, support tickets, chat and more in one search, what each app matches, how results are ranked, and the streamed search API behind it.
  • References and links between items: Point at any item in the workspace (issues, notes, people, deals, incidents, tickets, forms, flags, chats, computers, Studio decks and pages and more) with one reference, open it from a pasted link, and link items across products.
  • Home, the shared inbox and onboarding: Use Home to pick up recent notes and issues, see what is assigned to you, open your apps, and get started; read the bell's shared inbox; and know what the welcome step, first-visit cards and tour do.
  • Sign in to the console and the CLI: Sign in to the Venom Cloud console with email, GitHub, single sign-on or the operator token, create your first organisation, and approve a venom cloud login from the terminal.
  • Console home, Get started and onboarding paths: Read the console's Overview, finish the first-run checklist on Get started, build onboarding paths for new members, look up a guardrail code and ask your organisation's knowledge.
  • Drafts, everything waiting for your approval: Review every message Venom drafted for you in one list under Home. It covers Outreach drafts, messages your bots hold, People's morning queue, Support drafts and intro asks, with approve, edit, hold and skip, and a tool for agents.
  • Organisations, members and roles: Create and switch organisations, invite members, change their roles, understand what each role may do, and set a key group's permission profile for the venom CLI.
  • Teams, subteams and roles: How Venom Cloud models an org's teams, subteams, members and roles once for every product, what an org role allows in each product, and how today's Tasks teams and Notes team vaults fit in.
  • Single sign-on and SCIM: Connect your organisation to Okta, Microsoft Entra ID, Google Workspace or any OIDC or SAML 2.0 identity provider, map groups to roles, require SSO and provision members with SCIM.
  • API keys and key rotation: Create vck_ API keys for the venom CLI, scripts and OpenAI SDKs, scope them by model, budget, rate and expiry, rotate, pause and revoke them, and set the organisation's key rotation schedule.
  • Languages: Use Venom Cloud in Bahasa Indonesia, Simplified or Traditional Chinese, Cantonese, Japanese or Korean, and how translations are added without making pages heavier.
  • Providers and provider keys: Connect your own OpenAI, Anthropic, Mistral, MiniMax and other provider keys to Venom Cloud, choose the models each key serves, rotate keys and watch how each provider serves you.
  • Organisation gears: Define the gears every venom CLI user in your organisation sees, pick a model and route for each role, set the default gear and lock members to your gears.
  • Routing, failover drills, local autopilot and shadow tests: Decide which model answers and where it runs, rehearse an outage without sending traffic, move paid work to your own models, and try a candidate model on real requests before you switch.
  • Pricing and invoice reconciliation: See and set the price Venom Cloud books for each model, pick where prices come from, check providers for new models and prices, and compare a provider's bill with what Venom booked.
  • Budgets and spend guards: Set daily, monthly or lifetime spend limits per member, API key, key group, gear or project that warn first, then block requests or switch them to a cheaper model.
  • AI spend: See every daily AI limit in your organisation on one page, with a bar for what each product spent today, and change any of them in place if you are an owner or admin.
  • Usage, savings and chargeback: Read your organisation's spend and volume, set the monthly spend cap, see cost per task and per project, find savings, and produce chargeback statements per key group, project, gear, key or member.
  • Requests and request traces: Search every request your organisation sent through Venom Cloud, open one request's trace, read its stored prompt and response, and set how long content is kept.
  • Log query language: Search, filter, group and chart your organisation's request log with one line, in the console's Requests page, alerts, the live feed and the admin API.
  • Sessions, live feed and activity: Watch requests as they finish, see who is online, and open your team's agent sessions in the console, whether remote, shared, captured from the request log, handed off or shared live.
  • Claude Code sessions in Venom: Install the Venom plugin for Claude Code so each finished session shows up in Session history and feeds the Inbox of Venom Notes, redacted on your machine and sent only to your own cloud.
  • Failures and jobs: Find out what made agent sessions and requests fail, grouped by cause with example sessions, and inspect the relayed jobs the cloud dispatched to daemons.
  • Alerts and notifications: Run saved log searches every 5 minutes with a signed webhook, and read the notification inbox for budget thresholds, spend forecasts, spend anomalies and key rotation.
  • Skills in the Venom plugin for Claude Code: The skills that come with the Venom plugin for Claude Code, in every project once it is installed - plain writing, two management audits, doc sync, Linear plans, RCAs, cloud migrations, security audits, technical due diligence and Venom Studio artifacts.
  • Audit log and audit export: Search your organisation's audit log, see what each change did, undo a settings change, download the log, and copy it to your own S3-compatible bucket on a schedule.
  • Guardrails and filters in the console: Set the org's, key groups' and your own guardrails, test them on pasted text, and manage the prompt and response filters and the secret scanner from the Venom Cloud console.
  • Team library and starter packs: Publish prompts and skills your members get in venom, version and roll them back, and install a vertical starter pack from the Venom Cloud console.
  • Org skills registry: Keep your organisation's reusable agent skills in one place in Venom Cloud, add them from a GitHub repository, by upload or by writing them, turn each on or off, change several at once, approve updates from their source, and roll back to any version.
  • Marketplace and MCP servers: Submit, review and pin plugins, skills and MCP server packages in your org's marketplace, and approve the MCP servers each key group's venom users get.
  • Your organisation's MCP servers: Add your own MCP servers by URL for everyone in the organisation, test the connection, choose whether the cloud or only your venom clients reach them, and keep credentials sealed.
  • Org memory: Keep the short facts your team agrees on in Venom Cloud, review what members propose, and see the exact block venom loads into a session for a repository and key group.
  • Evals and experiments: Run the eval suite or your own golden tasks against your gears on a runner you control, and A/B test two gears or two prompt versions on live sessions from the Venom Cloud console.
  • Model quality, scorecard and red team: Schedule quality checks on the models your gears use, catch drift and swap degraded models, read the agent scorecard per gear or key group, and run the red-team suite from the console.
  • Customers, invoices and the customer portal: Resell model access to your own customers with their own keys, prices, limits, budgets, invoices, SLAs and a branded usage page.
  • Venom Tasks planning: Plan work in Venom Tasks with projects, milestones and updates, a drag-to-reschedule timeline, team cycles with a burn-up chart, saved views, and team and workspace settings.
  • Import issues into Venom Tasks: Move a whole Linear workspace into Venom Tasks from one API key, in the background, and sync it again later; or bring issues from Linear, Jira, GitHub, Asana, Trello or Lark into one team with a mapping and a dry run.
  • MSP mode and the partner portal: Manage many client organisations from one Venom Cloud org, with each client's consent, a ceiling role, scopes and an end date.
  • Export from Venom Tasks: Take your data out of Venom Tasks as CSV for any list, project or initiative, or as a ZIP of CSV and JSON for the whole workspace, with the exact columns and the JSON schema, who may export what, and how an agent does it.
  • Link GitHub pull requests to Venom Tasks issues: Connect a GitHub webhook so pull requests and commits that name an issue key show on the issue, move issues through draft, open, review, ready to merge and merged by each team's rules and target-branch rules, comment back on the pull request, and start an issue when you copy its branch name.
  • Recurring issues in Venom Tasks: Make an issue on a schedule in Venom Tasks, daily, weekly on chosen days, monthly or every few weeks, in your time zone, with pause, resume, an end date and an option to skip while the last one is open.
  • Subteams in Venom Tasks: Nest teams under a parent team, see a parent's work with its subteams' issues, choose what a subteam takes from its parent, and change a team's settings from the sidebar's team menu.
  • Venom Tasks settings: Settings in Venom Tasks has a left nav with your own Preferences and Notifications, workspace pages for teams, members, labels and import, and one page per team with a danger zone.
  • Integrations - Slack, Linear and Jira: Connect your own Slack app so @venom answers in threads, and your Linear or Jira so labelled issues become pull requests from runners you control.
  • Links and attachments on Tasks issues and projects: Add web links to an issue or a project, and attach files to an issue, including large ones, kept in the files of Notes.
  • SLAs in Venom Tasks: Give a team's issues a deadline by priority and label, in hours, days, business hours or business days, counted from creation or from leaving Triage; see the time left on every list, board and issue, get told when one is at risk or breached, filter by it and chart breaches in Insights.
  • Triage rules in Venom Tasks: Route new issues as they land in a team's Triage, by label, creator, source, text or priority, and set their team, status, assignee, agent, labels, priority, project or cycle; ordered, first match wins, recorded on the issue.
  • Venom Tasks notifications: Quiet hours that hold push and email until morning, notifications that open the comment they are about, muting one comment thread, the email when a workspace export is ready, and agent chats you started from an issue reporting back in your Inbox.
  • Customer requests in Venom Tasks: Link Support conversations, People companies and Funnel deals to issues and projects as customer requests, see who asked and what it is worth, and sort, filter and chart issues by that demand.
  • Daemons, nodes, fleet, autoscaling and model lifecycle: Connect and run your own daemons, trust public nodes, see your org's agents, rent GPUs on demand and keep gears ahead of retiring models.
  • Releases in Venom Tasks: Say what ships together with release pipelines and releases, fill them from GitHub pushes or any CI with a pipeline key, mark them shipped when GitHub reports a deployment, write release notes from a template, and copy each pipeline's changelog as Markdown.
  • Organisation settings: The Settings area of the Venom Cloud console - plan and billing, backup and restore, compliance packs, webhooks, the public status page and public session links.
  • The public site, downloads and docs routes: What the public pages of Venom Cloud serve without a sign-in - the site, stable download links, the cloud status page and the docs in HTML, markdown and llms.txt.
  • Self-hosting Venom Cloud: Run your own Venom Cloud on Vercel and Neon, or locally for development, with every environment variable and make target it reads.
  • Editing in Notes: How Venom Notes stores a note as markdown that opens in Obsidian unchanged, and which syntax each kind of block and formatting becomes.
  • Notes team vaults: Give one of your organisation's teams a shared Notes vault, see who opens it (subteams included), close it when it is empty, and share notes with a team.
  • Venom Tasks: Track issues in Venom Cloud with teams, triage, a list and a board, an issue page, the command menu and keyboard shortcuts, and hand work to agents as delegates.
  • Initiatives in Venom Tasks: Group projects under an initiative, nest initiatives, and read their roll-up, timeline and status updates, with keys for each.
  • Project updates and milestones in Venom Tasks: An update schedule with reminders and nudges for the lead, "update missing" on the list, the page and Pulse, editing and deleting updates, comments and reactions on them, a summary of what changed, an initiative's feed with its projects' updates, and milestones with descriptions and drag-to-reorder.
  • Insights in Venom Tasks: Chart any list, board, project, cycle or saved view by issue count, effort, SLA breaches, cycle time, lead time, triage time, age or time in each status, sliced and segmented by a field, see its cumulative flow, and open the issues behind a bar.
  • Pulse in Venom Tasks: One feed of the status updates of the projects and initiatives you lead, work on or follow, with health changes highlighted, the ones overdue for an update, and a weekly digest in the bell and by email.
  • Dashboards in Venom Tasks: Save an Insights chart with a name, keep it private or share it with the org, and see your saved insights as a grid of live charts on the Dashboards page or inside a Notes page.
  • Venom Flags: Put features behind flags in Venom Cloud, target users and segments, roll out by percentage per environment, review every change before it saves, and revert anything from the history.
  • Status page uptime checks, maintenance and subscribers: Watch your own services from the cloud with http, TCP and heartbeat checks, feed the status page's uptime bars and response-time charts, page on-call when a check keeps failing, schedule maintenance, and let readers follow by RSS, Atom or a signed webhook.
  • Venom Forms: Build forms in Venom Cloud with a Tally-style builder, conditional logic and a live preview. Publish a link, and let agents build, change and publish them too.
  • Forms logic, outlines and instructions: How Venom Forms decides which questions a respondent sees, the markdown outline that creates a form, and the instructions that edit one safely.
  • Share a form and take responses: The public form page, embeds (inline, popup, slider), file uploads, hidden fields from the link, and the local spam defences that need no third-party CAPTCHA.
  • Form responses: Read what came in: a table with a column per question, filters, a detail drawer, a summary with charts and drop-off by question, CSV export, retention, a feed of every form, and submits from your own backend over REST and MCP.
  • Send form responses to Notes, Tasks, Funnel, Support, Calendar, webhooks and Slack: Connect a form to seven destinations, from a Notes database row to a Funnel deal or a booking link. Deliveries run after the response is saved, retry on failure and keep a log.
  • Venom People: Remember everyone you meet in Venom Cloud. Keep who they are, how you met, what you talked about and an AI context card per person, search by what you remember, and share people with your team without sharing your notes.
  • Capture people in ten seconds: Add the people you meet to Venom People from your phone in about ten seconds. Scan a business card or badge, share a contact or screenshot from WhatsApp or Telegram, dictate or type a note, and let the event tag itself.
  • Reach in Venom People: Name a topic, a territory and the kind of person you want, and Reach ranks your own people by fit, seniority and how you can reach them, says why for each, and puts them into a pipeline or a sequence in one go.
  • Venom People for agents (MCP and REST): Let an agent search the people you know, add people, log interactions, read context cards, and list events and companies, through the workspace MCP server or its REST twin.
  • Attachments on a person: Keep images, files and links with someone in Venom People. Links show as cards with the service's mark and a title made from the address; nothing is fetched from the linked site.
  • Keep your network warm in Venom People: Debrief an event in a card stack, get five people a day to reach out to with a drafted message in your tone, set circles and cadences, see why each score is what it is, and ask who you know. Venom drafts; you press send.
  • Notes databases for agents (MCP and REST): Let an agent create a database (table) inside a Notes page with its columns and rows, query it, change its schema and views, import CSV, and delete it cleanly, through the workspace MCP server or its REST twin.
  • The Telegram bot for People: Connect your organisation's own Telegram bot to Venom People. Forward a contact, a business card photo, a vCard or a voice note to it and the person lands in People, tagged with the day's event.
  • Ask for an intro in Venom People: Ask one of your own contacts for an intro. Venom drafts the ask and a note to forward, tracks it to introduced, reminds you to nudge, and links it to a Funnel deal. It sends only when you press Send through Venom, one message per press.
  • Mention People contacts in Notes: Type @ in a note to mention a contact from Venom People, see the notes that mention a person on their page, log a note as a meeting, and how agents read a mention.
  • Notes pages for agents (trash, versions, sharing, comments, inbox): Notes tools beyond reading and writing notes, on the workspace MCP server and its REST twin. Trash, versions, publishing, sharing, links, favourites, comments, the Inbox, sources, files, settings, imports and database templates.
  • Share people and find warm intros in Venom People: Share a person, a selection or a whole circle with a team or the organisation, search who in the org knows someone at a company, see the warm-intro paths ranked by strength, and ask a colleague for an intro. Colleagues see that you know someone, never your notes.
  • Import contacts into Venom People: Bring in people from files you already have, Google Contacts, iCloud and Google vCards, LinkedIn connections, WhatsApp and Telegram exports, HubSpot and Pipedrive, with a review that merges duplicates and history that seeds relationship strength.
  • Link people and companies in Venom People: Link one of your people to another with a kind and a date, record where someone has worked, and accept suggested links, all private to you and shown from both sides.
  • Venom Funnel: A sales pipeline on top of Venom People. Move deals through stages on a board, link the people involved with their context cards, track products, goals and the weighted forecast, and let agents do the same over MCP.
  • Your network as a graph in Venom People: See you, every one of your people and their companies as a graph, with the links between people, why two people are connected, the People list's filters, colour and size by derived fields, a panel for what you select, focus, freeze, clusters, and people like someone.
  • Import from Funnel: Bring an existing Funnel database into Venom. The export format (one CSV per table or one JSON file), how contacts become People, what is matched and what is created, and what a re-import does.
  • Public controversy check in People: Turn on an optional check that flags people in Venom People who also appear on CancelPeople.com, with a neutral summary and things to watch out for when engaging. Off by default; names are matched on your server and never sent to the site.
  • Enrich people and their photos: Optional enrichment for Venom People. "Enrich" on a person, or on many at once, asks the providers your organisation picks (Gravatar, Venom Search, Brave Search, People Data Labs, Apollo) for public facts and a photo, shown as suggestions you apply. Off by default; official APIs only.
  • Classify people in People: Let the org's own model sort everyone in Venom People by sector, persona, seniority and opportunity, judge how relevant each person is to your focus, and search and sort by it, under a daily $ cap.
  • Meetings in People: A one-page brief on each person before a meeting, your next meetings on Today with their people, an after-meeting note that proposes the deal move, field updates and next step, and the Granola sync that files each meeting for you.
  • Venom Chat: Team chat where people and agents are members. Public and private channels, DMs and group messages, threads, reactions, pins, search, live updates, and notifications in the same bell as the rest of Venom.
  • Product feeds in Venom Chat: Post Incidents, Tasks, Flags, Experiments and Forms events to a channel as messages with buttons. Acknowledge a page or approve a flag change from the channel, with your own permissions.
  • The overnight queue in People: Switch a saved Reach view to run every night and find the people it picked on Today each morning, each with the reason and a drafted message to approve, edit or skip. Venom sends nothing unless you set a bot to.
  • Agents in Venom Chat: Add the Venom agent, or a service agent from Venom Tasks, to a channel and mention it; its answer streams into the thread. A channel owner picks its tools, including read access to the other Venom products, which run as you; a write waits for your Confirm.
  • Signals in People: For each of your people, Venom reads your notes, interactions and deals and gives a call (engage, progress, hold or drop), strengths, weaknesses and a bar per indicator. It runs on a schedule with the gear you choose, and records "insufficient data" when too little is written.
  • From a channel message to a merged pull request: Ask a service agent in a Venom Chat channel to build something. The request becomes a Tasks issue handed to the agent, and the thread shows its progress, its pull request with the diff, and the merge.
  • Venom Support: One shared inbox for customer email and form requests in Venom Cloud. Assign, snooze, tag and close conversations, write internal notes with @mentions, use saved replies, draft replies from your notes, and optionally let fully covered drafts send themselves after a review delay.
  • Support email, in and out: Point your own email provider's inbound webhook at Venom Support and connect your own SMTP server or Postmark, SendGrid, Mailgun or Resend key for replies. Venom sends nothing through any account of its own.
  • Support SLA policies and reports: Set first-reply and resolution targets per priority, channel, tag or customer company, count them in business hours, pause them while snoozed, get breach alerts, and read response times, breach rate, volume, agent load and ratings on the Reports page or over MCP and REST.
  • Support chat widget and help center: Put a chat on your own site that opens conversations in the Support inbox, answer them live, and publish a help center from your published Notes pages. Served from your own cloud, with no third-party script, font or analytics.
  • Venom Cloud APIs overview: The four HTTP surfaces of Venom Cloud, the credentials each takes, the error shape, rate limits, request headers and where every route is documented.
  • Inference API: Call models through Venom Cloud with any OpenAI SDK, stream answers, run background responses, list models, resume a dropped stream and route mesh-aware clients to a daemon.
  • Voice API on Venom Cloud: Text to speech, voice lists and transcription on Venom Cloud through your own provider keys, with the orchestrator's OpenAI-shaped audio API.
  • Venom Search: Turn on Venom Search, your org's own metasearch over official APIs and open data, and call it from the API, MCP or the CLI's web_search.
  • Agent and CLI API: The /v1 routes an agent or the venom CLI calls besides inference - org gears, usage, signed policy, guardrails, fleet, onboarding, backups and the session and task reports.
  • Sessions API: Share a session's trace, stream a live session to teammates, hand a session to someone else, and run venom serve sessions on a daemon through Venom Cloud.
  • Knowledge and tools API: Read the org's memory, library and plugin marketplace with a client key, ask questions over them, and run eval, issue-intake and red-team jobs on machines you control.
  • Venom for agents (one MCP server for notes, tasks and flags): Connect Claude Code, Cursor, ChatGPT or any MCP client to Venom Notes, Tasks, Flags, Forms, Incidents and Experiments through one endpoint, edit notes and issue descriptions with anchored edits, search both apps at once, and run many steps in one round trip.
  • Venom Tasks API: Read and change your org's Venom Tasks issues, teams, workflows, projects, cycles, views and inbox over the console session, and follow changes live.
  • Files and pictures over MCP (Notes and People): How an agent puts a picture or file into Venom Notes and Venom People without base64, with a one-time upload URL or a public link, and how it sees the pictures already there.
  • Venom Tasks for agents (MCP): Connect Claude Code, venom, Qoder or any MCP client to Venom Tasks, delegate issues to agents, link issues and notes, and let AI triage suggest a team, labels, a priority and duplicates.
  • What agents can do in Venom (MCP parity): For every Venom app, the actions an agent can take over MCP, the ones left to a person on purpose, and the tools still coming.
  • Venom Flags SDK and REST API: Evaluate Venom Flags in your own code with the TypeScript, Python or Go SDK or the client-side endpoint, report where flags are used from CI, and read and change flags, segments and environments over the REST API with curl.
  • What agents connect to by default: A logged-in venom connects every Venom product's MCP server (Notes, Tasks, People, Funnel and the rest) with deferred tools; how to narrow or turn them off, and the credential sessions Venom Cloud starts get.
  • Venom Experiments: A/B tests on Venom Flags flags with sound statistics (CUPED, always-valid sequential results, sample ratio checks, guardrails), run by people or agents, with a decision note left in Notes.
  • Sending events to Venom Experiments: Track product events from your own app with the Flags SDK's track(), what the ingest endpoint accepts, its limits and retention, and how exposures are recorded.
  • How Notes learns: What Venom Notes adds to your vault on its own, where it gets it from, how you review it in the Inbox, and how its spending is capped.
  • Insights and dashboards: Trends, funnels and retention over the events your apps send to Venom Experiments, saved as insights and embedded in Notes pages as live dashboards that people and agents can read.
  • Admin API: orgs, members and keys: Script your Venom Cloud org over /api/admin/v1 — orgs, key groups, members, client keys, join tokens, CLI logins, single sign-on, org settings, signed key group policies and onboarding paths.
  • Admin API: providers, gears and routing: Manage an org's provider keys, gears, routing policy, venom-auto tiers, prices, model lifecycle, gear and prompt experiments, shadow tests, guardrails and prompt filters over /api/admin/v1.
  • Admin API: usage, budgets and spend: Read your org's usage and costs, set spend guards and alerts, forecast the month, find savings, produce chargeback statements and reconcile provider invoices over /api/admin/v1.
  • Admin API: daemons, fleet and reliability: Manage your org's daemons, public nodes, GPU autoscaling, prewarming, GPU grants between key groups, failover drills, model quality checks, SLAs and the public status page over /api/admin/v1.
  • Admin API: logs, audit and alerts: Read the request log, run log queries, export requests and the audit log, set alerts and org webhooks, take backups and compliance packs, and manage shared, live and handed-off sessions over /api/admin/v1.
  • Admin API: knowledge, tools and integrations: Manage an org's library, memory, marketplace, starter packs, evals, red-team runs, Slack, Linear and Jira integrations and the knowledge Ask box over /api/admin/v1.
  • Admin API: customers and MSP: Resell Venom Cloud to your own customers with per-customer keys, limits, prices, budgets, invoices and a branded usage portal, or manage client orgs as a managed service provider, over /api/admin/v1.
  • SCIM API: Provision and deprovision your org's members from Okta, Entra ID or any SCIM 2.0 client through /scim/v2, with group-to-role mapping.
  • Venom Notes API: Read and write the notes in a Venom Notes vault, follow [[wikilinks]] and backlinks, search, fetch the graph, and move a vault in and out as a zip of Obsidian-compatible markdown.
  • Databases in Notes: Notion-style databases in Venom Notes that stay plain markdown, with property types, views, filters, formulas and rollups, and an Obsidian Bases file on export.
  • Log queries over the admin API: Run, page, facet and save request-log queries from scripts through /api/admin/v1/logs; the query language itself is on the console's log query page.
  • Sign-in flows: Get a Venom Cloud client key for a CLI or device without pasting one (the device login), and the browser sign-in routes for GitHub, Clerk and single sign-on.
  • Incoming webhooks: The webhook URLs Venom Cloud receives from Slack, Linear, Jira, Stripe and Clerk, how each is signed and what it answers, so you can connect and debug them.
  • Public and auditor endpoints: The Venom Cloud endpoints that need no Venom key (health, downloads, the docs as markdown and llms.txt) and the auditor API that checks public-mesh daemons.