beatapi-agent-plugin

Explore BeatAPI ·

Create an API key ·

Docs ·

Quick start ·

Security ·

Verification

BeatAPI Agent Plugin

BeatAPI is the professional capability layer for any agent: one route to Model, Data, Tool,

and Workspace capabilities. This plugin connects Codex, Cursor, Grok Bot, and

Grok Build to BeatAPI through a bundled Skill, local MCP server, typed client,

and locked public contract.

The existing host installations below use local stdio MCP. The OpenAI public

release is a separate remote MCP + OAuth package under preparation; it does not

require users to install a CLI or provide keys in chat. The owner has confirmed

the hosted ChatGPT OAuth connection and tool invocation. Full review cases,

the demo recording and public submission remain separate acceptance gates.

This repository does not configure or deploy the hosted service.

See [public submission](submission/SUBMISSION.md) for the build and review gates.

The public listing is named BeatAPI Agent Toolkit; its stable package ID

remains beatapi-agent-plugin, and existing local host manifests are unchanged.

The remote Skill is general-purpose: social/web research, SEO keyword and competitor

analysis, text and decision models, image/video generation and media workflows.

Research, SEO analysis and creative production can be used independently or combined.

SEO traffic figures are estimates, and ranking positions are dated snapshots, not live tracking.

Social data is read/research

only, not social posting. Public execution tools are generated individually from

gateway capability contracts; local capabilities_* interfaces stay compatible.

npm run submission:catalog -- --fetch reads the anonymous catalog only and writes

tool definitions, fixed-reference bindings and exclusions under dist/submission/.

These artifacts still need the hosted gateway's OAuth/transport activation; generating them

does not deploy a remote server or prove that every listed capability succeeds.

Public packaging also requires a pinned v2 catalog and a matching anonymous SDK

tool scan, not just OAuth metadata. Probe reports distinguish blocked, OAuth-only

and metadata-matched states; none substitutes for real user/workflow review tests.

DeepSeek Harness: five independently installable bundles provide

[Social Research](packages/dsh-social), [Media Kit](packages/dsh-media),

[BeatBrowser](packages/dsh-browser), [BeatDesign](packages/dsh-design), and

[BeatGEO](packages/dsh-geo). See [setup and validation](harness/README.md).

For host-independent onboarding, give an Agent this instruction:

set up https://beatapi.io/SKILL.md

The repository root [SKILL.md](SKILL.md) mirrors that setup contract; the

detailed installable Skill remains under skills/beatapi-video/.

For hosts that support remote MCP, BeatAPI also provides the stable Hosted MCP

endpoint https://beatapi.io/mcp with three provider-neutral tools:

capabilities_search, capabilities_inspect, and capabilities_run. The

bundled local MCP keeps focused workflow, upload, account, and task tools for

host-native use; both surfaces discover model IDs dynamically.

How it routes

Codex · Cursor · Grok -> Skill + local MCP -> BeatAPI -> Models · Social Data · SEO Data · Web Search · Workflows

The plugin exposes only capabilities supported by its current public contract

and the live catalog. Tool and Workspace coverage expands through reviewed

interfaces and integrations rather than README-only claims.

The repository packages the same canonical beatapi-video Skill, bundled MCP

server, typed client, and locked OpenAPI contract for four agent surfaces:

| Host | Plugin metadata | MCP configuration | API key path |

| --- | --- | --- | --- |