How It Works

Paste an instruction. Get an OPS score.

Three steps from raw text to operational decision. The whole sequence runs in seconds, in-memory, with no document persistence.

01

Receive

Paste raw instruction text from an email, PDF, MT103, or operational document. No reformatting required. The platform reads what you have.

02

Extract

Two-pass extraction maps content to ISO 20022 fields with verbatim citation — every value traces to an exact source span. The extractor never infers, fabricates, or pads identifiers.

03

Score

The 55-rule deterministic engine produces an OPS score, two component scores (Routing Confidence and ISO Readiness), and a queue assignment if review is required.

The two scores under the hood

OPS is the answer. These are the inputs.

Routing Confidence

Does the routing chain make sense? Are the BICs valid? Is there a first-hop bank? Is the corridor reachable? This score asks whether this payment can physically clear with the routing you’ve specified.

ISO Readiness

Will this instruction survive ISO 20022 validation? Required fields, identifier formats, structured remittance — weighted by operational significance, not just schema compliance.

A note on determinism

No black box. No model guess.

The scoring engine is a deterministic ruleset. The same instruction produces the same score every time. Every rule that fires is named, documented, and traceable. When your audit team asks why a payment scored 68, we can show them — rule by rule.

Try it on something real

Paste your own instruction. See the engine work.

No login. No retention. Use it as often as you’d like — bookmark it.

Open the Verifier →