passabsent from every registry#7 by calls of 15 on this host
0.2 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-08 13:26 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 83% / 83%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-04 08:38 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.2 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 12 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.
revenue recognition schedule audit is one of 15 listed endpoints on api.zfinia.com, tied 7th by calls with 9 others among them.
revenue recognition schedule audit takes a json body with the fields periods, currency, term_end, term_start and contract_value.
A response from revenue recognition schedule audit, as declared, includes limits, passed, periods, complete, currency, findings and 2 others.
revenue recognition schedule audit drew a single call from a single payer in the trailing 30 days.
The last call to revenue recognition schedule audit came 9 days before the snapshot, 2026-10-04.
On Base, revenue recognition schedule audit asks 0.2 USDC per call.
It accounts for 4% of the calls counted across the host.
TOLL files revenue recognition schedule audit under the "other" category: a POST endpoint on api.zfinia.com, listed in neither registry at the last pull.
revenue recognition schedule audit answered the sweep of 2026-10-08 with a valid 402, passing 5 of 6 sweeps since 2026-10-04.
Closest in price to revenue recognition schedule audit within the "other" category: intelligence address at api.arkm.com and services vulnerability audit at www.cultos.dev.
revenue recognition schedule audit is near the top of prices in the "other" category; 98% of comparable listings are cheaper.
The wallet paid by revenue recognition schedule audit is the payee of 179 endpoints across 5 hosts.
Seller tags: revenue recognition, accounting, exact arithmetic and contracts.
revenue recognition schedule audit was missing from the Coinbase registry at the pull of 2026-10-08, confirmed at the pull of 2026-10-09; 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-08 13:26 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.2 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-08 11:25 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-08 11:25 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 10:46 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 11:29 UTC | fail | 1 | daily-2026-10-06 |
| 2026-10-05 10:13 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 13:13 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-04 12:42 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:38 UTC · method
The input and output block
{
"input": {
"body": {
"periods": [
{
"end": "2026-02-28",
"label": "Q1",
"start": "2026-01-02",
"amount": "2000.00"
},
{
"end": "2026-06-30",
"label": "Q2",
"start": "2026-04-01",
"amount": "3000.00"
},
{
"end": "2026-09-30",
"label": "Q3",
"start": "2026-06-30",
"amount": "3000.00"
},
{
"end": "2026-12-31",
"label": "Q4",
"start": "2026-10-01",
"amount": "3999.99"
}
],
"currency": "EUR",
"term_end": "2026-12-31",
"term_start": "2026-01-01",
"contract_value": "12000.00"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"limits": {
"maxEntries": 20000,
"maxAccounts": 5000,
"maxFindings": 500,
"maxLinesPerEntry": 500,
"maxStatementLines": 20000
},
"passed": false,
"periods": [
{
"end": "2026-02-28",
"label": "Q1",
"start": "2026-01-02",
"amount": "2000"
},
{
"end": "2026-06-30",
"label": "Q2",
"start": "2026-04-01",
"amount": "3000"
},
{
"end": "2026-09-30",
"label": "Q3",
"start": "2026-06-30",
"amount": "3000"
}
],
"complete": true,
"currency": "EUR",
"findings": [
{
"code": "SCHEDULE_DOES_NOT_SUM_TO_CONTRACT_VALUE",
"detail": "The periods total 11999.99 against a contract value of 12000, out by exactly -0.01. That amount is never recognised."
},
{
"code": "GAP_BETWEEN_PERIODS",
"detail": "Nothing is recognised between 2026-03-01 and 2026-03-31, so that stretch of the term carries no revenue.",
"period": "Q2"
},
{
"code": "PERIODS_OVERLAP",
"detail": "The period beginning 2026-06-30 overlaps the one ending 2026-06-30, so the overlap is recognised twice.",
"period": "Q3"
}
],
"term_end": "2026-12-31",
"consistent": false,
"difference": "-0.01",
"request_id": "example-request",
"service_id": "revenue_recognition_schedule_audit",
"term_start": "2026-01-01",
"assumptions": [
"The schedule must sum to the contract value exactly. A cent either way means that amount is either never recognised or recognised without having been contracted, and both are reported with the exact f...",
"Periods are treated as inclusive day ranges, so the day after one period ends is the day the next must begin. A gap and an overlap are separate findings because they are opposite errors.",
"Periods are sorted by start, so the order supplied does not change the answer."
],
"limitations": [
"Whether the schedule supplied adds up and covers the term supplied. Not accounting advice: whether the pattern of recognition is appropriate, and which standard applies, are outside this.",
"consistent is true only when the schedule summed exactly, covered the term with no gap or overlap, and every amount fitted the currency."
],
"minor_units": 2,
"observed_at": "2026-10-02T00:00:00.000Z",
"not_examined": [],
"period_count": 4,
"finding_count": 4,
"contract_value": "12000",
"scheduled_total": "11999.99",
"service_version": "1.0.0",
"findings_by_code": {
"PERIODS_OVERLAP": 1,
"GAP_AT_TERM_START": 1,
"GAP_BETWEEN_PERIODS": 1,
"SCHEDULE_DOES_NOT_SUM_TO_CONTRACT_VALUE": 1
}
}
}
}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, "revenue recognition schedule audit on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-revenue-recognition-schedule-audit-a1cbcf. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-revenue-recognition-schedule-audit-a1cbcf-2026-10-13,
author = {TOLL},
title = {revenue recognition schedule audit on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-revenue-recognition-schedule-audit-a1cbcf}},
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.