passabsent from every registry#7 by calls of 15 on this host
0.15 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-04 21:22 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 50% / 50%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-04 08:30 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.15 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 2 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
Among the 15 endpoints on api.zfinia.com, json patch safety audit is tied 7th by calls with 9 others.
json patch safety audit takes a json body with the fields patch, document and protected_paths.
A response from json patch safety audit, as declared, includes limits, passed, complete, findings, operations, request_id and 2 others.
json patch safety audit drew a single call from a single payer in the trailing 30 days.
The last call to json patch safety audit came 9 days before the snapshot, 2026-10-04.
Each call is priced at 0.15 USDC, payable on Base.
json patch safety audit takes 4% of the calls counted across api.zfinia.com.
api.zfinia.com serves json patch safety audit, a POST endpoint that TOLL places in the "other" category, listed in neither registry at the last pull.
json patch safety audit answered the sweep of 2026-10-04 with a valid 402, passing 1 of 2 sweeps since 2026-10-04.
Closest in price to json patch safety audit within the "other" category: tiers prototype at api.run402.com and research newsfeed at win.oneshotagent.com.
json patch safety audit is near the top of prices in the "other" category; 97% of comparable listings are cheaper.
The wallet paid by json patch safety audit is the payee of 179 endpoints across 5 hosts.
Seller tags: json patch, configuration validation, api contracts and developer tooling.
json patch safety audit was missing from the Coinbase registry at the pull of 2026-10-05, confirmed at the pull of 2026-10-05; that is registry presence, not liveness.
Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.
the payment options, as of 2026-10-04 21:22 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.15 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-04 12:59 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-04 12:59 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-04 12:25 UTC | fail | 1 | new-after-daily-2026-10-04 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-04 08:30 UTC · method
The input and output block
{
"input": {
"body": {
"patch": "[{\"op\":\"remove\",\"path\":\"/limits\"},{\"op\":\"replace\",\"path\":\"/replicas\",\"value\":\"three\"},{\"op\":\"replace\",\"path\":\"/limits/cpu\",\"value\":\"500m\"},{\"op\":\"add\",\"path\":\"/hosts/-\",\"value\":\"c.test\"},{\"op\":\"move\",\"from\":\"/hosts\",\"path\":\"/hosts/0\"},{\"op\":\"remove\",\"path\":\"/name\"}]",
"document": "{\"name\":\"service\",\"replicas\":3,\"limits\":{\"cpu\":\"200m\",\"memory\":\"256Mi\"},\"hosts\":[\"a.test\",\"b.test\"]}",
"protected_paths": [
"/name"
]
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"limits": {
"maxFindings": 500,
"maxJsonBytes": 1048576,
"maxResources": 5000,
"maxTextBytes": 262144,
"maxEnvEntries": 2000,
"maxPatchOperations": 1000
},
"passed": false,
"complete": false,
"findings": [
{
"code": "VALUE_REMOVED",
"path": "/limits",
"detail": "patch[0] removes /limits, which holds 2 member(s). A patch has no inverse, so this is not undone by re-applying.",
"operation": "patch[0]"
},
{
"code": "REPLACE_CHANGES_TYPE",
"path": "/replicas",
"detail": "patch[1] replaces /replicas, which is number, with string. Anything reading that path with a type expectation breaks.",
"operation": "patch[1]"
},
{
"code": "TARGET_DOES_NOT_EXIST",
"path": "/limits/cpu",
"detail": "patch[2] replaces /limits/cpu and nothing is there at this point in the sequence, so applying the patch fails.",
"operation": "patch[2]"
}
],
"operations": [
{
"op": "remove",
"path": "/limits",
"operation": "patch[0]",
"target_existed": true
},
{
"op": "replace",
"path": "/replicas",
"operation": "patch[1]",
"target_existed": true
},
{
"op": "replace",
"path": "/limits/cpu",
"operation": "patch[2]",
"target_existed": false
}
],
"request_id": "example-request",
"service_id": "json_patch_safety_audit",
"assumptions": [
"The patch is applied to a copy as a sequence, so each operation is judged against the state it will actually see. Checking each one against the original document would miss the whole class of defect w...",
"RFC 6902 requires the target of remove, replace, move and copy to exist, so a missing target is reported as the patch failing rather than as doing nothing.",
"A fingerprint of the resulting document is returned so a caller can confirm the result matches what they expect without the result being echoed back."
],
"limitations": [
"The patch and the document supplied. Whether the resulting document is correct for its consumer is outside this.",
"safe_to_apply is true only when every operation applies and none of them removes or retypes existing data."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"not_examined": [
"NO_TEST_OPERATION: The patch contains no test operation, so it will apply to a document in any state. A test is how a patch refuses to apply to a document it was not written against."
],
"finding_count": 6,
"safe_to_apply": false,
"operation_count": 6,
"service_version": "1.0.0",
"findings_by_code": {
"VALUE_REMOVED": 2,
"MOVE_INTO_ITSELF": 1,
"REPLACE_CHANGES_TYPE": 1,
"TARGET_DOES_NOT_EXIST": 1,
"PROTECTED_PATH_MODIFIED": 1
},
"result_fingerprint": {
"sha256": "86e5785b5a4b56dbd848528a323325b44ddf5611b267a762e971e7a84d3c1f8f"
},
"declares_test_operation": false,
"destructive_operation_count": 3
}
}
}Cite this page
This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "json patch safety audit on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-json-patch-safety-audit-2f30b2. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-json-patch-safety-audit-2f30b2-2026-10-13,
author = {TOLL},
title = {json patch safety audit on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-json-patch-safety-audit-2f30b2}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.