trace integrity audit derived
api.zfinia.comMarket dataderived
POST https://api.zfinia.com/x402/v1/trace-integrity-audit
passabsent from every registry#6 by calls of 15 on this host
0.22 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
- — / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-04 08:32 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.22 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, trace integrity audit is tied 6th by calls with 10 others.
Callers of trace integrity audit supply a json body with the field spans.
trace integrity audit returns json; the example shows intact, limits, passed, traces, complete, findings and 2 others.
trace integrity audit drew a single call from a single payer in the trailing 30 days.
The last call to trace integrity audit came 28 days before the snapshot, 2026-10-04.
Each call is priced at 0.22 USDC, payable on Base.
trace integrity audit takes 3% of the calls counted across api.zfinia.com.
TOLL files trace integrity audit under market data: a POST endpoint on api.zfinia.com, listed in neither registry at the last pull.
trace integrity audit answered the sweep of 2026-10-04 with a valid 402, as at every sweep since 2026-10-04.
Closest in price to trace integrity audit within market data: smart money netflow at api.nansen.ai and q verdict resource at www.ax1.vc.
trace integrity audit is near the top of prices in market data; 97% of comparable listings are cheaper.
The wallet paid by trace integrity audit is the payee of 179 endpoints across 5 hosts.
Seller tags: distributed tracing, opentelemetry, data quality and observability.
trace integrity 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.22 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-04 13:00 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 13:00 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-04 12:26 UTC | pass | 0 | 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:32 UTC · method
The input and output block
{
"input": {
"body": {
"spans": "[\n {\n \"trace_id\": \"t1\",\n \"span_id\": \"a\",\n \"name\": \"GET /orders\",\n \"kind\": \"SPAN_KIND_SERVER\",\n \"start_time\": \"2026-10-02T12:00:00.000Z\",\n \"end_time\": \"2026-10-02T12:00:00.500Z\",\n \"attributes\": {\n \"http.request.method\": \"GET\",\n \"http.route\": \"/orders\"\n }\n },\n {\n \"trace_id\": \"t1\",\n \"span_id\": \"b\",\n \"parent_span_id\": \"a\",\n \"name\": \"SELECT orders\",\n \"kind\": \"SPAN_KIND_CLIENT\",\n \"start_time\": \"2026-10-02T11:59:59.960Z\",\n \"end_time\": \"2026-10-02T12:00:00.200Z\",\n \"attributes\": {}\n },\n {\n \"trace_id\": \"t1\",\n \"span_id\": \"c\",\n \"parent_span_id\": \"zz\",\n \"name\": \"cache.get\",\n \"start_time\": \"2026-10-02T12:00:00.100Z\",\n \"end_time\": \"2026-10-02T12:00:00.110Z\",\n \"attributes\": {}\n },\n {\n \"trace_id\": \"t2\",\n \"span_id\": \"d\",\n \"name\": \"GET /orders/8827341/items\",\n \"kind\": \"HTTP_SERVER\",\n \"start_time\": \"2026-10-02T12:00:01.000\",\n \"end_time\": \"2026-10-02T12:00:01.300Z\",\n \"attributes\": {\n \"http.request.method\": \"GET\"\n }\n }\n]"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"intact": false,
"limits": {
"maxLines": 20000,
"maxSpans": 10000,
"maxFields": 500,
"maxSamples": 20000,
"maxFindings": 500,
"maxJsonBytes": 2097152
},
"passed": false,
"traces": [
{
"trace": "t1",
"root_count": 1,
"span_count": 3,
"duration_ms": 540,
"orphan_count": 1
},
{
"trace": "t2",
"root_count": 1,
"span_count": 1,
"duration_ms": 300,
"orphan_count": 0
}
],
"complete": true,
"findings": [
{
"code": "TIMESTAMP_WITHOUT_OFFSET",
"span": "d",
"detail": "Span d has a start time with no UTC offset, so it is not a point in time. It was read as UTC, which is a guess."
},
{
"code": "PARENT_SPAN_NOT_IN_TRACE",
"span": "c",
"trace": "t1",
"detail": "Span c names parent zz, which is not in the data supplied. The trace renders as separate fragments rather than one tree."
},
{
"code": "CHILD_STARTS_BEFORE_PARENT",
"span": "b",
"trace": "t1",
"detail": "Span b starts 40ms before its parent a. A child cannot precede its parent, so this is clock skew between the hosts rather than a defect in the code, and every latency figure derived from it inherits t..."
}
],
"request_id": "example-request",
"service_id": "trace_integrity_audit",
"span_count": 4,
"assumptions": [
"Both snake_case and camelCase field names are read, because exporters differ and reading only one would report a well-formed trace as having no ids at all.",
"A timestamp with no UTC offset is reported rather than assumed: it is not a point in time, and assuming UTC is how a timeline comes to be hours wrong with no error anywhere. It is read as UTC so the r...",
"A child starting before its parent is reported as clock skew between hosts rather than as a code defect, because that is what it is, and a tolerance is accepted for callers who know their fleet."
],
"limitations": [
"The spans supplied. A span dropped by sampling or still in flight is not here, so a missing parent may exist upstream; the finding says it is not in the data supplied rather than that it does not exis...",
"intact is true only when every trace formed one tree, every parent resolved, and every time was coherent. Not a performance assessment."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"trace_count": 2,
"not_examined": [],
"finding_count": 3,
"service_version": "1.0.0",
"findings_by_code": {
"PARENT_SPAN_NOT_IN_TRACE": 1,
"TIMESTAMP_WITHOUT_OFFSET": 1,
"CHILD_STARTS_BEFORE_PARENT": 1
},
"clock_skew_tolerance_ms": 0
}
}
}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, "trace integrity audit on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-trace-integrity-audit-3a5c1c. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-trace-integrity-audit-3a5c1c-2026-11-01,
author = {TOLL},
title = {trace integrity audit on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-trace-integrity-audit-3a5c1c}},
year = {2026},
month = {11},
note = {Frozen at its last observation, 2026-11-01 05:59 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.