The Json Patch Conflict API from WritersLogic Verifiable AI Agent Hub — 1 operation(s) for json patch 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-json-patch-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 Json Patch 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: Json Patch Conflict
paths:
/api/v1/json-patch-conflict:
post:
operationId: json_patch_conflict
summary: Conflicts between two to four RFC 6902 JSON Patches made against the same…
description: 'Takes one base document and 2 to 4 JSON Patch (RFC 6902) operation lists written against it and reports, per pair, whether they commute: same-path writes, ancestor/descendant overlaps, array-index shifts (an insert or remove moves the elements a later patch addressed by index), concurrent `-` appends whose final order depends on application order, `test` operations invalidated by another patch, and operations that fail after the other patch ran. Each witness gives the exact JSON pointer and, for index shifts, the element the patch meant versus the element it would hit. It actually applies both orders and compares the results. For agents merging concurrent edits to one JSON document. It does not merge the patches and does not support JSON Merge Patch (RFC 7396).
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: developer
x-sample-url: https://agents.writerslogic.com/api/v1/samples/json-patch-conflict
security:
- x402: []
- apiKey: []
requestBody:
required: true
content:
application/json:
schema:
type: object
additionalProperties: false
required:
- document
- patches
properties:
document:
description: The base document both patches were written against (any JSON value).
patches:
type: array
minItems: 2
maxItems: 4
items:
type: object
properties:
name:
type: string
maxLength: 80
ops:
type: array
maxItems: 100
items:
description: 'A JSON Patch operation object: {op, path, value?, from?}.'
required:
- ops
additionalProperties: false
example:
document:
tags:
- a
- b
- c
title: x
patches:
- name: editor-1
ops:
- op: add
path: /tags/0
value: new
- name: editor-2
ops:
- op: replace
path: /tags/1
value: B
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.'
patches:
type: array
items:
type: object
properties:
name:
type: string
operations:
type: integer
appliesToBase:
type: boolean
failure:
anyOf:
- type: object
properties:
opIndex:
type: integer
reason:
type: string
path:
type: string
- type: 'null'
pairs:
type: array
items:
type: object
properties:
a:
type: string
b:
type: string
commutes:
type: boolean
description: True when both orders apply and produce the same document.
firstDifference:
anyOf:
- type: string
description: JSON pointer of the first place the two orders disagree.
- type: 'null'
conflicts:
type: array
items:
type: object
properties:
rule:
type: string
path:
type: string
detail:
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:
- Json Patch 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