Integrations, API and MCP

Integrations

Your data only moves between Zelvorm products in the ways listed here. Everything else stays where you put it.

Shared between products

Information that moves between Zelvorm products
From	To	What moves	When
Every product	Your Zelvorm account	Your name, email and sign-in. One account opens every product you can sign up for.	Automatic.
Zelvorm Books	Intelligence: Business Digital Twin	Balances and accounts from one business, so the model starts from your real numbers.	Only when someone who owns the business links it. It can be unlinked.
Mission Control	Intelligence, in a client organisation's workspace	The organisation's website, staging sites, Google Analytics, Search Console, Google Ads and Meta Ads connections.	Set up once in Mission Control. Intelligence must be turned on by the organisation's owner.
Zelvorm Launch	Zelvorm Watch	A shortcut that adds your live domain to Watch. Nothing else moves between them.	You click it, once your domain is live.
Zelvorm Patente	Patente Drive	The game opens in your Patente language, and each round points to the matching theory topic.	Automatic: the game is part of Patente.
Zelvorm Tools	Your Zelvorm account	Favourites and which tools you used recently, when you're signed in.	Only if you sign in. The tools work without an account.

Kept separate

Zelvorm Office

Contacts, deals, projects and payroll stay in Office. Office payroll doesn't post into Books, and Office doesn't appear in the API.

Zelvorm Watch

Sites, checks and problems stay in Watch, and aren't in the API.

Zelvorm Atlas

Directories, listings and reviews stay in Atlas, and aren't in the API.

Zelvorm Crew

Your company, staff, tasks and their work stay in Crew, and aren't in the API. Staff read public web pages, but can't open your other Zelvorm products. If you connect Slack or Teams, the work you ask for there is posted back there.

Zelvorm Commerce

Your shops, products, orders, ad spend and messages stay in Commerce, and aren't in the API. Commerce reads from your shop (by its public product list, a CSV or WooCommerce read-only keys; the Shopify app is coming soon) and never writes back. Store Spy reads competitors' public product lists only.

Zelvorm Guard

Orders stay in Guard, and aren't in the API. Your own store can send new orders to Guard's scoring API with a key you make, and gets the score back. Confirmations go out from your WhatsApp or by text, never from us; buyers' contact details are wiped 90 days after the outcome.

Zelvorm Stock

Products, sales and purchase orders stay in Stock, and aren't in the API. Stock reads products and sales from Commerce or a CSV and never writes to your shop or emails suppliers: you send the purchase orders.

Zelvorm Listings

Listings stay in Listings, and aren't in the API. You import a CSV or paste a listing and copy the result back: Listings never writes to Amazon, Etsy or your store. Keyword ideas come from Google's public search suggestions.

Zelvorm Price Lab

Price Lab reads products, costs and orders from Zelvorm Commerce and competitor prices from Commerce's Store Spy. It never changes a price in your shop: you do.

Zelvorm Ad Doctor

Ad Doctor reads the CSV reports you export from Meta, TikTok and Google Ads, and your real sales from Zelvorm Commerce. It never logs in to an ad account or changes a campaign.

Zelvorm Customs

Customs reads duty rates from the UK Trade Tariff (and its Northern Ireland tariff for EU rates) and the US International Trade Commission's HTS, and exchange rates from the European Central Bank. Only the HS code and country of origin are sent; your products stay in Customs.

Zelvorm Loop

Loop reads delivered orders from Zelvorm Commerce, emails review requests from your shop's name, and gives you a public reviews page, a widget script for your store and a returns portal. Reviews and returns aren't in the API.

Zelvorm Lens

Lens stores your product pictures. AI pictures are made with Google's Gemini image models from the photo you choose; the checker and editing tools run in your browser. Lens never posts to a marketplace.

Zelvorm Patente

Your answers and exams stay in Patente, and aren't in the API.

API and MCP

Let your own tools read your data.

Claude, ChatGPT or your own scripts can read your Books summaries, Intelligence results, favourite tools and project status. They can propose a Books journal or a support ticket, but nothing changes until you approve it in your account.

1. Sign in and open Account → API and MCP.
2. Make a token. Choose what it may read and which businesses or organisations it covers.
3. Copy it straight away. You're only shown it once.
4. Send it as Authorization: Bearer zv_…

Rate limit: 60 calls a minute, per token
Token lifetime: 30, 90, 365 days
Proposals wait: 14 days, 50 at a time
Logging: Every call is logged in your account

Leaving a business or organisation cuts a token off from it at once. Only Books, Intelligence, Tools and Mission Control are in the API today.

MCP server (Streamable HTTP)

{
  "mcpServers": {
    "zelvorm": {
      "type": "http",
      "url": "https://www.zelvorm.com/api/mcp",
      "headers": {
        "Authorization": "Bearer zv_your_token"
      }
    }
  }
}

Use this in any MCP client that can send a custom header.

REST API

curl https://www.zelvorm.com/api/v1/me \
  -H "Authorization: Bearer zv_your_token"

REST endpoints under /api/v1
GET	/api/v1/me	Who the token belongs to
GET	/api/v1/books/businesses	The Books businesses the token may read
GET	/api/v1/books/{id}/summary?from=&to=	Cash, money owed, income, expenses and profit
GET	/api/v1/books/{id}/accounts	Chart of accounts
GET	/api/v1/intelligence/results?workspace=&saved=1	Recent or saved results
GET	/api/v1/intelligence/results/{id}	One result, with its text
GET	/api/v1/tools/favourites	Favourite and recent tools
GET	/api/v1/projects	Mission Control projects
GET	/api/v1/proposals/{id}	Where a proposal stands
POST	/api/v1/books/{id}/journals	Propose a journal
POST	/api/v1/organisations/{id}/tickets	Propose a support ticket

Reference

Tools and permissions.

MCP tools

get_account · account:read
Who this token belongs to, and the Zelvorm products they use.
list_books_businesses · books:read
The Zelvorm Books businesses this token may read.
get_books_summary · books:read
A business's cash and bank balance, what customers owe, what it owes, and income, expenses and profit for a period (journal dates, inclusive). Figures come from the double-entry ledger.
list_intelligence_results · intelligence:read
Recent Zelvorm Intelligence results in a workspace: 'personal' or an organisation id. Set saved_only to see pinned results only.
get_intelligence_result · intelligence:read
One Intelligence result, with its Markdown output.
list_favourite_tools · tools:read
The person's favourite free tools and the ones they used recently.
list_projects · projects:read
Mission Control projects in the organisations this token may read: name, status, dates.
list_books_accounts · books:read
A business's chart of accounts (code, name, type), for proposing journals.
propose_books_journal · books:propose
Propose a manual journal in a Books business. It is NOT posted: it waits until the account owner approves it. Debits must equal credits. Use account codes from list_books_accounts.
propose_support_ticket · projects:propose
Propose a support ticket to the Zelvorm team for an organisation. It is NOT sent: it waits until the account owner approves it.
get_proposal · account:read
Where a proposal stands: pending, approved, rejected, failed or expired.

Permissions a token can have

account:read
Your name, email and which Zelvorm products you use.
books:read
Summaries of the businesses you choose: cash, owed, profit for a period.
intelligence:read
Your saved and recent Intelligence results.
tools:read
Your favourite tools and recent tool use.
projects:read
Status of the projects in the organisations you choose.
books:propose
Suggest journal entries in the businesses you choose. Nothing is posted until you approve it.
projects:propose
Suggest support tickets in the organisations you choose. Nothing is sent until you approve it.

Other ways in and out

Zelvorm Office: messages in

Each company has a secret address. Send customer messages to it from a website form, Zapier or a WhatsApp provider, as JSON with a channel, a name, an address and a message.

Zelvorm Watch: one line of script

Add it to your site to report missing addresses. Download the redirects you choose as .htaccess, nginx, Vercel JSON or CSV.

Zelvorm Launch: your domain

Point your domain at Zelvorm with two DNS records.

Intelligence: Flow Architect

A flow can start from an incoming webhook, and can call a webhook as one of its steps.

Studio client events

The Zelvorm team can send signed events to Slack, Zapier, Make, n8n or any HTTPS address, such as a new request or a paid invoice. They carry ids and a one-line summary, never personal details or amounts.

Connected services

Google Analytics, Search Console, Google Ads and Meta Ads supply numbers for reports. Stripe handles card payments where they're switched on, and WhatsApp can carry client messages to the team.

What connects, and what doesn't.