Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Marketing / Revnu API
Revnu API logo

Revnu API

66
AI ReadinessAI-Aware (B)66/100
See full scorecard
Official vendor OpenAPI document · agent-readyMarketingMarketing Automationbearer36 EndpointsREST

For Agents

Approve or dismiss Revnu's pending outreach and content cards, run and pause recurring GTM workflows, read leads and results, and maintain the do-not-contact block list.

Use for: List the review cards waiting for my approval in Revnu, Approve and send the pending Gmail draft, Pause the weekly outreach workflow until next month, Add these competitor domains to the do-not-contact block list

Not supported: Does not host a CRM, process customer payments, or send email outside its approval queue. Use for controlling Revnu's GTM agent, its workflows, leads, and content only.

The Revnu API controls Revnu's go-to-market agent for software businesses, routing anything that sends, publishes, or spends through the same approval queue the dashboard uses. It lists review cards waiting for approval and lets you answer, send, snooze, dismiss, or request changes on each, and it composes, runs, pauses, and resumes recurring workflows from a plain-words schedule. Leads come back with status, score, contacts, and research, alongside a do-not-contact block list, a per-channel results scoreboard, and a chat channel to message the agent directly. Separate endpoints serve published blog posts to a Content API token and accept server-side signup, booking, and payment events for attribution.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Revnu API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Revnu API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frevnu.com%2Frevnu" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frevnu.com%2Frevnu" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Revnu API.

Review Revnu's approval queue and answer, send, snooze, dismiss, or request changes on each card

Compose recurring workflows from a plain-words schedule and run, pause, resume, or delete them

Page through leads by status or workflowRunId and read one lead's contacts, draft, and research

Block companies, mailboxes, or LinkedIn profiles from outreach, up to 500 per call

Read the per-channel growth scoreboard covering email, ads, SEO, social, and LinkedIn

Message the Revnu agent and poll its reply by requestId

Serve published blog posts with markdown, HTML, and JSON-LD to your own site through the Content API

Use Cases

Patterns agents use Revnu API for, with concrete tasks.

★ Approving GTM work from your own agent

Revnu holds outbound email, posts, and spend in a review queue until someone approves them. A developer's coding or ops agent can work that queue through Jentic: it searches by intent, gets the reviewList and reviewAnswer operations with their input schemas, and calls them with the personal token injected at execution time. Leaving reviewSend out of the allowed operations keeps the agent from sending real email while it triages.

Call GET /api/v1/review with status pending, read each card with GET /api/v1/review/{id}, and call POST /api/v1/review/{id}/snooze on any card that needs the founder's input

Scheduling and controlling recurring workflows

Recurring GTM jobs such as a weekly prospect list or a monthly SEO refresh live as Revnu workflows. POST /api/v1/workflows composes one from a schedule in plain words and a list of steps, POST /api/v1/workflows/{id}/runs starts the next run now without changing the schedule, and the pause and resume operations stop and restart it without losing history. GET /api/v1/workflows/{id}/runs returns per-step outcomes for each run.

List workflows via GET /api/v1/workflows, find the one named 'Weekly prospect list', start a run via POST /api/v1/workflows/{id}/runs, then read GET /api/v1/workflows/{id}/runs for the queued run's status

Keeping outreach off the wrong contacts

Before Revnu researches or emails anyone, its send and research gates check the block list. POST /api/v1/blocklist adds domains, email addresses, or LinkedIn profiles, up to 500 per call, and is idempotent, so re-sending a whole list is safe. GET /api/v1/blocklist pages through the entries and DELETE /api/v1/blocklist/{id} removes one, except for addresses that unsubscribed, which stay blocked.

Add the customer domains from the CRM export to the block list via POST /api/v1/blocklist, then confirm the added and existing counts in the response

Attributing signups and payments

Revnu ties results back to the channel a visitor came from when your server reports the outcome. POST /api/measurement/events, authenticated with a server-side event key, records signups, booked calls, and payments, and the response says whether the event matched a visitor and counted toward the site's win definition. GET /api/v1/results then shows the per-channel scoreboard.

Send a signup event to POST /api/measurement/events from the server after a new account is created, then read GET /api/v1/results to see the email and SEO sections

Key Endpoints

36 endpoints — the revnu api controls revnu's go-to-market agent for software businesses, routing anything that sends, publishes, or spends through the same approval queue the dashboard uses.

METHOD

PATH

DESCRIPTION

GET

/api/v1/review

List the review queue

POST

/api/v1/review/{id}/answer

Answer a review card

POST

/api/v1/workflows

Create a recurring workflow

POST

/api/v1/workflows/{id}/runs

Run a workflow now

GET

/api/v1/leads

List leads

POST

/api/v1/blocklist

Add block list entries

GET

/api/v1/results

Get the results scoreboard

GET

/api/content/v1/posts

List published posts

GET

/api/v1/review

List the review queue

POST

/api/v1/review/{id}/answer

Answer a review card

POST

/api/v1/workflows

Create a recurring workflow

POST

/api/v1/workflows/{id}/runs

Run a workflow now

GET

/api/v1/leads

List leads

POST

/api/v1/blocklist

Add block list entries

GET

/api/v1/results

Get the results scoreboard

GET

/api/content/v1/posts

List published posts

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

R

Revnu API

- AI-Aware (B)
66/100
74
Foundational Compliance
68
Developer Experience & Jentic Compatibility
50
AI-Readiness & Agent Experience
94
Agent Usability
60
Security
73
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
74

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

0%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

68

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

73%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

50

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4
62%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

83%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

54%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

60

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

73

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
73%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Revnu by hand means juggling three bearer tokens, a scoped personal token for the main API, a Content API token, and a server-side event key, and routing each call to the right one. Through Jentic you install once, import Revnu from the API Directory, store each token once, and your agent calls it.

Permission scoping

Revnu puts the review card, workflow, and lead id in the URL path, as in /api/v1/workflows/{id}/pause, so a rule can pin your agent to one workflow or to the review operations it needs. You choose the operations it may call, so ones like sending a Gmail card or deleting a workflow are not included unless you add them.

Credential isolation

Your Revnu tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list cards waiting for approval' or 'pause a workflow', and Jentic returns the matching Revnu operation with its input schema so the agent calls the right endpoint without reading the docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Instantly API

→

Cold email sending platform with campaigns and lead lists you run yourself

Choose Instantly when you want to run cold email campaigns directly; choose Revnu when its agent should plan the work and you approve each send

Alternative

lemlist API

→

Multichannel outreach sequences across email and LinkedIn

Choose lemlist for hand-built sequences; choose Revnu for an agent-run GTM program gated by an approval queue

Complementary

Apollo API

→

People and company data to research and qualify leads

Use Apollo to enrich or source contacts, then add unwanted domains to Revnu's block list or review Revnu's surfaced leads

FAQs

Specific to using Revnu API through Jentic.

What authentication does the Revnu API use?

Per its OpenAPI spec, the Revnu API uses three HTTP bearer schemes: a personal API token (personalToken, rvp_ prefix) scoped per token for the /api/v1 endpoints, a read-only Content API token (contentToken, rvc_ prefix) for blog posts, and a server-side event key (eventKey, rsk_live_ prefix) for the Event API. Through Jentic each token is held by your own Jentic One instance and attached at call time.

Can the Revnu API send email on its own?

Only through the approval queue. POST /api/v1/review/{id}/send approves and sends a Gmail reply or draft and needs the review:write scope, and it sends real email. Other actions on a card, such as snooze, dismiss, or request changes, close or defer it without sending.

What are the rate limits for the Revnu API?

The OpenAPI spec does not list numeric rate limits, but GET /api/v1/me returns the rate limits the current token is held to, along with its label and scopes. Check https://revnu.com/docs for the documented limits.

Is there a Revnu MCP server?

You don't need an MCP server to give your agent Revnu. Jentic connects it directly from the API Directory: import it, store your token once, and your agent discovers the review, workflow, and lead operations on demand without another server's tool definitions in its context.

How do I run a Revnu workflow through Jentic?

Search Jentic for 'run a Revnu workflow now', call GET /api/v1/workflows to find the workflow id, then execute POST /api/v1/workflows/{id}/runs. The run is queued and appears in GET /api/v1/workflows/{id}/runs with per-step outcomes. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Revnu API?

Yes. For a triage agent, write a rule that allows GET /api/v1/review, GET /api/v1/review/{id}, and POST /api/v1/review/{id}/snooze. It can read and defer cards but cannot approve, send email, or touch workflows, and every call it makes is logged. Revnu's own token scopes, such as review:read, add a second bound.

Can I publish Revnu blog posts on my own site?

Yes. GET /api/content/v1/posts lists published posts with cursor paging and filters by type and time, and GET /api/content/v1/posts/{slug} returns one post render-ready, with markdown, safe HTML, a table of contents, head metadata, and JSON-LD. Both use the read-only Content API token.

GET STARTED

Start building with Revnu API

Explore with Jentic One
View OpenAPI Document