Workspace and credits
Credits sit on the team workspace. MCP and REST do not open a second balance.
Credits live on the team you have open, not on your personal login. A comment you post in the browser spends the same pool as post_comment from an agent. That is why keys are minted on the team API keys page, and why a personal account has no key page.
What you should do
- Open the team you intend to spend from before you paste a URL or create a token.
- Read the credits chip in the header, or call
get_usageand readcredits_left. - Before a write, also read
comment_credits,like_credits,find_credits, and thelimitsfor the platform you will use. Those limits are not prices. They are live max length and like minimums, and they can change.
What spends credits
| Action | What to read on get_usage | Typical value today |
|---|---|---|
| One comment or one reply | comment_credits | 25 |
| One like | like_credits times quantity | 1 per like |
| One Find keyword | find_credits | 50 |
Trust get_usage and the composer over any number on this page. Those limits can change.
Credits leave the wallet when the write is accepted, before the comment is live. Retrying with the same idempotency_key does not take a second charge. An empty Find job refunds the Find credits the same way the web app refunds.
Plans, packs, and Find
Monthly plans grant a pool. Add-on packs add credits on top. When a write fails with PAYMENT_REQUIRED, the error includes checkout_url for that team's Billing page.
find_enabled is true only while the team has an active paid plan. A free grant can still paste a URL and post.
Holds
If the workspace is held, writes return HELD. Find and Post stay paused until support clears the hold. get_usage and get_status still work.
How to buy more is in Buy a plan.
Last updated on