Action contracts let your AI execute approved backend operations — refund an invoice, suspend a license, route a ticket — without ever touching your raw database. Every call signed, every operation gated by role, every write requiring explicit confirmation.
An action is a registered, signed, role-checked, audited contract — never raw database access.
Each action is a JSON contract: name, parameters, scope, allowed roles, confirmation policy, endpoint URL. Drop it in actions.json, OpsIQ reads it, the AI now knows it exists. No code change needed in the AI itself.
Your backend uses HMAC-SHA256 over the raw body to prove the call really came from OpsIQ. Replay protection via timestamp.
Per-action policy: never / once-per-session / always. Confirmation cards show the exact preview before execution.
Every action attempt and execution stored: actor, role, params, response, duration, IP.
Action surfaces let the same registry serve admin AI, client AI and writing AI without overlap.
WHMCS, custom SaaS, WordPress, your internal portal, your ERP. The pattern is platform-neutral.
When an admin says "refund Adam's last invoice", the AI matches the intent against the registered action contracts, finds saas.refund_invoice, fills the parameters from your live data, returns a confirmation card. Admin clicks confirm. OpsIQ POSTs the signed action to your endpoint. AI History captures every step.
The WHMCS connector ships WHMCS-specific actions. The Stripe connector ships Stripe-specific actions. The opsiq_saas connector ships SaaS-specific actions. You enable the connectors you use, the actions appear automatically — your AI now knows how to talk to the platforms you actually run.
No. Confirmation policy is enforced server-side. The AI cannot fake a confirmed=true flag — the action runner ignores AI-supplied confirmed values for actions whose policy requires human approval.
OpsIQ shows the error in the audit log and surfaces it back to the admin. The action is not retried automatically for non-idempotent operations.
The action contract is JSON. The endpoint can be in any language that handles HTTP and HMAC. PHP, Node, Python, Go, Rust — all fine.
Define your first action contract in 10 minutes. Read the developer docs for the schema.