Install Jentic One Beta

Connect the BurstyAI API to your agent

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

Run topical-authority research as a single or bulk workflow

Generate AI-written blog posts and blog titles via /workflows/blog-writing/run and /workflows/blog-title/run

Extract LSI keywords and Google-autocomplete suggestions for a seed term

Convert a YouTube video into a blog post via /workflows/youtube-to-blog/run

Submit URLs to Google indexing in single or bulk mode

GET STARTED

Start building with BurstyAI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use BurstyAI API for, with concrete tasks.

★ AI blog post generation and publishing

Generate a long-form blog post from a topic prompt and publish it directly to WordPress in one chain. POST /workflows/blog-writing/run produces the content, /workflows/blog-title/run generates supporting title options, and /workflows/wordpress-integration/run pushes the result to a configured WordPress site. Suitable for content teams scaling top-of-funnel SEO output.

POST /workflows/blog-writing/run with the topic, then POST /workflows/wordpress-integration/run with the returned post body and the target WordPress site.

Keyword research at scale

Pull LSI keywords, Google autocomplete suggestions, nested keywords, Google Ads keyword ideas, and keyword intent classifications from a single integration. The bulk variants accept a list of seed terms, making it suitable for SEO agencies running research for multiple clients in parallel.

POST /workflows/lsi-keywords/bulk/run with a list of seed keywords, then POST /workflows/keyword-intent/bulk/run on the merged set to classify intent.

Lead research and backlink analysis

Run /workflows/company-research/run on a list of target domains and /workflows/backlink-research/run to find backlink opportunities, producing structured records suitable for cold outreach and SEO link building. Each workflow has bulk and scheduled variants for repeatable pipelines.

POST /workflows/company-research/run for each prospect domain, store the structured results, and feed them into a CRM enrichment step.

AI agent SEO assistant via Jentic

An AI assistant can take a single prompt - for example, 'create a blog post on agentic AI and publish it' - and orchestrate the BurstyAI blog-writing, internal-link extraction, and WordPress integration workflows end to end. Jentic securely stores the BurstyAI API key and issues scoped, short-lived access for each call.

Search Jentic for 'write an AI blog post', load the /workflows/blog-writing/run schema, execute it with the topic, then chain the WordPress publish workflow.

Key Endpoints

32 endpoints — jentic publishes the only available openapi specification for burstyai api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/workflows/blog-writing/run

Run AI blog writing for a single topic

POST

/workflows/blog-writing/bulk/run

Run AI blog writing for a batch of topics

POST

/workflows/lsi-keywords/run

Generate LSI keywords for a seed term

POST

/workflows/google-indexing/run

Submit a URL to Google indexing

POST

/workflows/keyword-intent/run

Classify keyword search intent

POST

/workflows/youtube-to-blog/run

Convert a YouTube video to a blog post

POST

/workflows/wordpress-integration/run

Publish a generated post to WordPress

POST

/workflows/company-research/run

Run company research on a domain

POST

/workflows/blog-writing/run

Run AI blog writing for a single topic

POST

/workflows/blog-writing/bulk/run

Run AI blog writing for a batch of topics

POST

/workflows/lsi-keywords/run

Generate LSI keywords for a seed term

POST

/workflows/google-indexing/run

Submit a URL to Google indexing

POST

/workflows/keyword-intent/run

Classify keyword search intent

POST

/workflows/youtube-to-blog/run

Convert a YouTube video to a blog post

POST

/workflows/wordpress-integration/run

Publish a generated post to WordPress

POST

Why Jentic?

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

Setup

Wiring BurstyAI by hand means learning its Authorization-header API key, keeping track of the single, bulk, and scheduled variant for each workflow, and polling long-running jobs through /aiflowjobs/{jobId}/result yourself. Through Jentic you install once, import the BurstyAI API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

BurstyAI routes each request through a workflow path like /workflows/blog-writing/run with the seed topic or keyword list in the request body, so you limit the agent to the operations it needs, such as running blog writing or generating LSI keywords. That keeps heavier operations like WordPress publishing or Google indexing submission out of reach unless you add them.

Credential isolation

Your BurstyAI 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 'write an AI blog post' or 'generate LSI keywords for a seed term', and Jentic returns the matching /workflows/{name}/run operation with its input schema, so the agent picks the right workflow without reading the BurstyAI docs.

FAQs

Specific to using BurstyAI API through Jentic.

Why is there no official OpenAPI spec for BurstyAI API?

BurstyAI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call BurstyAI API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the BurstyAI API use?

BurstyAI uses an Authorization header containing your API key. Through Jentic, the key is stored encrypted in the vault and a scoped, short-lived token is issued per operation so the raw key never enters the agent's context.

Can I run a BurstyAI workflow on a batch of inputs?

Yes - most workflows have a bulk variant such as /workflows/lsi-keywords/bulk/run and /workflows/blog-writing/bulk/run that accept an array of inputs in a single call.

Can I schedule a BurstyAI workflow to run on a recurring cadence?

Yes. The /schedule endpoints (e.g., /workflows/topical-authority/schedule) accept a schedule definition so the workflow runs automatically without you re-triggering each call.

What are the rate limits for the BurstyAI API?

The OpenAPI spec does not declare explicit limits. BurstyAI applies per-account quotas tied to the plan - handle 429 responses with retry-with-backoff and prefer bulk endpoints to single endpoints when processing many inputs.

How do I run a BurstyAI workflow through Jentic?

Run `pip install jentic` and search for 'write an AI blog post' (or any other workflow). Jentic returns the matching /workflows/{name}/run operation, you load its schema, and execute the call with the input payload - credentials stay in your Jentic One instance.

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

Yes. Because you run Jentic One yourself, your own rules decide which BurstyAI workflow operations and credentials the agent may use. Each BurstyAI request maps to a distinct workflow path such as /workflows/blog-writing/run or /workflows/lsi-keywords/run, so you can allow only the operations the agent needs and keep heavier ones like /workflows/wordpress-integration/run or /workflows/google-indexing/run out of reach until you grant them.

BurstyAI API

Name: BurstyAI API
Brand: BurstyAI API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticMarketingSeo SemapiKey32 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Run AI-powered SEO, content, and lead-research workflows in single, bulk, or scheduled mode - including blog writing, keyword research, internal-link extraction, and Google indexing.

Use for: I need to write a blog post on a given topic, Generate a list of LSI keywords for a seed keyword, Submit a batch of URLs to Google indexing, Convert a YouTube video into a blog article

Not supported: Does not handle paid ad management, social posting, or analytics dashboards - use for AI-driven SEO, content, and lead-research workflows only.

Jentic publishes the only available OpenAPI specification for BurstyAI API, keeping it validated and agent-ready. The BurstyAI API provides AI-driven workflow endpoints for SEO, content creation, lead research, and marketing operations. Each workflow comes in single, bulk, and scheduled variants so the same operation can be run for one input, a list of inputs, or on a recurring cadence. Workflows cover topical authority, LSI keywords, internal-link extraction, Google indexing, keyword intent analysis, blog writing, blog title generation, YouTube-to-blog conversion, AI image generation, WordPress publishing, Google autocomplete, nested keywords, Google Ads keyword ideas, backlink research, and company research. Authentication is a single Authorization header containing an API key.

Jentic One on Github View OpenAPI Document

Connect the BurstyAI API to your agent

Capabilities

Start building with BurstyAI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

BurstyAI API