Integration

Beehive Pay integration

Beehive Pay (BeehiveHub) is a Brazilian payment gateway; amounts are in centavos of BRL. Charge buyers by credit card (a card token made in the buyer's browser, never a raw card number), PIX or boleto, list, read and refund transactions and report delivery progress; create and look up customers; create hosted checkouts and public payment links; manage recipients (payees), their payout rules and bank accounts, read the available balance and the company profile, and pay out with transfers. Answers carry buyers' personal data (name, email, phone, CPF/CNPJ, address); bank account numbers are withheld. Production accounts only (the sandbox runs on another host). Not exposed: the sandbox-only test status change, company profile updates, reading a checkout back and reading one bank account by id (the host does not serve it). Authentication is HTTP Basic with the secret key (Settings, API credentials) as the username and the letter x as the password.

Connect Beehive Pay How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Beehive Pay.Built from the 24 Beehive Pay tools below, on the connection you add once.

What you can do with Beehive Pay

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Payment link, 5 operations

create_payment_linkCreate payment linkPOSTAgents: ask firstPublishes a public payment link anyone with its address can pay: https://link.conta.paybeehive.com.br/<alias>. Send alias, title, amount in centavos and settings (which of card, PIX and boleto are offered).
delete_payment_linkDelete payment linkDELETEAgents: ask firstDeletes a payment link by id (from list_payment_links). Beehive documents no way to restore a deleted link.
get_payment_linkGet payment linkGETAgents: ask firstReturns one payment link by id: alias (public address https://link.conta.paybeehive.com.br/<alias>), title, amount in centavos, status and payment options.
list_payment_linksList payment linksGETAgents: ask firstLists the company's payment links with alias, title, amount in centavos, status and payment options. Payers open https://link.conta.paybeehive.com.br/<alias>.
update_payment_linkUpdate payment linkPUTAgents: ask firstRewrites a payment link: read it with get_payment_link first and send back alias, title, amount and the whole settings object with your change (another alias changes the public address). Returns the link.

Recipient, 4 operations

create_recipientCreate recipientPOSTAgents: ask firstCreates a recipient (payee) for split payments and payouts with its legal name, CPF/CNPJ, payout rules and the bank account it is paid into (holder document must equal the recipient's). Returns the recipient with its id.
get_recipientGet recipientGETAgents: ask firstReturns one recipient by id: legal name, CPF/CNPJ, payout rules (payouts enabled, automatic anticipation, anticipatable percentage) and, when Beehive returns it, its balance in centavos.
list_recipientsList recipientsGETAgents: ask firstLists the company's recipients (payees) with their CPF/CNPJ, payout rules and, when Beehive returns it, balance. An id goes to create_transfer, get_balance or a split rule's recipientId.
update_recipientUpdate recipientPUTAgents: ask firstChanges a recipient's legal name and, optionally, its payout rules. legalName is always required: read it with get_recipient and send it back to keep it. Returns the recipient.

Transaction, 4 operations

create_transactionCreate transactionPOSTAgents: ask firstCharges a buyer real money: credit_card needs card {hash} from Beehive's browser tokenization (or {id} of a saved card) and installments; pix answers pix.qrcode (or pix.qrCode); boleto answers boleto.url and digitableLine. Returns the transaction.
get_transactionGet transactionGETAgents: ask firstReturns one transaction by id: status, amounts and fees in centavos, splits, refunds, delivery status, the PIX code or boleto line, and the buyer's personal data (name, email, phone, CPF/CNPJ, address). Use it to check whether a charge was paid.
list_transactionsList transactionsGETAgents: ask firstLists the company's transactions, filtered by status, payment method, delivery status, installments or the buyer's name, email, CPF/CNPJ or phone. Each holds the buyer's personal data. Paging is not documented.
refund_transactionRefund transactionPOSTAgents: ask firstRefunds a paid transaction, sending real money back to the buyer: leave amount out to refund the whole transaction or what remains of it. Returns the updated transaction with its refunds.

Customer, 3 operations

create_customerCreate customerPOSTAgents: ask firstCreates a customer (buyer) with name, email and CPF/CNPJ document, plus optional phone, address and your own externalRef; returns it with the id that create_transaction takes as customer.id. Stores personal data.
get_customerGet customerGETAgents: ask firstReturns one customer by id: name, email, phone, birth date, CPF/CNPJ and address (personal data), plus revenue totals (amounts and counts paid by card, PIX and boleto, refunded and charged back).
list_customersList customersGETAgents: ask firstLooks up customers by email address (required: Beehive documents no other filter and no paging). Returns each match with its personal data and revenue totals.

Bank account, 2 operations

add_recipient_bank_accountAdd recipient bank accountPOSTAgents: ask firstAdds a bank account to a recipient; Beehive documents this as the way to change the recipient's main account, where its payouts go. The holder's CPF/CNPJ must equal the recipient's. Returns the account.
list_recipient_bank_accountsList recipient bank accountsGETAgents: ask firstLists a recipient's bank accounts: bank, branch, account type, holder name and CPF/CNPJ, and which one is active. Account numbers are withheld. Banking and personal data.

Transfer, 2 operations

create_transferCreate transferPOSTAgents: ask firstPays out real money from the balance to a recipient (recipientId from list_recipients; get_company's defaultRecipient.id is the main one), to pixKey or bankAccount if given, else the recipient's main bank account. Check get_balance first.
get_transferGet transferGETAgents: ask firstReturns one transfer (payout) by id: status (for example pending, bank_processing, success or failed), amount and fee in centavos, failReason, destination PIX key or bank account (account number withheld) and receipt URL.

Balance, 1 operation

get_balanceGet balanceGETAgents: ask firstReturns the available balance, in centavos of BRL, of one recipient (recipientId) or, when left out, of the company's main recipient. Check it before create_transfer.

Checkout, 1 operation

create_checkoutCreate checkoutPOSTAgents: ask firstCreates a hosted checkout page for a cart and returns its secureUrl to send the buyer to. Once a transaction made through it is confirmed, no other one can be created from it.

Company, 1 operation

get_companyGet companyGETAgents: ask firstReturns the company behind the secret key: legal and trade name, CPF/CNPJ, enabled payment methods and payout fees, business details, address, revenue totals and its main recipient (defaultRecipient.id).

Delivery, 1 operation

update_transaction_deliveryUpdate transaction deliveryPUTAgents: ask firstSets the delivery status of a physical order (waiting, in_transit or delivered) and its carrier tracking code; the transaction must have been created with traceable true. Returns the updated transaction.

Use Beehive Pay from Claude Code, Cursor or Codex

Connect Beehive Pay in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Beehive Pay operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Beehive Pay

Create your workspace
Sign up free. Nothing to install.
Connect Beehive Pay once
Add your Beehive Pay connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.