Requested vs quoted specification attributes: met, not met or not comparable

$0.005 USDC per call · Business, finance and compliance · POST /api/v1/qualifier-compare · Id qualifier-compare

Compares up to 200 requested attribute requirements with the values a supplier quoted (voltage, grade, finish, tolerance, brand, certification), for an agent checking that a quote matches the request before buying. Requirements are eq, ne, gte, lte, gt, lt, between (value..max), in (a list) or present; numeric comparisons use exact decimals, an optional tolerance, and the caller's unit conversions (none are built in). A missing quoted value, a unit with no conversion, or a non-numeric value in a numeric requirement is not-comparable, so the result is unknown rather than a pass. Text is compared after trimming and Unicode NFKC, case-insensitively unless caseSensitive. With no ordering operator and no tolerance, eq and ne read numbers only in canonical form (so "0123" and "123" are different identifiers, "100" and "100.0" are equal). Does not judge equivalence of different words or part numbers.

What you get

A quote that omits the voltage or quotes it in different units is not a match. Each attribute is met, not met or not comparable, with both values shown.

Call it

Send the JSON body below to https://agents.writerslogic.com/api/v1/qualifier-compare. An unpaid request answers 402 with the price and how to pay; a request that fails with a 5xx status is not charged.

curl -i -X POST https://agents.writerslogic.com/api/v1/qualifier-compare \
  -H 'content-type: application/json' \
  -d '{"items":[{"attribute":"voltage","requested":{"op":"gte","value":"24","unit":"V"},"quoted":{"value":"24","unit":"V"}},{"attribute":"length","requested":{"op":"eq","value":"100","unit":"mm","tolerance":"0.5"},"quoted":{"value":"10.2","unit":"cm"}},{"attribute":"finish","requested":{"op":"in","values":["anodized","powder coat"]},"quoted":{"value":"Anodised"}},{"attribute":"ip-rating","requested":{"op":"present"}}],"conversions":[{"from":"cm","to":"mm","factor":"10"}]}'

Input

FieldTypeRequiredDescription
itemsarray<object>; max 200 itemsyes
conversionsarray<object>; max 50 itemsnoCaller-supplied unit conversions; none are built in.
caseSensitivebooleanno

Example request body

{
  "items": [
    {
      "attribute": "voltage",
      "requested": {
        "op": "gte",
        "value": "24",
        "unit": "V"
      },
      "quoted": {
        "value": "24",
        "unit": "V"
      }
    },
    {
      "attribute": "length",
      "requested": {
        "op": "eq",
        "value": "100",
        "unit": "mm",
        "tolerance": "0.5"
      },
      "quoted": {
        "value": "10.2",
        "unit": "cm"
      }
    },
    {
      "attribute": "finish",
      "requested": {
        "op": "in",
        "values": [
          "anodized",
          "powder coat"
        ]
      },
      "quoted": {
        "value": "Anodised"
      }
    },
    {
      "attribute": "ip-rating",
      "requested": {
        "op": "present"
      }
    }
  ],
  "conversions": [
    {
      "from": "cm",
      "to": "mm",
      "factor": "10"
    }
  ]
}

Result

The response is { "data": ..., "_provenance": ... }. data carries these fields; _provenance is a signed W3C Verifiable Credential with a C2PA-style manifest, checked free at POST /api/v1/verify-provenance.

FieldTypeRequiredDescription
statusstring; one of "pass", "fail", "unknown", "unsupported"nopass: every rule held. fail: a rule was violated (see witnesses). unknown: the input lacks the evidence to decide. unsupported: outside what this engine covers. Missing evidence is never a pass.
itemsarray<object>no
countsobjectno
witnessesarray<object>no
versionsobjectnoEvery semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile).
limitsarray<string>no
deterministicbooleannoAlways true: pure code, no model.

Pay and connect

Available through: x402 (USDC on Base), MCP. MCP clients reach it through the money-math-kit package.

Machine-readable