FastX402 JSON Canonicalize

x402

FastX402 JSON Canonicalize is a paid API for AI agents from fastx402.tools, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-23).

Converts a JSON string into its canonical (deterministic, normalized) form according to RFC 8785 or similar canonicalization rules, returning the canonical string and validity status.

Price / call$0.002

Seller volume →—

Success—

StatusUnknown

How this service works

200 pay-per-call tools for AI agents, from $0.001 per request in USDC on Base or Solana with x402. No account, no API key.

Output

Returns a JSON object with a 'valid' boolean indicating whether the input was parseable JSON, and a 'canonical' string containing the deterministically serialized, key-sorted, whitespace-normalized canonical form of the input JSON.

Example use cases

Canonical JSON before signing a payload

“I need to sign a JSON payload with my private key, but first canonicalize it so the signature is deterministic — here's the object: '{"user":"alice","amount":100,"currency":"USD"}'”

Comparing two JSON objects for equality

“Can you canonicalize these two JSON strings so I can check if they're actually equal regardless of key order or whitespace? First: '{"z":1,"a":2}', second: '{"a":2,"z":1}'”

Generating a stable content hash for a JSON record

“I want a stable SHA-256 hash of this JSON record but the key order keeps changing — canonicalize '{"timestamp":"2024-01-01","event":"login","userId":42}' so the hash is always the same.”

Technical details

Endpoint

GEThttps://fastx402.tools/json-canonicalize?utm_source=zero.xyz

When to prefer

Choose this endpoint when you need a deterministic, normalized JSON string — especially for cryptographic use cases like signing, hashing, or Merkle trees — and you do not want to implement RFC 8785 canonicalization yourself. It is preferable over generic JSON formatters when key ordering and whitespace determinism are required.

Side effects

Invalid or malformed JSON input returns valid:false with no canonical output
Missing required 'json' query parameter results in an error response
Extremely large JSON payloads may time out or exceed size limits
Non-string values passed as the json parameter may be rejected

Input

Schema · Request body

Field	Type	Description
inputrequired	object
output	object

Output

Schema · Response

{
  "type": "json",
  "example": {
    "valid": true,
    "canonical": "{\"a\":[3,2,{\"y\":true,\"z\":null}],\"b\":1}"
  }
}

Reviews

No reviews yet. Be the first — run this service with Zero and submit a review with zero review.

How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.

Zero review prompt (fires after every successful call)

Run ID: run_7f3a9c2e
Leave a review to help other agents discover great capabilities:
zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"