561 Group Market

RFC 6902 JSON Patch Applicability

Check whether a supplied RFC 6902 patch applies sequentially to supplied JSON. An inapplicable patch is a paid diagnostic result with its zero-based failing operation and rule; original data stays untouched. Resource-limit excess is refused before payment. Ordinary finite JSON, valid Unicode; 64 KiB canonical request/result, depth 64, 8192 nodes, 4096 array elements.

Price
from $0.0012 USDC per request (starting price; the 402 response quotes the exact amount for your input)
Network
Base mainnet, eip155:8453, settled in USDC through the Coinbase CDP facilitator
Method and URL
POST https://market.561.group/v1/data/json-patch-check
Response type
application/json
Seller
Causeway Services (561 Group)

Input contract

Input that fails this contract is refused with a 4xx status before any payment is requested.

{
  "maxBytes": 1048576,
  "bodySchema": {
    "type": "object",
    "additionalProperties": false,
    "properties": {
      "value": {},
      "patch": {}
    },
    "required": [
      "value",
      "patch"
    ]
  }
}

Example request

{
  "method": "POST",
  "url": "https://market.561.group/v1/data/json-patch-check",
  "headers": {
    "accept": "application/json",
    "content-type": "application/json"
  },
  "body": {
    "value": {
      "count": 1
    },
    "patch": [
      {
        "op": "test",
        "path": "/count",
        "value": 2
      }
    ]
  }
}

Output

{
  "schema": {
    "type": "object",
    "required": [
      "applicable"
    ],
    "additionalProperties": false,
    "properties": {
      "applicable": {
        "type": "boolean"
      },
      "operations": {
        "type": "integer",
        "minimum": 0,
        "maximum": 128,
        "description": "Present on an applicable patch."
      },
      "present": {
        "type": "boolean",
        "description": "Final document presence on an applicable patch."
      },
      "error": {
        "type": "object",
        "required": [
          "code",
          "message"
        ],
        "properties": {
          "code": {
            "type": "string"
          },
          "message": {
            "type": "string"
          },
          "operation": {
            "type": "integer",
            "minimum": 0,
            "maximum": 127,
            "description": "Zero-based failing operation, when failure is associated with an operation."
          }
        }
      }
    }
  },
  "example": {
    "applicable": false,
    "error": {
      "code": "test-failed",
      "message": "target does not equal the test value",
      "operation": 0
    }
  }
}

How to buy with x402

  1. Send the request without payment. The server answers 402 Payment Required with a base64 JSON PAYMENT-REQUIRED header holding the amount, asset, network and payee.
  2. Have your wallet sign an EIP-3009 transferWithAuthorization for exactly those terms (an x402 client library does this for you).
  3. Repeat the identical request with the signed payload in the PAYMENT-SIGNATURE header.
  4. The server verifies, runs the operation, settles, and returns 200 with the result and a PAYMENT-RESPONSE header carrying the settlement receipt.

Read the price without paying

curl --include --request POST --header 'accept: application/json' --header 'content-type: application/json' --data-raw '{"value":{"count":1},"patch":[{"op":"test","path":"/count","value":2}]}' --url 'https://market.561.group/v1/data/json-patch-check'

This request authorizes nothing; it returns the live payment terms. Read the full explanation of x402.

Machine-readable