Octave API

Name: Octave API API
Brand: Octave API
Availability: InStock

✓ Official Vendor SpecAI/MLLanguage ModelsapiKey1 EndpointsREST

For Agents

List the AI sales agents configured in an Octave HQ workspace through the public v2 API.

Connect the Octave API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Octave 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Octave API API.

List the AI agents configured in an Octave HQ workspace via /agents/list

Discover prospector, content, email, and enrichment agents available to the account

Audit which agents are deployed before triggering deeper Octave workflows

Sync the catalogue of Octave agents into an internal agent registry

GET STARTED

Start building with Octave API API

Explore with Jentic

View OpenAPI Document

Octave HQ exposes its agent platform through a public v2 API focused on listing the AI agents configured in a workspace. The platform's agents cover prospector, content, email, enrichment, qualification, and call-preparation roles aimed at outbound sales workflows. The published surface in this spec is intentionally narrow — listing agents — and provides the entry point external tools need to discover what agents exist before triggering deeper, account-specific actions in Octave.

Use Cases

Patterns agents use Octave API API for, with concrete tasks.

★ Octave Agent Inventory Audit

Audit which AI agents are configured in Octave by calling /agents/list and comparing the result to the expected inventory. Useful for revenue operations teams who need to know which prospector, content, email, enrichment, qualification, and call-preparation agents are live before approving a campaign. The single-endpoint scope keeps the integration trivial.

Call /agents/list and return the names and types of all configured agents.

Internal Agent Registry Sync

Synchronise the catalogue of Octave agents into an internal agent-registry tool by polling /agents/list on a schedule and writing the result into an internal table. Helps RevOps and engineering teams maintain a single source of truth for which third-party agents are connected to which workspaces. The endpoint is read-only, so the sync carries no risk of changing Octave configuration.

Call /agents/list nightly and upsert the rows into the internal agents table keyed by Octave agent ID.

Pre-Campaign Readiness Check

Run a pre-campaign readiness check by calling /agents/list and verifying that the prospector, email, and qualification agents required for the workflow exist before launching outbound. If any expected agent is missing the campaign is held until configuration is fixed. Fits well into a CI-style preflight job ahead of large outbound bursts.

Call /agents/list and assert that agents named 'prospector' and 'email' are present, otherwise abort the campaign.

AI Agent Octave Discovery

An orchestrating AI agent can call Octave through Jentic to discover what specialised sales agents are available to the account before deciding which workflow to invoke. The agent finds /agents/list by intent, executes it, and uses the response to plan downstream actions. Credentials remain in the Jentic vault throughout.

Use Jentic to call /agents/list and return the count of agents grouped by type.

Key Endpoints

1 endpoints — octave hq exposes its agent platform through a public v2 api focused on listing the ai agents configured in a workspace.

METHOD

PATH

DESCRIPTION

GET

/agents/list

List all configured Octave agents

GET

/agents/list

List all configured Octave agents

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Octave API keys are stored encrypted in the Jentic vault. Agents receive scoped access — the api_key header value is injected at execution time and never enters the agent's prompt.

Intent-based discovery

Agents search by intent (e.g. 'list AI sales agents in Octave') and Jentic returns the /agents/list operation with its input schema, so the agent calls the right endpoint without browsing docs.

Time to first call

Direct Octave integration: a few hours for auth and response parsing. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Apollo.io API

B2B prospecting database with email and dialer

Use Apollo alongside Octave when the prospector agent needs an external contact data source for list building.

Alternative

Instantly API

Cold-email sending platform with deliverability tooling

Choose Instantly when the agent's job is to send outbound email at scale; Octave focuses on the agent layer that decides what to send.

Alternative

Outreach API

Sales engagement platform for sequences and dialer

Choose Outreach for full sales-engagement workflow management; Octave is narrower and AI-agent-centric.

Alternative

Salesloft API

Sales engagement and revenue orchestration

Choose Salesloft for end-to-end sales engagement; Octave for workflows orchestrated by configurable AI agents.

FAQs

Specific to using Octave API API through Jentic.

What authentication does the Octave API use?

An API key supplied via the api_key header. Jentic stores the key encrypted in its vault and injects it at execution time so the raw secret never enters the agent's prompt.

Can I list all my Octave agents through this API?

Yes — that is exactly what the /agents/list endpoint returns. The response includes the agent identifier and type (prospector, content, email, enrichment, qualification, call preparation) for each agent configured in the workspace.

What are the rate limits for the Octave API?

Octave does not publish a hard quota in the spec. Cache the agent list — it changes infrequently — and avoid polling the endpoint more than once a minute. Respect any 429 responses with exponential backoff.

How do I list agents through Jentic?

Search Jentic for 'list Octave AI agents', load the schema for /agents/list, then execute. With pip install jentic the call is await client.search(...), await client.load(...), await client.execute(...) inside an asyncio.run wrapper.

Does this API let me trigger an Octave agent run?

The single endpoint exposed in this spec is /agents/list — agent execution is not part of the public v2 surface. Trigger runs through the Octave UI or contact Octave for any workflow that needs programmatic agent execution.

Is the Octave API free?

API access is tied to an Octave subscription. Confirm tier-specific entitlements in your Octave dashboard — there is no standalone free API tier in the spec.