canonical: https://jentic.com/apis/buska.io/buska

# Buska Public API

The Buska API searches social mentions across platforms, scores a post for B2B buyer intent with Buska AI, and returns the qualified buying signals detected for your team. A single search covers mentions across 19 platforms, and a usage endpoint reports your current quota. It pairs social listening with lead qualification so an agent can go from a mention to a scored signal.

## For AI agents

Search social mentions across platforms, score a post for B2B buyer intent, and retrieve qualified buying signals detected for your team.

## Scope

Does not handle post publishing, direct messaging, or ad campaign management. Use for social-listening search, intent scoring, and buying signals only.

## Capabilities

- Search social mentions across platforms for a keyword or brand
- Score a post for B2B buyer intent with Buska AI
- Retrieve qualified buying signals detected for your team
- Check your current API usage and remaining quota

## Use cases

### Agent-driven social listening

An AI agent monitoring a brand can search Buska for mentions across the 19 platforms it covers, then score the most relevant posts for buyer intent so the team sees which mentions are worth a reply. The search and scoring happen through two calls the agent chains.

Example prompt: Search mentions for the brand 'Acme' and score the top post for B2B buyer intent

### Buying-signal lead qualification

A sales agent can pull the qualified buying signals Buska has detected for the team and act only on the strongest, using the lead-scoring call to confirm intent before adding a prospect to outreach. The usage endpoint shows how much quota each run consumes.

Example prompt: Retrieve the qualified buying signals for the team and score each to rank them by intent

### Quota-aware monitoring

A monitoring automation can check its remaining Buska quota before each search run, so a scheduled job that watches several keywords never exceeds the plan. Buska applies a monthly subscription quota first and pay-as-you-go credits as a fallback.

Example prompt: Check the current Buska usage and quota, then run a mention search only if quota remains

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/mentions/search` | Search social media mentions |
| POST | `/leads/score` | Score a post for B2B lead qualification |
| GET | `/signals` | List qualified buying signals |
| GET | `/usage` | Get current API usage and quota |

## Key resources

- **Mentions** — Search social media mentions across platforms
- **Leads** — Score a post for B2B lead qualification with Buska AI
- **Signals** — List qualified buying signals detected for your team
- **Usage** — Read current API usage and remaining quota

## 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:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 70 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 94 / 100
- **View full report:** https://jentic.com/apis/buska.io/buska/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 Buska by hand means handling its x-api-key header and its two-tier billing where a monthly quota is spent before pay-as-you-go credits. Through Jentic you install once, import Buska from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** You choose which Buska operations the agent may call, such as mention search and signal reads, so the lead-scoring operation is not included unless you add it.
- **Credential handling:** Your Buska 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.
- **Discovery method:** Agents search Jentic by intent such as 'search social mentions for a brand', and Jentic returns the matching Buska operation with its input schema so the agent calls the right endpoint without browsing the docs.

## Related APIs

- **Sprout Social** — Sprout Social is a full social-management suite with listening; Buska focuses on intent-scored mentions.
- **Apify** — Apify scrapes social and web data at scale; Buska scores mentions for buyer intent.
- **Apollo.io** — Apollo runs the outreach; Buska supplies the buying signal that triggers it.

## FAQ

### What authentication does the Buska API use?

The Buska API authenticates with an API key sent in the x-api-key header, per its OpenAPI spec. You generate the key in the Buska settings under the API tab.

### Is there a Buska MCP server?

You do not need an MCP server to give your agent Buska. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the search, scoring, and signal operations without loading another server's tool definitions into its context.

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

Yes. Write a rule that allows only mention search and signal reads, so the agent can listen and read detected signals but cannot spend credits on lead scoring until you add that operation, and every call it makes is logged.

### Can I score a post for buyer intent with the Buska API?

Yes. The lead-scoring endpoint runs a post through Buska AI and returns a B2B buyer-intent qualification, so an agent can rank mentions by how likely they are to signal a purchase.

### What are the rate limits for the Buska API?

The OpenAPI spec states a rate limit of 60 requests per minute per API key. Beyond that, a two-tier billing applies: your monthly subscription quota is spent first, then pay-as-you-go credits.

### How do I search social mentions with the Buska API through Jentic?

Search Jentic for 'search social mentions for a brand', and it returns the Buska mention-search operation with its input schema. Pass the keyword, read back the mentions across platforms, and score the ones worth acting on. To run it on your own infrastructure, install Jentic One from its GitHub repo.