Bolt Claw documentation

Find documentation pages about a subject. Returns an id, a title, a URL and a matching line for each hit, best first. Pass the id to `fetch` to read the page.

Read one documentation page in full, as markdown. The id is what `search` returns, which is the page's path without /docs/ - for example `authentication` or `api/pages`.

What the API is, where it lives, and a worked example that creates a page and answers a message.

How a key is issued, what a scope allows, and why a key never does more than the person who created it.

Every code, what it means, and what to change. Branch on `code`, never on the sentence.

A plan changes volume, never capability. Here are the numbers, and the headers that tell you where you are.

The three shapes a success body takes, and why lists are cursors rather than page numbers.

A request that timed out may still have succeeded. `Idempotency-Key` is how you retry without doing it twice.

What you can exercise without live effects, and what is real from the first call.

Register a URL and we POST to it. The event catalog, the signature, and what happens when your receiver stops answering.

Rates per product or plan, groups and levels, bonuses and ceilings, and why every commission is the amount it is.

An invite-a-friend panel inside your own product, or your own screen on the same data, with sessions your server mints.

Tell a person who arrives through a referral link what it gives them, on your site or ours, and check it at checkout.

Free months, credit, perks, gift cards and the friend's discount, for either side, and the grants that track them.

Codes used at Stripe Checkout credited without a key, and with a restricted key, coupons, promotion codes and rewards given for you.

How every referral program's fraud engine scores, holds and asks, and what a person decides.

Pay every promoter with one press from your own PayPal, Wise, Stripe, Tremendous, Trolley or Tango account. BoltClaw never holds the money.

Hand each payout to your own system by a signed webhook, read where it goes, and report the result.

Promoters sign a W-9 or W-8 inside BoltClaw, payouts wait for it, and at year end you download your 1099-NEC data. BoltClaw never files anything for you.

Issue an invoice in each EU or UK business promoter's name for every payout, take their own invoice from everyone else, and give every payout a statement.

Referral links on go.example.com and your partner portal on partners.example.com: every DNS step, what each domain serves, and removing one.

Your logo, colours and name on the partner portal, the join page, the panel and partners' emails, and how partners sign in without a new password.

The partner directory, messages to your promoters, importing a partner list, a file library, links to any page, campaign tags and the disclosure line.

A leaderboard inside one program, contests with prizes a person awards, milestones that give rewards, a waitlist people move up, and a fenced second tier.

Terms written from your program's own settings, your customers' privacy requests answered, and what partners download and delete themselves.

Every program's commissions, conversions, partners, payouts, rewards and contest results as a spreadsheet, and last month by email.

Twelve billing systems connected directly, the live setup status, and test data that never touches real money.

Where a referral cookie needs consent, the tag waits for your banner: one attribute, one call, and a snippet for each consent tool.

Stripe in one click with the Bolt Claw Stripe App, or a webhook and its signing secret: checkouts, invoices, refunds, disputes and codes.

A notification destination and its secret: transactions, renewals, refunds and chargebacks, with discount ids learned from Paddle's own events.

An endpoint signed with Standard Webhooks: paid orders, renewals and refunds, with discount codes credited from their text.

A webhook signed with Standard Webhooks: payments, refunds and disputes, with promo codes credited from their text.

A header token Bolt Claw makes, plus RevenueCat's own signing: in-app purchases, renewals and refunds on every store.

A webhook with its own secret: paid orders and refunds, coupons credited from their code, every delivery claimed so it counts once.

A webhook with an HMAC secret and Expansion on: orders, subscription charges, returns and chargebacks.

A signing secret Bolt Claw makes for you: orders, renewals and refunds. Lemon Squeezy sends no discount code.

Webhooks with the store's own key and no app: paid orders, refunds and disputes, with partner links credited from the landing page.

A webhook protected by Basic auth Bolt Claw makes, because Chargebee signs nothing: payments, renewals and refunds.

An endpoint secret and a read-only API key: every invoice is read from Recurly before it counts.

Gumroad's unsigned ping and an access token: every sale is re-read from Gumroad before it counts.

The tag in the root layout, the code kept by middleware, every signup reported as a lead from a server action.

The tag in your templates, a middleware that keeps the code, and each signup reported from its route.

The code saved in the new user's metadata, and an Edge Function that reports the signup with the verified user.

A callable Cloud Function that reports each signup with the signed-in user's own id.

The code saved on the sign-up, and Clerk's user.created webhook reporting each new user as a lead.

The code kept by your server, and each new user reported from the createUser event.

The code kept by your server, and each new user reported from an after-hook on sign-up.

The tag in your base template, a middleware that keeps the code, and each signup reported from its view.

The tag in your layout, a before_action that keeps the code, and each signup reported after it is created.

The tag in your layout, a middleware that keeps the code unencrypted, and each signup reported from the Registered event.

Webflow, Framer, Bubble and the like: the tag in the site-wide code, your billing system, and signups from the builder's workflows.

Install the app, link a program: codes become discounts, orders are credited, buyers invite their friends.

One plugin: the tag, every order and refund reported once, partner codes as coupons, an invite on the order page.

The Zapier app's triggers, actions and searches, and importable Make and n8n templates with every webhook verified.

For shops not on the app: each paid Shopify order reported as a sale, from Make or n8n.

When a reward that is not cash is ready, give the credit in your own tool and mark it fulfilled.

A Slack message for every approved partner, by display name, with the webhook's signature checked first.

One row for every commission a partner earns, safe from formulas, with the webhook's signature checked first.

Where the tag goes on Webflow, Framer, Bubble, Carrd, Squarespace and Wix, and what each one needs.

Keep partners' old links working, bring the partners over, and point your webhooks at the new events.

The hosted Model Context Protocol server, so an AI assistant can do what your key can do and nothing more.

What `/v1` promises, what is deliberately not versioned, and everything that has changed.

Your key and its workspace.

The workspace's API keys, and what each may do.

Link-in-bio pages, served at boltclaw.ai/{slug}.

The links on a page, in display order.

Threads people start from a page, and the messages in them.

The endpoints registered to receive events. Read only here.

Connected network accounts. Connecting one happens in the dashboard.

Posts to one or more connected accounts, now, scheduled, or as drafts.

Images and videos for posts, uploaded in two steps.

Comments, mentions and direct messages from every connected account.

Comment-to-DM rules that reply to people and capture leads.

Contact details people chose to give.

The organisation's plan, allowances and platform charges.

Referral programs, partners, conversions, commissions and payouts.

Device sign-in, approvals, and a key acting on itself.

What assistants did here, and what everybody did here.