Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PlusVibe.ai 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.
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%2Fplusvibe.ai%2Fplusvibe" | shStep 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%2Fplusvibe.ai%2Fplusvibe" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with PlusVibe.ai API.
Get workspaces accessible with the API key
Create a new campaign
List all campaigns in a workspace
Add leads to a campaign
Delete leads from a campaign
GET STARTED
Patterns agents use PlusVibe.ai API for, with concrete tasks.
★ Developer Tools Operations
Use the PlusVibe.ai API to perform developer tools operations programmatically. The API provides 11 endpoints covering core functionality including get workspaces accessible with the API key, create a new campaign, list all campaigns in a workspace.
Call GET /authenticate to get workspaces accessible with the API key
Automated Account Management
Automate account operations by combining multiple PlusVibe.ai API endpoints. Agents can create a new campaign and then list all campaigns in a workspace in a single workflow.
Call POST /campaign/add/campaign to create a new campaign, then verify the result
AI Agent Integration via Jentic
AI agents discover and call PlusVibe.ai API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'get workspaces accessible with the API key', load the operation schema, and execute with Jentic-managed credentials
11 endpoints — plusvibe.
METHOD
PATH
DESCRIPTION
/authenticate
Get workspaces accessible with the API key
/campaign/add/campaign
Create a new campaign
/campaign/list-all
List all campaigns in a workspace
/lead/add
Add leads to a campaign
/lead/get
Get or search for a lead by email
/lead/delete
Delete leads from a campaign
/account/list
List all email accounts in the workspace
/analytics/campaign/stats
Get detailed campaign statistics
/authenticate
Get workspaces accessible with the API key
/campaign/add/campaign
Create a new campaign
/campaign/list-all
List all campaigns in a workspace
/lead/add
Add leads to a campaign
/lead/get
Get or search for a lead by email
/lead/delete
Delete leads from a campaign
/account/list
List all email accounts in the workspace
/analytics/campaign/stats
Get detailed campaign statistics
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the PlusVibe.ai API by hand means setting up API key auth against api.plusvibe.ai, then wiring campaign, lead, and analytics calls yourself. Through Jentic you install once, import the PlusVibe.ai API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
PlusVibe.ai identifies campaigns and leads through request payloads rather than pinning a record in the URL path, so scope the agent to the operations it needs, such as adding a lead or listing campaigns. You choose that set, so a destructive operation like lead deletion is included only if you add it while a read-only agent keeps just the list and stats operations.
Credential isolation
Your PlusVibe.ai API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'add a lead to a campaign' or 'get campaign stats', and Jentic returns the matching PlusVibe.ai operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using PlusVibe.ai API through Jentic.
What authentication does the PlusVibe.ai API use?
The PlusVibe.ai API uses an API key passed in the `x-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get workspaces accessible with the API key with the PlusVibe.ai API?
Yes. Use the GET /authenticate endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the PlusVibe.ai API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get workspaces accessible with the API key through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get workspaces accessible with the API key'. Jentic returns the matching PlusVibe.ai API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the PlusVibe.ai API have?
The PlusVibe.ai API exposes 11 endpoints covering account, analytics, authenticate operations.
Can I limit what my agent is allowed to do with the PlusVibe.ai API?
Yes. Because you run Jentic One yourself, you decide which PlusVibe.ai operations your agent may call and which credentials it may use. PlusVibe.ai identifies campaigns and leads through request payloads rather than the URL path, so you scope by operation: give a read-only agent only list campaigns and campaign stats, or add lead creation when it needs to write. A destructive call such as deleting leads from a campaign is available to the agent only if you explicitly include it.
For Agents
Programmatically get workspaces accessible with the API key, create a new campaign. Covers 11 operations with apiKey authentication.
Use for: I need to workspaces accessible with the API key, I want to a new campaign, Search for all campaigns in a workspace, Find all add leads to a campaign
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
PlusVibe.ai (formerly Pipl.ai) is a cold email automation platform. The API provides access to workspaces, campaigns, leads, email accounts, analytics, unibox email management, webhooks, blocklists, and tags. The API exposes 11 endpoints secured with apiKey authentication.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>