canonical: https://jentic.com/apis/fuseai.com/fuseai

# Fuseai Fuse Business API

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.

## For AI 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.

## Scope

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

## Capabilities

- 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
- Deanonymize website visitors and read campaign, dialer, and enrichment analytics roll-ups
- Create signal-based agents such as funding-announcement, job-change, and headcount-growth watchers
- Read the token owner's identity, credit balance, and credit-spend ledger

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Lists and Contacts** — Build and populate contact lists, columns, and smart columns via `/business/lists` and its sub-resources, and manage contacts via `/business/contacts`
- **Prospecting** — Run people and company searches and save results via `/business/prospects/search`, `/business/companies/search`, and `/business/saved-searches`
- **Campaigns** — Create and run outreach campaigns, steps, and scheduled sends via `/business/campaigns` and `/business/scheduled-sends`
- **Agents and Research** — Create signal-based agents and Deep Research runs via `/business/agents` and `/business/research/runs`
- **Account** — Read identity, credit balance, spend, and analytics via `/business/me`, `/business/credits`, and `/business/analytics`

## AI readiness

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.

- **Score:** 40 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 88 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 69 / 100
  - Security: 10 / 100
  - AI Discoverability: 85 / 100
- **View full report:** https://jentic.com/apis/fuseai.com/fuseai/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

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

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Apollo** — Sales intelligence platform with its own prospect database, enrichment, and sequences
- **Clearbit** — Company and person enrichment from an email or domain
- **Instantly** — Cold email sending and deliverability at scale

## FAQ

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