VenomDocs

Data export and data structures

Download a complete copy of your organization's data, and how each file in the export is structured.

Export your organization.

Owners and admins can export everything the organization keeps in Venom: projects with their overviews and logs, tasks with their briefs, mentions, artifacts with every revision, skills with their files, Teams, members, settings, the MCP servers you added, and the last 30 days of agent activity. Members' personal skills, personal MCP servers and anything else in their personal scope stay with their author and aren't included.

Open Settings → General and find Export your data.

Select Request export. Venom builds the archive in the background, so you can leave the page. Large organizations take a few minutes.

Select Download when it's ready. Each link works for five minutes; select Download again for a new one. The archive is deleted 7 days after it's ready.

You can also ask support@venomlabs.dev for a complete copy. Venom support produces the same archive, and it appears in Export your data for your owners and admins.

Members and viewers can't export the organization. Through the MCP server, anyone can read what they have access to at any time.

The archive.

The export is one ZIP file. Every file inside is described below. The archive carries the same description as its README.md, and manifest.json lists every file with its SHA-256 digest, so you can check that nothing is missing or changed.

This page describes export format version 1.

What is not included.

Secret values are never exported: shared and personal keys entered for MCP servers, OAuth tokens for MCP connections, and the tokens agents use to reach Venom. Enter credentials again with your new provider. Venom's own security, server and firewall logs and its internal product analytics are not part of an organization's data and are not included.

Members' personal skills, personal MCP servers and anything else in their personal scope, such as personal guidance and preferences, are not included, because only their author can see them in Venom. Each member can read their own personal skills and MCP servers through the MCP server or the web app at any time.

Deleted log entries are included while they are recoverable, 30 days after deletion. Activity records are kept for 30 days, so the archive holds the last 30 days.

Conventions.

  • Every JSON file is UTF-8, indented with two spaces, and has an object at its top level, so later versions can add fields without breaking readers.
  • Times are ISO 8601 in UTC, for example 2026-11-12T09:30:00+00:00.
  • Text written by people and agents (overviews, briefs, log entries, artifacts, skills) is kept exactly as written. It is usually Markdown.
  • Projects, tasks, log entries, artifacts and mentions have 32-character hexadecimal IDs. Members have UUIDs. Team IDs start with team_.
  • Fields such as author, sender_id, recipient_id, owner_id and user_id hold a member's user ID; members.json lists them. Skills, MCP servers and agent guidance record updated_by as the person's sign-in subject, so the export adds updated_by_user_id next to it. Fields ending in _handle were added at export time with that member's current handle.
  • version fields count the changes to a record. Venom uses them to detect conflicting edits.

Layout.

README.md                                this description
manifest.json                            format version, counts and file digests
organization.json                        profile and settings
members.json                             people and their roles
teams.json                               Teams, their members and directory links
projects/KEY/project.json                a project, its overview and project log
projects/KEY/tasks/REF.json              a task, its brief and its log
artifacts/ID/artifact.json               an artifact and its revision history
artifacts/ID/REVISION/FILENAME           the original file of each revision
mentions.json                            every mention in the organization
skills/PLACE/NAME/skill.json             a skill, its status and its revisions
skills/PLACE/NAME/draft/PATH             the skill's current working files
skills/PLACE/NAME/revisions/REV/PATH     the files of each published revision
mcp_servers.json                         MCP servers added to Venom, without keys
activity.json                            agent activity from the last 30 days
files/PATH                               files from the retired Brain file store

KEY is a project key such as web-app and REF a task reference such as web-app-3. PLACE is where a skill lives: organization, team/TEAM_ID or project/KEY. files/ appears only for organizations that stored files before Venom moved to projects and tasks.

Files.

Each section lists one file's top-level fields.

manifest.json.

FieldTypeDescription
formatstringAlways venom-organization-export.
versionintegerExport format version. This document describes version 1.
export_idstringID of the export, as shown in Settings.
generated_atstringWhen the archive was generated.
organizationobjectid, name and slug of the organization.
requested_byobjectuser_id and handle of the person who requested it, and via: web (Settings) or support (a request to Venom support).
activity_windowobjectstart and end of the Activity records included.
countsobjectHow many records of each kind the archive holds.
warningsarraySentences describing anything that could not be included. Empty for a complete export.
filesarrayEvery other file, each with path, bytes and sha256 (hexadecimal SHA-256 of its bytes).

organization.json.

FieldTypeDescription
idstringOrganization ID.
namestringName shown to members.
slugstringURL name.
descriptionstring or nullDescription shown when people pick an organization.
owner_idstringUser ID of the owner.
is_activebooleanFalse while the organization is being deleted.
created_at, updated_atstringWhen it was created and last changed.
agent_guidancearrayOrganization guidance for agents, one item per place it was set: place, read and write guidance text, tool_overrides (tool name to the organization's description of that tool; null restores Venom's), updated_at, updated_by, updated_by_user_id, updated_by_handle.

members.json.

members lists everyone with a membership, including pending invitations and people who were removed.

FieldTypeDescription
user_idstringThe member's user ID.
namestringFull name.
emailstringEmail address.
email_verifiedbooleanWhether the address was verified at sign-in.
handlestring or nullHandle in this organization, used for mentions.
rolestringowner, admin, member or viewer.
statusstringactive, invited or deactivated.
is_activebooleanWhether the membership is active.
joined_atstring or nullWhen the person first joined.
invited_bystring or nullUser ID of the person who invited them.
created_at, updated_atstringWhen the membership was created and last changed.
external_identitiesarrayHandles in other systems: provider (for example slack), provider_tenant, handle, provider_user_id, source, confirmed_at, is_active, created_at.

teams.json.

teams lists every Team, including deactivated ones.

FieldTypeDescription
idstringTeam ID.
namestringTeam name.
handlestring or nullTeam handle, shown as @handle.
descriptionstring or nullDescription.
parent_idstring or nullID of the Team it sits inside.
membership_authoritystringlocal (managed in Venom) or directory (managed by a connected directory).
is_active, deactivated_atboolean, string or nullWhether the Team is active, and when it was deactivated.
created_at, updated_atstringWhen it was created and last changed.
membersarrayuser_id, handle, role (member or maintainer), is_active, created_at, deactivated_at.
directory_linksarrayDirectory groups linked to the Team: provider, provider_tenant, provider_group_id, display_name, source, is_active, created_at.

projects/KEY/project.json.

FieldTypeDescription
idstringProject ID.
keystringProject key, used in task references.
name, descriptionstringName and short description.
statusstringactive or archived.
team_id, teamstring, object or nullThe owning Team, with its id, name and handle.
task_countintegerTask numbers given out so far.
versionintegerChange counter.
created_at, updated_atstringWhen it was created and last changed.
overviewstringThe project overview.
collaboratorsarrayPeople who joined the project individually: user_id, handle.
entriesarrayThe project's own log entries, oldest first. Task status changes are in the task files.
tasksarrayEvery task: id, ref, title, status, and path of its file.
artifactsarrayEvery artifact of the project and its tasks: id, title, and path of its artifact.json.

projects/KEY/tasks/REF.json.

FieldTypeDescription
idstringTask ID.
ref, numberstring, integerTask reference (web-app-3) and its number in the project.
project_id, project_keystringThe project.
titlestringTask title.
statusstringopen, in_progress, blocked, done or cancelled.
brief_entry_idstringID of the brief entry.
versionintegerChange counter.
created_at, updated_atstringWhen it was created and last changed.
briefobjectThe maintained task brief, as a log entry.
entriesarrayThe task's other log entries, oldest first.

Log entries.

Briefs, task updates and project log entries share one structure.

FieldTypeDescription
idstringEntry ID.
owner_type, owner_idstringtask or project, and its ID.
project_idstringThe project.
summary, bodystringThe entry's summary and text, as written. Empty for a deleted entry.
author, author_handlestringWho wrote it.
agentstring or nullThe agent that wrote it through MCP, by the name it registered (for example Claude Code). Null for the web app.
created_at, updated_atstringWhen it was written and last edited.
revisionintegerEdit counter, starting at 1.
briefbooleanTrue for a task's maintained brief.
deletedbooleanTrue for a deleted entry. Its content is in previous_revisions while recoverable.
transitionobject or nullA status change: from and to.
artifactsarrayAttached artifact revisions: artifact_id, revision, title, filename.
mentionsarrayMentions on the entry: mention_id, user_id, handle, kind, note.
in_reply_tostringPresent when the entry answers a mention: that mention's ID.
previous_revisionsarrayEarlier versions still recoverable: revision, summary, body, author, author_handle, agent, created_at, updated_at, deleted, transition, artifacts, mentions, and recoverable_until.

artifacts/ID/artifact.json.

Each revision's original file is stored next to it, at artifacts/ID/REVISION/FILENAME.

FieldTypeDescription
idstringArtifact ID.
title, descriptionstringTitle and description of the latest revision.
filenamestringFile name of the latest revision.
revisionintegerLatest revision number.
byte_sizeintegerSize of the latest revision in UTF-8 bytes.
owner_type, owner_id, owner_refstringtask or project, its ID, and its reference or key.
project_id, project_keystringThe project.
archivedbooleanWhether the artifact is archived.
author, author_handlestringWho saved the latest revision.
created_at, updated_atstringWhen the first and latest revisions were saved.
revisionsarrayEvery revision, oldest first: revision, title, description, filename, byte_size, author, author_handle, created_at, updated_at, and file, the path of its file in this archive.

mentions.json.

mentions lists every mention in the organization, for every recipient, including those withdrawn by their author.

FieldTypeDescription
idstringMention ID.
recipient_id, recipient_handlestringWho was mentioned.
sender_id, sender_handlestringWho mentioned them.
sender_agentstring or nullThe agent that wrote the mention, if any.
kindstringfyi, question or request.
notestring or nullThe note for the recipient.
entry_id, task_id, project_idstringThe entry, task and project it points to.
task_ref, task_title, entry_summarystringThe task and entry as they were when last updated.
statestringunread, seen, answered or declined.
withdrawnbooleanTrue when the author removed the mention or deleted its entry.
reply_entry_idstring or nullThe entry that answered it.
versionintegerChange counter.
created_at, updated_atstringWhen it was created and last changed.

skills/PLACE/NAME/skill.json.

Every organization, Team and project skill is included, whatever its status: drafts, published skills, withdrawn skills and skills that people switched off. Members' personal skills are not included: only their author can see them in Venom.

FieldTypeDescription
name, descriptionstringSkill name and description.
placestringorganization, team or project.
team_id, team_handlestringFor a Team skill: the Team.
project_id, project_keystringFor a project skill: the project.
statusstringdraft, published or withdrawn.
current_revisionstring or nullThe published revision agents receive.
has_unpublished_changesbooleanWhether the draft differs from the published revision.
updated_at, updated_by, updated_by_user_id, updated_by_handlestringWhen the draft or status last changed, and by whom.
sourceobject or nullWhere the skill was imported from, if it was imported.
frontmatterobjectMetadata from the draft's SKILL.md.
disabled_forarrayUser IDs of the people who switched the skill off for their agents.
draft_filesarrayPaths of the current working files in this archive.
revisionsarrayEvery published revision: revision, published_at, published_by, published_by_user_id, published_by_handle, description, frontmatter, source, in_publication_history (false after a withdrawal), and files, the paths of its files in this archive.

mcp_servers.json.

servers lists the third-party MCP servers added to the organization, its Teams and its projects. Members' personal MCP servers are not included, and neither are the keys and tokens entered for any server.

FieldTypeDescription
slugstringServer ID, used in tool names.
name, descriptionstringName and description.
urlstringServer URL, as entered.
authstringHow it signs in: none, shared (one key for everyone), personal (each person's key) or oauth.
catalogstring or nullThe catalog entry it was added from.
placestringorganization, team or project, with the same identifying fields as skills.
created_at, updated_at, updated_by, updated_by_user_id, updated_by_handlestringWhen it was added and last changed, and by whom.
disabled_forarrayUser IDs of the people who switched it off for their agents.

activity.json.

events lists what agents did through the Venom MCP server in the last 30 days, oldest first. Records describe each operation. They never contain tool arguments, content or results.

FieldTypeDescription
event_idstringEvent ID.
actor_id, actor_user_id, actor_handlestringWho the agent acted for: their sign-in subject, user ID and handle.
operation, categorystringThe tool or operation, and its category: read, write, manage, skill, mcp or other.
sourcestringAlways mcp.
path, skill_name, revision, resource_uristring or nullWhat a skill load or resource read targeted.
client_id, client_name, client_versionstring or nullThe agent client, as it identified itself.
request_idstring or nullThe client's request ID.
started_at, finished_atstringWhen the operation started and finished.
statusstringsucceeded, failed, started (still running), or unknown (no outcome was recorded).
duration_ms, error_codeinteger, string or nullHow long it took, and why it failed.
bytes_read, bytes_written, lines_returned, created, replacementsinteger, boolean or nullSize measures, where the operation reports them.

On this page