Skip to content
AudonDocs
Esc
  • OverviewGet started
  • Free spend auditGet started
  • Provider setupSpend Optimization
  • Fixes and Auto-applySpend Optimization
  • MethodologySpend Optimization
  • Action Control conceptsAction Control
  • Quickstart: SDKAction Control
  • Action Gateway (MCP)Action Control
  • For agents: onboard yourselfAction Control
  • Action catalog and custom actionsAction Control
  • Connectors: Stripe, Shopify and WebhookAction Control
  • Policies and approvalsAction Control
  • Free action auditAction Control
  • Action Control API referenceAction Control
  • REST APIPlatform
  • MCP serverPlatform
  • Security overviewTrust
  • StatusTrust
  • SubprocessorsTrust
  • Terms of ServiceLegal
  • Privacy PolicyLegal
  • Data Processing AddendumLegal
  • Cookie PolicyLegal
  • Acceptable Use PolicyLegal
  • AI Data Use PolicyLegal
  • Billing and Cancellation PolicyLegal
  • Auto-apply Add-on TermsLegal
Documentation menu: Action ControlAction audit

Action Control

Free action audit

The read-only historical audit of Stripe or Shopify history and agent logs: what it reads, the detectors and the finding classes.

The action audit is the free, read-only way in. It looks at what already happened: your Stripe or Shopify history and, if you have them, your agents’ tool-call logs. Nothing is executed and nothing changes in your systems. It is free on every plan.

1. Connect Stripe or Shopify read-only

Click Connect with Stripe to install Audon’s read-only Stripe App (read access to charges and refunds, customers, coupons and subscriptions), or Connect Shopify store to install the Audon app with read access to orders, refunds, discounts, gift cards and store credit. Neither can change anything. A Stripe restricted key with read permissions works too (Use an API key instead); if a key can also write, Audon warns you.

From Shopify the audit reads orders (as payments), their refunds, code discounts, gift cards and store credit; Shopify shows the last 60 days of orders unless the app holds read_all_orders. Agent logs may name an order by its GID, its numeric id or its name (#1001): all three match.

2. Upload agent logs (optional)

Logs let the audit tie money movements to agent tool calls. Two formats:

jsonJSONL, one tool call per line
{"timestamp":"2026-10-31T09:14:02Z","agent":"support-agent","tool":"refund_create","arguments":{"charge":"ch_3QmX…","amount":45000},"result":{"status":"succeeded"}}

Or OpenTelemetry (OTLP/JSON) spans that carry gen_ai.tool.name and gen_ai.tool.call.arguments. Upload in the app or with POST /v1/integrity/audit-logs.

What is kept, and for how long. Audon doesn’t store the file. It keeps one row per business tool call (time, agent, tool, action type, ids, amount, status, and a hash of the arguments, never the arguments or message text) and deletes those rows automatically 7, 30 (default) or 90 days after the audit that read them, as set under Settings → Budget and retention, or after the upload when no audit runs. Delete now on the audit page (or DELETE /v1/integrity/audit-logs/{upload_id}) deletes them at once. Findings stay.

3. Run it

Start the audit in the app or with POST /v1/integrity/audits (202). It imports up to 90 days: charges, refunds, coupons and canceled subscriptions (up to 5,000 per type), and customer balance credits for up to 200 customers seen in the period.

What it finds

DetectorFinds
duplicate_refundMore than one refund for the same charge or order.
refund_exceeds_paymentRefunds above the payment, or on a payment already refunded in full.
large_refund, large_credit, large_discountAmounts above three times the period’s 95th percentile or your stated threshold; coupons of 50% or more.
customer_burstThree or more money actions for one customer within 24 hours.
agent_burstAn agent making at least max(10, 5 × its median) calls in an hour.
failed_actionActions that failed at the provider.
repeated_actionThe same agent, tool and arguments within 10 minutes.
refund_without_intentWith logs: a refund with no matching agent call within 15 minutes.

Finding classes

  • Flagged action: worth a look.
  • Suspected loss: money that likely left in error.
  • Confirmed loss: duplicate refunds that both succeeded at the provider while the log shows two separate refund calls, or a loss a person confirmed.

Found, not prevented

The audit finds losses that already happened. They can be recovered, but they are never counted as prevented. Prevention starts when live actions run through Audon: see the quickstart or the Action Gateway.

Last updated