Declare what your HTTP action counts

A generic HTTP executor cannot infer how much money or how many records an arbitrary endpoint changes. Declare the quantity explicitly, and review that declaration alongside the request. Anlyon enforces the quantity you write before dispatch; it does not independently discover the business meaning of every API.

An impact declaration specifies a dimension, unit, amount expression and bound. Supported expressions are intentionally limited: an integer, an input path or an input collection count, with an optional integer multiplier. Use the current reference for the exact schema.

Choose an honest quantity

Operation shape	Candidate quantity
One existing record update	One resource mutation
Send to a list of recipients	Recipient count, including every supported recipient field
Explicit monetary transfer	Validated integer amount in one currency
Bulk operation with bounded expansion	A justified upper bound on actual impact

An upper bound that is too low is a definition error. A collection length is also inadequate if the provider expands one input into many downstream operations. Document that behavior before claiming a limit on the resulting business impact.

Test the expression and the request together

Try empty input, missing fields, wrong types, boundary sizes and the largest allowed request. Compare the declared quantity with what the endpoint actually does. Do not test the expression in isolation while the request template reads a different input field.

If an applicable limit exists and the quantity cannot be evaluated, the governed effect is refused. Without an applicable limit, an effect lacking a quantity may still run. Opting into a governed record alone does not create a meaningful business allowance.

Review changes as behavior changes

When the API or request template changes, revisit the declaration. Adding cc recipients or a bulk expansion option can invalidate an earlier count. Keep the action definition, input validation and operator explanation aligned.

Calls made directly to the provider remain outside Anlyon's limit. Keep alternate execution paths constrained independently.

Configure declared actions, inspect impact-limit semantics, then choose the scope that should share the quantity.