Credits and risk

Aeolo uses credits for server-side work. Read-only commands should be cheap or free; background analysis and generation consume credits.

Typical risk levels

Risk	Examples	Agent behavior
Read-only	`agent context`, `visibility show`, `content get`	Does not mutate state or spend credits, but may expose private business data. Run after the user/domain/task scope is clear.
Draft mutation	`content import`, `content update`, `post import`	Confirm if changing existing user work.
Paid background job	`content generate`, `reference analyze`, `video generate`, `visibility check run`	Explain cost and ask unless already approved.
Public preview	`content preview`, `post preview`	Creates or reuses an unauthenticated share-token URL.
External publish	`content deploy`, `post publish`	Always require explicit approval.

aeo billing credits
aeo billing ledger

Use the ledger after a failed job to verify whether credits were refunded.

The backend is the source of truth. Frontend or agent copy should describe modes, not hardcoded provider names.