Start Here / Introduction
Introduction
What the Revnu API is for, what it can and cannot do, and where to start.
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-storeWhat 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 and their contacts. Never draft bodies.
What it will not do
No provider tools (Gmail, Attio, ads, SEO, Reddit) are exposed. No lead writes, no campaign controls, no settings writes. Anything with a side effect still flows 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 and Cursor: one config snippet 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 write 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.