Install Jentic One Beta

Connect the Fuse Business API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fuse Business 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%2Ffuseai.com%2Ffuseai" | sh

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%2Ffuseai.com%2Ffuseai" | 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 Fuse Business API.

Run people and company searches against the accepted filter values and save results to a list

Build prospect lists with members, custom columns, and AI smart columns that research every row

Enrich a list's contacts in place and push them into a connected CRM

Create email outreach campaigns with sequence steps, scheduled sends, and approval gates

GET STARTED

Start building with Fuse Business API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Fuse Business API for, with concrete tasks.

★ AI Agent Prospecting via Jentic

An AI agent reaches Fuse Business through Jentic to find and qualify prospects without wiring the HTTP Basic auth or tracking credits itself. It searches by intent, receives the matching operation and its input schema, and executes the search with the token injected at run time. This lets the agent turn a target definition into a saved, enriched list in one flow.

Search Jentic for 'search for prospects and save them to a list', load the POST /business/prospects/search schema, and execute it with the Fuse token injected at run time

Prospect List Building and Enrichment

A sales team turns a search definition into a working, enriched contact list. Fuse runs a people search against its filter options, saves the matches to a list, and enriches the contacts in place so every row carries the data the team needs. Smart columns can then research each row and record where each value came from.

Call POST /business/prospects/search to find matching people, POST /business/prospects/search/save-to-list to save them, then POST /business/lists/{listId}/enrich to enrich the contacts in place

Outreach Campaign Automation

A revenue team builds and activates an email outreach campaign from a draft. Fuse creates the draft, adds sequence steps, and queues scheduled sends that can be reviewed and approved before they go out. Campaign analytics and per-lead state let the agent track replies and progress step by step.

Call POST /business/campaigns to create a draft, POST /business/campaigns/{campaignId}/steps to add sequence steps, then POST /business/campaigns/{campaignId}/approve to activate it

Signal-Based Account Monitoring

A team watches target accounts for buying signals and reacts automatically. Fuse creates signal-based agents, such as a funding-announcement or job-change watcher, and activates them to surface matching people and companies into lists. Because activating an agent spends credits, the credit ledger lets the team keep the spend in view.

Call POST /business/agents/funding-announcements to create a funding-announcement agent, then POST /business/agents/{agentId}/activate to start it

Key Endpoints

146 endpoints — the fuse business api runs b2b prospecting and sales outreach from one surface: it searches people and companies against accepted filter values, builds and enriches contact lists, and drives multi-step email campaigns with scheduled sends and approval gates.

METHOD

PATH

DESCRIPTION

POST

/business/prospects/search

Run a people search

POST

/business/companies/search

Run a company search

GET

/business/lists

List the token owner's prospect lists

POST

/business/lists/{listId}/enrich

Enrich a list's contacts in place

POST

/business/campaigns

Create a draft campaign

POST

/business/campaigns/{campaignId}/approve

Approve and activate a campaign

GET

/business/credits

Get the token owner's credit balance

GET

/business/me

Get the token owner's identity

POST

/business/prospects/search

Run a people search

POST

/business/companies/search

Run a company search

GET

/business/lists

List the token owner's prospect lists

POST

/business/lists/{listId}/enrich

Enrich a list's contacts in place

POST

/business/campaigns

Create a draft campaign

POST

/business/campaigns/{campaignId}/approve

Approve and activate a campaign

GET

/business/credits

Get the token owner's credit balance

GET

/business/me

Get the token owner's identity

Why Jentic?

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

Setup

Wiring Fuse by hand means handling its HTTP Basic auth with your af_ token as the username, polling its async jobs for exports, enrichment, and research, and tracking credit spend yourself. Through Jentic you install once, import Fuse Business from the API Directory, store the token once, and your agent calls it.

Permission scoping

Fuse puts resource ids in the URL path, such as /business/lists/{listId} and /business/campaigns/{campaignId}, so a rule can pin your agent to the lists and campaigns it should touch. You choose which operations it may call, so destructive ones like list deletion or campaign approval are not included unless you add them.

Credential isolation

Your Fuse API token 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 'find companies that raised funding' or 'create an outreach campaign', and Jentic returns the matching Fuse operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Fuse Business API through Jentic.

What authentication does the Fuse Business API use?

The Fuse Business API uses HTTP Basic authentication per its OpenAPI spec: you pass your API token (an af_ prefixed string) as the Basic-auth username with an empty password, and it is required on the /business operations. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.

What are the rate limits for the Fuse Business API?

The OpenAPI spec does not specify rate limits. Fuse meters usage in credits instead: the credits balance and the credit-usage ledger report your headroom and spend, so an agent can check them before a costly run such as enrichment or a research run. See https://docs.fuseai.com for current limits.

Can I search for prospects with the Fuse Business API?

Yes. POST /business/prospects/search runs a people search using the accepted filter values from GET /business/prospects/filter-options, and POST /business/companies/search runs the equivalent company search. You can save either result set straight into a list and then enrich it in place.

Is there a Fuse Business API MCP server?

You don't need an MCP server to give your agent Fuse Business. Jentic connects it directly from the API Directory: import it and your agent calls the prospecting, list, and campaign operations on demand, discovering each operation's schema when it needs it rather than loading a separate server's tool definitions into context.

How do I build and enrich a prospect list with the Fuse Business API through Jentic?

Search Jentic for 'search for prospects and save them to a list', and it returns the Fuse search operation with its input schema. Save the matches to a list, then call POST /business/lists/{listId}/enrich to enrich the contacts in place. 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 Fuse Business API?

Yes. Write a rule that allows only the search and list-building operations a task needs, for example running a prospect search and saving the results to one list, so the agent cannot delete lists, approve campaigns, or push contacts to your CRM. Because every call runs through your own instance, each one is logged for you to review.

Fuseai Fuse Business API

AI ReadinessNon-Ready (F)40/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact Managementbasic146 EndpointsREST

For Agents

Search prospects and companies, build and enrich contact lists, run email outreach campaigns, and create signal-based monitoring agents. All operations use HTTP Basic auth with an API token and are metered in credits.

Use for: Search for software company decision-makers in a target industry, Find companies that recently announced funding, Build a prospect list and enrich its contacts, Create an email outreach campaign with a multi-step sequence

Not supported: Does not handle payment processing, contract e-signature, or support ticketing. Use for B2B prospecting, list enrichment, and email outreach only.

The Fuse Business API runs B2B prospecting and sales outreach from one surface: it searches people and companies against accepted filter values, builds and enriches contact lists, and drives multi-step email campaigns with scheduled sends and approval gates. It also exposes AI smart columns that research every row, knowledge hubs built from websites, deanonymized website-visitor feeds, and signal-based agents that watch for funding announcements, job changes, and headcount growth. Analytics roll-ups and a credit ledger report campaign, dialer, and enrichment activity so a team can track spend. Usage is metered in credits and every operation belongs to the authenticated token owner's workspace.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

91%

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).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

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

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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.

AI-Readiness & Agent Experience

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

Grade: C-Signals: 4

52%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

55%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: B+Signals: 1

69%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

10%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

85%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Fuse Business API to your agent

Capabilities

Start building with Fuse Business API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Fuseai Fuse Business API

Jentic AI Readiness Score

Fuse Business API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness