ToolVet
41trust / 100

Json Canonicalize

by JSON Canonicalizer in Other

x402 APIFailing, checked 22 h ago

JSON canonicalization — canonicalize structured data with RFC 8785 JCS; return canonical JSON text, UTF-8 byte length and SHA-256 hash for integrity checks, signature preparation and deduplication. Uses binary64 rounding and strict Unicode/duplicate-key checks; rejects negative zero, overflow and nonzero underflow.

POST
https://data-tools.use.x402atlas.com/json-canonicalize
Price
$0.01
per call in USDC
Uptime
80.4%
last 30 days
Response time
452 ms
546 ms slowest 5%
Last check
Failed
22 h ago, next in 45 h

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 22 h ago: Connection failed (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR)

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://data-tools.use.x402atlas.com/json-canonicalize

Each call costs $0.01 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://data-tools.use.x402atlas.com/json-canonicalize
content-type: application/json

{
  "value": {
    "literals": [
      null,
      true,
      false
    ],
    "numbers": [
      333333333.3333333,
      1e+30,
      4.5,
      0.002,
      1e-27
    ],
    "string": "€$\u000f\nA'B\"\\\\\"/"
  }
}

Parameters

ParameterTypeRequiredDescription
valueobject or array or string or number or boolean or nullYesJSON value to canonicalize, <=50000 nodes; JCS rejects negative zero, overflow and nonzero underflow and uses binary64 rounding; unique decoded keys, valid Unicode, depth <=64, finite JSON numeric tokens <=1024 bytes and exponent magnitude <=4096

Example response

The provider's example. We can't check it without paying.

{
  "algorithm_version": "rfc8785-jcs-v1",
  "canonical_json": "{\"literals\":[null,true,false],\"numbers\":[333333333.3333333,1e+30,4.5,0.002,1e-27],\"string\":\"€$\\u000f\\nA'B\\\"\\\\\\\\\\\"/\"}",
  "input": {
    "node_count": 12
  },
  "operation": "json-canonicalize",
  "sha256": "2d5e01a318d0f0879ab568c4be289c8b1f64ef8921a53c6277d5e069978baacb",
  "utf8_bytes": 118,
  "warnings": []
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://data-tools.use.x402atlas.com/json-canonicalize' \
  -H 'content-type: application/json' \
  --data-raw '{"value":{"literals":[null,true,false],"numbers":[333333333.3333333,1e+30,4.5,0.002,1e-27],"string":"\u20ac$\u000f\nA'\''B\"\\\\\"/"}}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://data-tools.use.x402atlas.com/json-canonicalize' \
  -H 'content-type: application/json' \
  --data-raw '{"value":{"literals":[null,true,false],"numbers":[333333333.3333333,1e+30,4.5,0.002,1e-27],"string":"\u20ac$\u000f\nA'\''B\"\\\\\"/"}}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fdata-tools.use.x402atlas.com%2Fjson-canonicalize&method=POST
const res = await pay("https://data-tools.use.x402atlas.com/json-canonicalize", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "value": {
      "literals": [
        null,
        true,
        false
      ],
      "numbers": [
        333333333.3333333,
        1e+30,
        4.5,
        0.002,
        1e-27
      ],
      "string": "\u20ac$\u000f\nA'B\"\\\\\"/"
    }
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://data-tools.use.x402atlas.com/json-canonicalize",
        json={
            "value": {
                "literals": [
                    None,
                    True,
                    False,
                ],
                "numbers": [
                    333333333.3333333,
                    1e+30,
                    4.5,
                    0.002,
                    1e-27,
                ],
                "string": "\u20ac$\u000f\nA'B\"\\\\\"/",
            },
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
22 h agoConnection failed (ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR)---
4 days agoExpected HTTP 402, got 404404426 ms-
5 days agoExpected HTTP 402, got 404404496 ms-
6 days agoExpected HTTP 402, got 404404424 ms-
7 days agoExpected HTTP 402, got 404404409 ms-
Show 10 older checks
8 days agoExpected HTTP 402, got 404404381 ms-
8 days agoExpected HTTP 402, got 404404599 ms-
8 days agoExpected HTTP 402, got 404404424 ms-
8 days agoExpected HTTP 402, got 404404506 ms-
8 days agoExpected HTTP 402, got 404404431 ms-
8 days agoExpected HTTP 402, got 404404433 ms-
8 days agoPassed402433 ms$0.01
9 days agoPassed402372 ms$0.01
9 days agoPassed402463 ms$0.01
9 days agoPassed402463 ms$0.01