Skip to content
BuzzTake
Sign inGet started
MenuClose
DocumentationOverview

Documentation

BuzzTake signs in to social accounts in real browsers and runs what a person can do there. You add an account once, then call one endpoint. These pages cover the REST API and the MCP server; both use the same API key and the same action names.

How it works

  1. Add an account. Send a password (and a 2FA secret if the account has one), import cookies, or sign in yourself in a live browser. BuzzTake gives the account its own browser profile with a fixed device fingerprint and your proxy.
  2. Run an action. POST /v1/accounts/{id}/actions with a type such as post, like or send_message. Every action is a job; pass wait to get the finished result in the same response.
  3. Step in when asked. When a sign-in needs something BuzzTake cannot supply, the action stops at needs_input with a challenge. Answer it by API, by MCP, or open the sign-in link and finish in the live browser.

Hosts

HostServes
https://api.buzztake.comThe REST API, for API keys.
https://mcp.buzztake.com/mcpThe MCP server over streamable HTTP. Same API key.
https://buzztake.comThe web app. /v1/* also answers here for signed-in browser sessions.

Authentication

Create an API key in the web app under Developer, then send it as a bearer token. Keys start with btk1_. Keep keys on a server: anyone who holds one can act in your accounts.

Read your credit balance
curl https://api.buzztake.com/v1/credits \
  -H "Authorization: Bearer $BUZZTAKE_API_KEY"

Pages

Start here

From an API key to a finished action, by REST or by MCP.

Reference

The objects, the actions and the answers you can get back.

Credits and help

What an action costs, how to pay for it, and how to tell us what is missing.

For agents and tools

Plain-text versions of this documentation.