Loading
Build on the API the dashboard itself uses. Publish posts, work the inbox, run automations, pull leads and run referral programs from your own code, receive signed webhooks, or let an AI assistant do it through the hosted MCP server.
You asked Claude:
Post the workshop reminder to every account on Friday.
Publishing needs your approval. Nothing has been posted yet.
Waiting for your yes
GET /v1/pages
Authorization: Bearer bc_live_...The same API the dashboard uses, with your own keys.
Every surface below runs on one versioned API, with keys you issue and scopes you choose.
Schedule posts to every connected network, upload media, and read each post's result network by network.
Social media API36 events, from a new comment to a referral payout, sent to your endpoint as signed webhooks that carry ids only.
WebhooksConnect Claude or ChatGPT through the hosted MCP server. It works with the connecting person's permissions and asks before anything consequential.
MCP serverThe boltclaw CLI signs in through your browser, keeps its key on your machine, and its commands are generated from the same API description.
Report sign-ups, sales and refunds from your server; Bolt Claw credits the partner and holds the commission through your refund window.
Referral programsCreate link-in-bio pages, add and reorder links, publish them and read their view and click counts.
Link in bioThe API, webhooks, the MCP server and the CLI are on Free, with 20 requests a minute. A paid plan raises the rate, and Pro allows 20 API keys.
Compare the plans$0, for good
$19 a month
$49 a month
$149 a month
At boltclaw.ai/docs/api. It is generated from the OpenAPI description the API is built from, with a worked request for each call, and every page also comes as markdown for an assistant to read.
You issue a key in the dashboard with the scopes it needs, out of 19, and an optional expiry. It is shown once and stored as a SHA-256 hash. A key never carries more than its creator can do today, so a changed role narrows it on the next request.
Yes. The boltclaw CLI signs in through your browser with a device code; its key is made on your machine and only the key's hash is sent. Logging out revokes the key before deleting it, and a command that waits for a person's approval exits with its own code.
Yes. Send a test event to any endpoint to check your receiver and its HMAC-SHA256 signature check, and read every attempt in the delivery log. Real deliveries that fail are retried with backoff for about twelve hours.
Your plan sets them: 20 requests a minute on Free, 60 on Creator, 120 on Pro and 600 on Business, per key. Every response tells you where you stand in its X-RateLimit headers.
The whole developer platform is on the free plan. Sign up with Google or an email address, and pay nothing until you choose a plan.