passabsent from every registry#5 by calls of 7 on this host
0.02 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-02 22:12 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-09-02 22:27 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.02 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 91 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.
answerpool.io serves regs cfr, a GET endpoint that TOLL places in the "other" category, listed in neither registry at the last pull.
On Base, regs cfr asks 0.02 USDC per call.
Its declared inputs are the query parameters cfr_part and cfr_title.
regs cfr returns json; the example shows as_of, count, documents and total_matching.
regs cfr answered the sweep of 2026-10-03 with a valid 402, as at every sweep since 2026-09-11.
answerpool.io lists 7 endpoints; regs cfr is tied 5th by calls with 3 others.
regs cfr takes 9% of the calls counted across answerpool.io.
In the trailing 30 days: one call, one payer.
regs cfr was last called 39 days before the snapshot.
Closest in price to regs cfr within the "other" category: business time at chrono.schemasure.com and exchange rate at api.strale.io.
regs cfr is priced above 84% of comparable listings in the "other" category.
The wallet paid by regs cfr is the payee of 60 endpoints on one host.
The seller's tags on regs cfr are regulation, cfr, watch and compliance.
regs cfr was missing from the Coinbase registry at the pull of 2026-10-03, confirmed at the pull of 2026-10-03; that is registry presence, not liveness.
The price of regs cfr is declared by 165 other listings in the "other" category too.
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-02 22:12 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.02 USDC | exact | 0xb3ba3C…9AED8c |
the checks, as of 2026-10-03 04:03 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-03 04:03 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 13:12 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 06:28 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 05:46 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 18:07 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 04:00 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-25 19:42 UTC | pass | 0 | daily-2026-09-25 |
| 2026-09-23 05:24 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 05:34 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 05:57 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-20 18:36 UTC | pass | 0 | daily-2026-09-20 |
| 2026-09-19 03:59 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-18 08:51 UTC | pass | 0 | daily-2026-09-18 |
| 2026-09-17 03:58 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 03:58 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 03:57 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 03:56 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 03:56 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 06:11 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 09:36 UTC | pass | 0 | daily-2026-09-11 |
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-09-02 22:27 UTC · method
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"cfr_part": 240,
"cfr_title": 17
}
},
"output": {
"type": "json",
"example": {
"as_of": "2026-09-02T14:00:00Z",
"count": 1,
"documents": [
{
"url": "https://www.federalregister.gov/d/2026-12341",
"type": "Rule",
"flags": [
"significant",
"effective_soon",
"final_rule_pending_effect"
],
"title": "Cybersecurity Risk Management Rule",
"action": "Final rule.",
"topics": [
"Securities"
],
"abstract": "Requires registrants to disclose material cybersecurity incidents.",
"agencies": [
"Securities and Exchange Commission"
],
"docket_ids": [
"SEC-2026-001"
],
"significant": true,
"effective_on": "2026-09-12",
"cfr_references": [
"17 CFR 240"
],
"document_number": "2026-12341",
"publication_date": "2026-08-30",
"comments_close_on": null,
"days_to_effective": 10,
"days_to_comment_close": null,
"regulation_id_numbers": [
"3235-AN00"
]
}
],
"total_matching": 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, "regs cfr on answerpool.io". https://tollindex.com/e/answerpool-io-v1-regs-cfr-0e91e7. Accessed [access date].
BibTeX
@misc{toll-e-answerpool-io-v1-regs-cfr-0e91e7-2026-10-12,
author = {TOLL},
title = {regs cfr on answerpool.io},
howpublished = {\url{https://tollindex.com/e/answerpool-io-v1-regs-cfr-0e91e7}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-12 05:54 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.