Documentation

Understand the service before you connect it.

These short guides cover the developer flow, supporter payments, privacy boundaries, and key handling. For more depth, see the technical setup guide and how the platform is built.

Developer quickstart

1. Sign in with GitHub

boostmyagents requests public GitHub identity only. It does not request repository access.

2. Get your boost page

Your personal boost page is created the first time you sign in. From the dashboard you can also add public repositories owned by your GitHub account; each gets its own page and key. Organization repositories are not supported yet. Add the generated badge to your README.

3. Receive your gateway key

Your first key is created at sign-in. The LiteLLM virtual key is shown once. Store it in your password manager or secret store. If it is lost, regenerate it; the old secret is never revealed again.

4. Connect your coding agent

Point Claude Code or a compatible Anthropic client at the boostmyagents gateway and use a supported model. Usage is metered until the boost is exhausted. The technical setup guide has the exact commands and the model list.

What supporters buy

A supporter buys a fixed boost for restricted AI usage through hosted Stripe Checkout. The developer receives no cash and the boost is not a charitable donation.

Fee model: 95% of each boost pays for developer AI usage and 5% is the boostmyagents platform fee. Card-processing fees and applicable tax are shown separately at checkout.

Supporters do not create accounts. boostmyagents does not store supporter email addresses or card details; Stripe handles payment information.

Security and privacy

Prompt contents

Prompt contents are private. They are not inspected to determine which repository a developer worked on.

Budget enforcement

The gateway counts request tokens, clamps output, and rejects requests that could exceed the available ceiling. The launch configuration permits one concurrent request per virtual key.

Key handling

Recipient secrets are show-once virtual keys. The application stores identifiers and prefixes, not a retrievable copy of the secret.

GitHub access

GitHub OAuth uses public identity only and never requests repo scope.

Frequently asked questions

For supporters

Is a boost a donation?

No. It purchases restricted AI usage and is not charitable or tax-deductible.

Are boosts refundable?

No. Boosts are non-refundable except where the law requires it. If you believe a charge was made in error, email michel@breezyassist.com before opening a dispute with your card issuer.

What fees do I pay?

A 5% platform fee is taken from the boost amount, and Stripe’s processing fee is added on top. Both are shown before you pay.

Do I need an account to boost someone?

No. You pay through hosted Stripe Checkout without creating an account.

How much can I boost?

Boosts are fixed amounts from $5 to $50. You pick one on the developer’s boost page.

Can I leave a message for the developer?

Yes. You can add an optional message of up to 500 characters when you boost.

Do boosts expire?

Yes. A boost expires one year after it is confirmed. Usage the developer has not spent by then is forfeited; it is not refunded, extended, or transferred. We are building a common pool so that expired boosts go on to fund other open-source developers.

Can boostmyagents prove which repository used the boost?

No. Repository attribution is honor-system because prompt surveillance would violate the privacy boundary.

For developers

What does it cost me?

Nothing. Creating an account, a boost page, a badge, and a gateway key is free, and you are not charged for boosts you receive.

Can I withdraw a boost as money?

No. A boost is never paid out as cash and cannot be transferred to another account.

Which models and tools work?

The Anthropic models on our supported models list. Tools that run on your own machine work normally, including Claude Code’s file, search, and shell tools. Tools that run on Anthropic’s servers are rejected: hosted web search (which Claude Code’s built-in web search relies on), web fetch, code execution, and hosted MCP servers. Fast mode and priority tiers are rejected too. Each key runs one request at a time.

What happens when my boost runs out?

Requests that would cost more than what remains are rejected before they reach Anthropic. Rejected requests are not charged, and you are never billed for going over.

What if a supporter disputes their payment?

The remaining usage from that boost is removed while the dispute is open. If the dispute is resolved in our favour, it is restored.

What do you log about my requests?

Technical metadata only: client name and version, feature flags, timings, token counts, and error codes. It is kept for 30 days. Prompt and response content is never recorded.

What if I lose my key?

Regenerate it from your dashboard. The old key cannot be shown again.