Can I use the token from a browser app?

No. The API is server-side only and does not send CORS headers. A token in a browser bundle is a token on the internet. Call it from your backend, a serverless function, a bot, or the revnu CLI, and keep the token in an environment variable.

Start Here / Introduction

Revnu API, CLI and MCP Docs

The Revnu API, CLI and MCP server let your software read and approve your growth agent's review queue, message it and pull results. Start here.

Last updated 1 October 2026

Revnu runs GTM on autopilot for software businesses: a growth agent finds buyers, runs outreach, ads and GEO, and asks for your approval before anything important goes out. These docs cover its developer surface: a JSON API over HTTPS, the revnu CLI, and an MCP server for Claude, ChatGPT and Cursor.

Your Revnu agent queues anything that needs your say-so: outreach drafts, blog posts, budgets, questions. The API lets your own software read that queue, approve or decline from wherever you already work, message the agent, and pull results into your own reporting.

It is the agent's front door, not a toolbox. Nothing here sends email, publishes or spends except through the same approvals the dashboard uses.

The contract in one screen

Base URL:  https://revnu.com/api/v1
Auth:      Authorization: Bearer rvp_...   (server-side only)
Format:    JSON in, JSON out, every response Cache-Control: no-store

What you can do

Review queue. List what is waiting, read one card, approve, answer, choose, send, request changes, snooze, dismiss.
Agent. Send a message, wait for or poll the reply, read the thread, check whether the agent is up.
Results. The same scoreboard the agent wakes up with, plus workflows and their run history.
Leads. Read leads, their contacts, and one lead's surfaced draft and research; set a lead's labels; manage the block list.
LinkedIn. Look up one person's LinkedIn connection, invite and conversation with your connected accounts. Read-only.
Workflows. Create, edit, pause, resume and delete recurring workflows.

What it will not do

No provider tools (Gmail, Attio, ads, SEO, Reddit) are exposed. The only direct writes are a lead's labels (PATCH /leads/{id}), the block list, and workflows (the same plain-language steps and schedule the dashboard editor writes); no campaign controls, no settings writes. Provider side effects still flow through the agent and its trust ladder.

Where to start

Quickstart: from a fresh token to an approved card in ten minutes.
Authentication and scopes: how tokens work and which scope each call needs.
Use with Claude, ChatGPT and Cursor: add https://revnu.com/api/mcp as a connector and your assistant can drive your agent.

Agents: this page is also markdown at /docs/introduction.md, answers Accept: text/markdown, and is listed in /docs/llms.txt.

Frequently Asked Questions

No. The API is the agent's front door, not a toolbox. Every send, publish or spend goes through the same review cards and trust ladder the dashboard uses. Approving a card ships what the agent already drafted, and a read-only token cannot cause a send, a publish or a spend at all.