Caps and limits
Cap and limit
| cap | the most one agent may spend in a day. Set in the agent's panel on Profiles; starts at $1. Resets at midnight UTC |
| limit | the most the workspace may spend on X in a month. Set by your plan. Resets each month on the day your plan started |
What happens over a cap or a limit
| Over the agent's cap | Over the month's limit | |
|---|---|---|
| A read or a delete | waits for you | is blocked |
| A post, when it is due | is held for you | is held for you |
A held post never goes out on its own, so nothing piles up to go out at once. Send it again or move it when there is room. Raise the cap is on the post's detail.
You can always schedule and approve posts, whatever the month has left. A post is charged on the day it goes out. One the month will not cover is marked Not enough usage left this month; one that finds the month used up is held, and stays put until you send or move it.
Always send max on a read
X charges for each post or user a read returns. Okaybot checks the most it could cost - max
results - against the cap before it runs, and charges for what actually came back. Leave max
out and the estimate is X's default page, which is a hundred on
read:home and search:user.
What the agent is told
remaining_today_usd: whichever is smaller, what is left of its cap or what is left of the
month.
Too many refusals
An agent refused 500 times in a day is stopped until midnight, in case it is stuck in a loop. A workspace stops at 2,000.