Check a change before it touches the ad account.

oddly's recommendations are brand-respecting and demand-driving, and every change it proposes stays reversible and decrease-only by design. Before a tool, a teammate, or an automated operator changes a Meta or Google ad account, ask Verifier whether the change passes those same deterministic rules. Verifier returns approve, block, or warn, with the rule that decided and the signal it traced to.

What Verifier does

Install

Verifier is reached through the oddly platform SDK, @oddly/sdk.

# install
npm install @oddly/sdk

import { OddlyClient } from "@oddly/sdk";

const oddly = new OddlyClient({ apiKey: process.env.ODDLY_KEY });

// ask before you change the account
const verdict = await oddly.verify({
  channel: "meta",
  action: "set_budget",
  adSetId: "1234567890",
  proposedDailyBudget: 240
});

if (verdict.decision === "block") {
  // do not apply. verdict.rule explains why.
}

Full endpoint reference, request and response schemas, auth, and rate limits ship with the platform API developer docs.

What Verifier is not

• Not an executor. oddly's own executor still applies approved changes. Verifier only returns a verdict; it does not act on the account.
• Not a generic policy engine. The rules are commerce-specific, built for Meta and Google ad-account decisions, not arbitrary configuration checks.
• Not a generative model. Verdicts are deterministic. The same proposed change always returns the same decision, with no model drift.

Pricing