Install Jentic One Beta

Connect the Buska Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Buska Public 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%2Fbuska.io%2Fbuska" | 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%2Fbuska.io%2Fbuska" | 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 Buska Public API.

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

Patterns agents use Buska Public API for, with concrete tasks.

GET STARTED

Start building with Buska Public API

Explore with Jentic One

View OpenAPI Document

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.

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.

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

Key Endpoints

4 endpoints — 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.

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

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

Why Jentic?

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

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Buska Public API through Jentic.

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.

Buska Public API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readySocial MediaSocial ListeningapiKey4 EndpointsREST

For Agents

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

Use for: Search for social mentions of my brand across platforms, Score a LinkedIn post for B2B buyer intent, Retrieve the qualified buying signals detected for my team, Find mentions of a competitor over the last week

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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

100%

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: DSignals: 4

36%

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.

44%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

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: A+Signals: 1

94%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Buska Public API to your agent

Capabilities

Use Cases

Start building with Buska Public API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Buska Public API

Jentic AI Readiness Score

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