Criteria & Credits

Daily pull caps

Acquisition tools fetch from external services that bill Aims directly (not your credit balance), so they are guarded by a per-user daily cap rather than by credits. The cap is the safety rail against a runaway automation burning through paid fetches. There are three independent budgets:

Each successful call spends one unit of the matching budget; budgets reset at 00:00 UTC. When a budget is exhausted the tool returns a clear error and does nothing — no fetch, no charge. Re-adding an existing social source still counts against the cap, because the cap limits how many add attempts an automation can make, not just new sources. The defaults above can be raised per deployment by the workspace owner.

How credits are spent

The create tools spend credits from your balance automatically on each call — the same way generating in the web app does. Your balance is effectively the ceiling: when it is too low, the call fails up front with an insufficient-credits error and nothing is charged.

• aims_copy_to_image — a flat ~25 credits per image (High quality, 2K). Charged on call; refunded automatically if the job fails to queue or dispatch.

• aims_copy_to_video — video tokens, varying with duration and resolution (longer and higher-resolution cost more). Charged on call; refunded automatically on a queue/dispatch failure.

• aims_recreate_post — a small fixed credit cost for the text rewrite, refunded automatically if the rewrite fails.

Generation runs in the background. Image and video tools return a jobId immediately and you poll aims_get_job for the finished URL; the post rewrite returns its text on the spot. Because spend is automatic, the assistant should confirm before generating in bulk — and the shipped prompts are written to generate one deliberate result at a time rather than fanning out.