Free workflow

Normalize displayed prices and update a cart snapshot

Displayed prices may use different decimal separators, and an agent can overwrite the wrong cart entry if it applies an unguarded change. Normalize prices first, then test the expected record before editing its snapshot.

1

Read the price with its declared format

Supply a supported locale, currency and decimal scale. For example, 1.234,56 € with de-DE, EUR and two decimal places becomes 1234.56. Check each returned valid flag; ranges, prose, conflicting currency tokens and excess precision remain errors. A shared $ symbol does not establish which dollar currency the merchant uses.

commerce.money-parse · free
2

Guard changes to the supplied snapshot

Use a test operation on the expected SKU or currency before replacing a price or quantity. Map only a valid normalized amount into the patch value. Array additions insert at an index; /- appends. If any operation fails, no result is committed and the original supplied snapshot is unchanged. This tool does not write to a merchant cart or place an order.

data.json-patch · free
3

Recalculate explicit components

Map the updated snapshot into the item schema, including unitPrice, quantity and discount. Supply the same declared currency and decimal scale. Keep unavailable shipping, tax and fees as null. A known subtotal is not a complete checkout total until every component is supplied.

commerce.price-components · free

Normalized price strings, a guarded JSON snapshot and an exact reconciliation. Each operation is a separate call; currency selection, product identity and permission to modify a real cart remain the caller's responsibility.

These are separate free calls. Map fields explicitly; no automatic merchant changes.

Run the complete recipe

Node.js 22+. No account or key needed. Default preview is offline; --execute performs three free calls.

Download cart workflow SHA-256 · Sample input · Instructions
node cart-workflow.mjs --execute cart-example.json

Free access, with clear limits

All available hosted tools are free during validation. Existing input, output and source-access limits apply. Full tools and the combined report share capacity limits that count attempts, including failed executions and marked checks; they are not per-user allowances. No account, API key, wallet or funding is needed. Existing credit balances are preserved. Live Reddit remains unavailable until configured. Paid billing will not resume automatically.

Hosted full executions share 1,000 attempts per UTC day and 60 per minute. Local browser audits and comparisons do not consume that hosted allowance. Bounded previews retain their own limits. Results can omit content; inspect source attribution, missing values and truncation. Byte reduction is not measured model-token or dollar savings.

Try a real task, then tell agentutilities@proton.me whether it helped. Omit credentials and private records. Feedback is optional.