failabsent from every registrycounted above 0% of Search
0.003 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 05:50 UTC · method
- Validation state
- fail
- Uptime, 7 / 30 / 90 days
- — / 0% / 0%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-04 14:32 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.003 USDC
- Networks
- 3
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 96 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.
forecast answered HTTP 400 rather than 402 at the sweep of 2026-10-04; the recorded state is fail.
At weather.agentic-jp.com, forecast takes GET requests, is listed in neither registry at the last pull, and falls under search by TOLL's rules.
forecast is priced at 0.003 USDC on Base.
Requests carry the path parameter area.
forecast accepts payment on Base, Polygon and Solana, 3 options in all, to 2 different wallets.
A response from forecast, as declared, includes area, daily, weekly, summary_en, summary_ja, report_datetime and 1 other.
forecast drew a single call from a single payer in the trailing 30 days.
The last call to forecast came 58 days before the snapshot, 2026-09-04.
weather.agentic-jp.com lists no other endpoint.
forecast is priced above 21% of comparable listings in search.
Closest in price to forecast within search: pm search at api.sitecheck-api.workers.dev and search at api.agentstools.dev.
The wallet paid by forecast is the payee of 25 endpoints across 7 hosts.
forecast was missing from the Coinbase registry at the pull of 2026-10-04, confirmed at the pull of 2026-10-04; that is registry presence, not liveness.
The price of forecast is declared by 206 other listings in search 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-04 05:50 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.003 USDC | exact | 0x38c9F6…77a584 |
| Coinbase | eip155: | USDC | 0.003 USDC | exact | 0x38c9F6…77a584 |
| Coinbase | solana: | USDC | 0.003 USDC | exact | 2BTzdCAc…yBpNMk |
the checks, as of 2026-10-04 09:46 UTC · methodendpoint answered HTTP 400
returns_402· an unauthenticated request gets HTTP 402
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-04 09:46 UTC | fail | 1 | daily-2026-10-04 |
| 2026-10-03 04:48 UTC | fail | 1 | daily-2026-10-03 |
| 2026-10-02 14:02 UTC | fail | 1 | daily-2026-10-02 |
| 2026-10-01 07:07 UTC | fail | 1 | daily-2026-10-01 |
| 2026-09-30 06:24 UTC | fail | 1 | daily-2026-09-30 |
| 2026-09-29 18:44 UTC | fail | 1 | daily-2026-09-29 |
| 2026-09-28 04:35 UTC | fail | 1 | daily-2026-09-28 |
| 2026-09-25 20:18 UTC | fail | 1 | daily-2026-09-25 |
| 2026-09-23 05:57 UTC | fail | 1 | daily-2026-09-23 |
| 2026-09-22 06:07 UTC | fail | 1 | daily-2026-09-22 |
| 2026-09-21 06:30 UTC | fail | 1 | daily-2026-09-21 |
| 2026-09-20 19:09 UTC | fail | 1 | daily-2026-09-20 |
| 2026-09-19 04:31 UTC | fail | 1 | daily-2026-09-19 |
| 2026-09-18 10:21 UTC | fail | 1 | daily-2026-09-18 |
| 2026-09-17 04:28 UTC | fail | 1 | daily-2026-09-17 |
| 2026-09-16 04:29 UTC | fail | 1 | daily-2026-09-16 |
| 2026-09-15 04:27 UTC | fail | 1 | daily-2026-09-15 |
| 2026-09-14 04:23 UTC | fail | 1 | daily-2026-09-14 |
| 2026-09-13 04:22 UTC | fail | 1 | daily-2026-09-13 |
| 2026-09-12 06:38 UTC | fail | 1 | daily-2026-09-12 |
| 2026-09-11 10:09 UTC | fail | 1 | 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-07-07 14:32 UTC · method
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"pathParams": {
"area": ":area"
},
"queryParams": {}
},
"output": {
"type": "json",
"example": {
"area": {
"code": "130000",
"name": "東京都",
"name_en": "Tokyo"
},
"daily": [
{
"area": "東京地方",
"date": "2026-05-18T17:00:00+09:00",
"pops": [
0,
0,
0,
10
],
"wave": "0.5メートル",
"wind": "南の風",
"temps": [
17,
29
],
"weather": "晴れ",
"weather_en": "Clear",
"weather_code": "100"
}
],
"weekly": [
{
"pop": 20,
"date": "2026-05-19T00:00:00+09:00",
"temp_max": 27,
"temp_min": 16,
"weather_en": "Mostly clear",
"reliability": "A",
"weather_code": "101"
}
],
"summary_en": "Tokyo today: Clear. Temperatures 17-29°C. Max chance of rain 10%.",
"summary_ja": "東京都の今日の天気は晴れ。気温は17〜29℃。降水確率は最大10%。",
"report_datetime": "2026-05-18T17:00:00+09:00",
"publishing_office": "気象庁"
}
}
}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, "forecast on weather.agentic-jp.com". https://tollindex.com/e/weather-agentic-jp-com-forecast-area-38be58. Accessed [access date].
BibTeX
@misc{toll-e-weather-agentic-jp-com-forecast-area-38be58-2026-11-01,
author = {TOLL},
title = {forecast on weather.agentic-jp.com},
howpublished = {\url{https://tollindex.com/e/weather-agentic-jp-com-forecast-area-38be58}},
year = {2026},
month = {11},
note = {Frozen at its last observation, 2026-11-01 13:19 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.