passabsent from every registry#7 by calls of 15 on this host
0.16 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:39 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.16 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, accrual cutoff audit is tied 7th by calls with 9 others.
accrual cutoff audit takes a json body with the fields entries, grace_days and period_end.
A response from accrual cutoff audit, as declared, includes limits, passed, entries, complete, findings, consistent and 2 others.
accrual cutoff audit drew a single call from a single payer in the trailing 30 days.
The last call to accrual cutoff audit came 9 days before the snapshot, 2026-10-04.
Each call is priced at 0.16 USDC, payable on Base.
accrual cutoff audit takes 4% of the calls counted across api.zfinia.com.
api.zfinia.com serves accrual cutoff audit, a POST endpoint that TOLL places in the "other" category, listed in neither registry at the last pull.
accrual cutoff audit answered the sweep of 2026-10-04 with a valid 402, as at every sweep since 2026-10-04.
Closest in price to accrual cutoff audit within the "other" category: tiers prototype at api.run402.com and research newsfeed at win.oneshotagent.com.
accrual cutoff audit is near the top of prices in the "other" category; 97% of comparable listings are cheaper.
The wallet paid by accrual cutoff audit is the payee of 179 endpoints across 5 hosts.
Seller tags: period close, accruals, accounting and exact arithmetic.
accrual cutoff 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.16 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-04 12:58 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:58 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-04 12:25 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:39 UTC · method
The input and output block
{
"input": {
"body": {
"entries": [
{
"id": "EXP-1",
"amount": "400.00",
"posted_on": "2026-09-28",
"service_on": "2026-09-25"
},
{
"id": "EXP-2",
"amount": "1250.00",
"posted_on": "2026-10-03",
"service_on": "2026-09-29"
},
{
"id": "EXP-3",
"amount": "3100.50",
"posted_on": "2026-10-21",
"service_on": "2026-09-15"
},
{
"id": "EXP-4",
"amount": "900.00",
"posted_on": "2026-09-29",
"service_on": "2026-10-15"
},
{
"id": "EXP-5",
"amount": "75.00",
"posted_on": "2026-09-30"
}
],
"grace_days": 5,
"period_end": "2026-09-30"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"limits": {
"maxEntries": 20000,
"maxAccounts": 5000,
"maxFindings": 500,
"maxLinesPerEntry": 500,
"maxStatementLines": 20000
},
"passed": false,
"entries": [
{
"entry": "EXP-1",
"amount": "400",
"in_period": true,
"posted_on": "2026-09-28",
"service_on": "2026-09-25"
},
{
"entry": "EXP-2",
"amount": "1250",
"in_period": true,
"posted_on": "2026-10-03",
"service_on": "2026-09-29"
},
{
"entry": "EXP-3",
"amount": "3100.5",
"in_period": true,
"posted_on": "2026-10-21",
"service_on": "2026-09-15"
}
],
"complete": true,
"findings": [
{
"code": "POSTED_AFTER_CUTOFF_WITHIN_GRACE",
"entry": "EXP-2",
"detail": "EXP-2 is for service on 2026-09-29, before the 2026-09-30 cutoff, and was posted on 2026-10-03, after it. 1250 belongs to the period and is not in it unless an accrual puts it there. This is inside th..."
},
{
"code": "POSTED_AFTER_CUTOFF",
"entry": "EXP-3",
"detail": "EXP-3 is for service on 2026-09-15, before the 2026-09-30 cutoff, and was posted on 2026-10-21, after it. 3100.5 belongs to the period and is not in it unless an accrual puts it there."
},
{
"code": "POSTED_BEFORE_SERVICE",
"entry": "EXP-4",
"detail": "EXP-4 was posted on 2026-09-29, inside the period, for service on 2026-10-15, after it. 900 is in the period and does not belong to it unless a prepayment takes it out."
}
],
"consistent": false,
"grace_days": 5,
"period_end": "2026-09-30",
"request_id": "example-request",
"service_id": "accrual_cutoff_audit",
"assumptions": [
"The service date decides which period an entry belongs to and the posting date decides which period it landed in. Comparing the two is the whole check, and an entry with no service date is reported as...",
"Both directions are reported: work done before the cutoff and posted after understates the period, and an amount posted inside the period for later service overstates it. Those are different correctio...",
"The total in the wrong period is summed exactly and published, since that figure is what a cutoff review is looking for."
],
"entry_count": 5,
"limitations": [
"Whether the dates supplied put each amount in the period its service date implies. Not accounting advice and not an audit opinion: whether an accrual is required, how it should be measured, and what p...",
"consistent is true only when every entry had a service date and every one of them was posted in the period its service date implies."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"not_examined": [],
"finding_count": 4,
"in_period_total": "4750.5",
"misstated_total": "5250.5",
"service_version": "1.0.0",
"findings_by_code": {
"POSTED_AFTER_CUTOFF": 1,
"SERVICE_DATE_ABSENT": 1,
"POSTED_BEFORE_SERVICE": 1,
"POSTED_AFTER_CUTOFF_WITHIN_GRACE": 1
},
"after_period_total": "900",
"misstated_as_number": 5250.5
}
}
}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, "accrual cutoff audit on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-accrual-cutoff-audit-2e43e1. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-accrual-cutoff-audit-2e43e1-2026-10-13,
author = {TOLL},
title = {accrual cutoff audit on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-accrual-cutoff-audit-2e43e1}},
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.