Find assumptions that disagree across agents (currency, timezone, version, customer id, ...)

$0.005 USDC per call · Agent infrastructure · POST /api/v1/assumption-conflict · Id assumption-conflict

Takes assumptions that several agents or steps hold about the same fact (key, value, who) and reports every key where the values differ, naming the conflicting pairs and whether they differ only by case or whitespace (a formatting difference) or in substance (USD vs EUR, a different id, a different version). Optionally requires each listed agent to state each required key; a missing statement is unknown, not agreement. Values are compared exactly after trimming; no unit, currency or timezone conversion is attempted.

What you get

Merging agents' outputs that quietly assumed different currencies, zones or customers is how wrong totals get reported.

Call it

Send the JSON body below to https://agents.writerslogic.com/api/v1/assumption-conflict. 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/assumption-conflict \
  -H 'content-type: application/json' \
  -d '{"assumptions":[{"agent":"pricing","key":"currency","value":"USD"},{"agent":"tax","key":"currency","value":"EUR"},{"agent":"pricing","key":"tz","value":"Europe/Berlin"},{"agent":"tax","key":"tz","value":"Europe/Berlin"}]}'

Input

Field	Type	Required	Description
`assumptions`	array<object>; max 500 items	yes
`requiredKeys`	array<string; length 1..200>; max 50 items	no	Keys every listed agent must state.
`agents`	array<string; length 1..200>; max 50 items	no	Agents expected to state the required keys.

Example request body

{
  "assumptions": [
    {
      "agent": "pricing",
      "key": "currency",
      "value": "USD"
    },
    {
      "agent": "tax",
      "key": "currency",
      "value": "EUR"
    },
    {
      "agent": "pricing",
      "key": "tz",
      "value": "Europe/Berlin"
    },
    {
      "agent": "tax",
      "key": "tz",
      "value": "Europe/Berlin"
    }
  ]
}

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.

Field	Type	Required	Description
`status`	string; one of "pass", "fail", "unknown", "unsupported"	no	pass: 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.
`conflicts`	array<object>	no
`missing`	array<object>	no
`agreedKeys`	array<string>	no
`witnesses`	array<object>	no
`versions`	object	no	Every semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile).
`limits`	array<string>	no
`deterministic`	boolean	no	Always true: pure code, no model.

Pay and connect

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

Machine-readable

This agent as JSON (schemas, example, OpenAPI operation)
Free signed sample response
OpenAPI 3.1 · Catalog · Index of every agent