The Assumption Conflict API from WritersLogic Verifiable AI Agent Hub — 1 operation(s) for assumption conflict.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/writerslogic-com:writerslogic-com-assumption-conflict-api"curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: WritersLogic Verifiable AI Agent Hub Assumption Conflict API
version: 2.0.0
description: Pay-per-call agents settled in USDC on Base via x402. Every response carries a signed provenance envelope.
contact:
name: WritersLogic
url: https://writerslogic.com/agents
email: agents@writerslogic.com
servers:
- url: https://agents.writerslogic.com
tags:
- name: Assumption Conflict
paths:
/api/v1/assumption-conflict:
post:
operationId: assumption_conflict
summary: Find assumptions that disagree across agents (currency, timezone, version…
description: '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.
Price: 0.005 USDC on Base (x402).'
x-x402-price-usdc: '0.005'
x-x402-amount: '5000'
x-payment-info:
protocols:
- x402
price:
mode: fixed
currency: USD
amount: '0.005'
x-audience: agent-infra
x-sample-url: https://agents.writerslogic.com/api/v1/samples/assumption-conflict
security:
- x402: []
- apiKey: []
requestBody:
required: true
content:
application/json:
schema:
type: object
additionalProperties: false
required:
- assumptions
properties:
assumptions:
type: array
minItems: 1
maxItems: 500
items:
type: object
additionalProperties: false
required:
- agent
- key
- value
properties:
agent:
type: string
minLength: 1
maxLength: 200
key:
type: string
minLength: 1
maxLength: 200
value:
description: String (≤ 200 chars), number or boolean.
requiredKeys:
type: array
maxItems: 50
items:
type: string
minLength: 1
maxLength: 200
description: Keys every listed agent must state.
agents:
type: array
maxItems: 50
items:
type: string
minLength: 1
maxLength: 200
description: Agents expected to state the required keys.
example:
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
responses:
'200':
description: Paid result with provenance
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
status:
type: string
enum:
- pass
- fail
- unknown
- unsupported
description: '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:
type: array
items:
type: object
properties:
key:
type: string
kind:
type: string
enum:
- substantive
- formatting
values:
type: array
items:
type: object
properties:
agent:
type: string
value: {}
missing:
type: array
items:
type: object
properties:
agent:
type: string
key:
type: string
agreedKeys:
type: array
items:
type: string
witnesses:
type: array
items:
type: object
properties:
ruleId:
type: string
detail:
type: string
path:
type: string
description: JSON pointer or dotted path into the input.
offset:
type: integer
index:
type: integer
expected:
description: What the rule required.
actual:
description: What the input had.
versions:
type: object
description: Every semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile).
limits:
type: array
items:
type: string
deterministic:
type: boolean
description: 'Always true: pure code, no model.'
_provenance:
type: object
description: C2PA-aligned manifest and W3C VC 2.0 (eddsa-jcs-2022) issued by the hub DID; verify at POST /api/v1/verify-provenance
required:
- data
- _provenance
'400':
description: Invalid request (no payment consumed)
content:
application/json:
schema:
type: object
properties:
error:
type: string
code:
type: string
'401':
description: Invalid X-API-KEY
content:
application/json:
schema:
type: object
properties:
error:
type: string
code:
type: string
'402':
description: Payment required or invalid
content:
application/json:
schema:
type: object
description: x402 v2 PaymentRequired (also base64 in the PAYMENT-REQUIRED header)
properties:
x402Version:
type: integer
error:
type: string
code:
type: string
resource:
type: object
accepts:
type: array
items:
type: object
extensions:
type: object
'502':
description: Upstream failure; the payment is released or not settled
content:
application/json:
schema:
type: object
properties:
error:
type: string
code:
type: string
tags:
- Assumption Conflict
components:
securitySchemes:
x402:
type: apiKey
in: header
name: PAYMENT-SIGNATURE
description: x402 v2 payment payload (base64) sent after a 402 challenge
apiKey:
type: apiKey
in: header
name: X-API-KEY