context why moving derived
x402.deepsearch.comMarket dataderived
GET https://x402.deepsearch.com/v1/context/why-moving/:ticker
passabsent from every registry#4 by calls of 4 on this host
0.1 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-13 14:08 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-01 06:22 UTC
- First observed by TOLLderived
- 2026-10-01
- Pricederived
- 0.1 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 36 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.
At x402.deepsearch.com, context why moving takes GET requests, is listed in neither registry at the last pull, and falls under market data by TOLL's rules.
context why moving is priced at 0.1 USDC on Base.
Its declared inputs are the path parameter ticker.
A response from context why moving, as declared, includes data, source and packType.
context why moving answered the sweep of 2026-10-30 with a valid 402, as at every sweep since 2026-10-01.
context why moving shares x402.deepsearch.com with 3 other listed endpoints and is tied 4th by calls with 1 other.
context why moving takes 3% of the calls counted across x402.deepsearch.com.
In the trailing 30 days: one call, one payer.
context why moving was last called 31 days before the snapshot.
Closest in price to context why moving within market data: startup domain check at api.strale.io and send token at keyring-agent.blockchhub.link.
context why moving is near the top of prices in market data; 92% of comparable listings are cheaper.
The wallet paid by context why moving is the payee of 38 endpoints on one host.
context why moving was missing from the Coinbase registry at the pull of 2026-11-01, not yet confirmed by a second pull; that is registry presence, not liveness.
The price of context why moving is declared by 309 other listings in market data 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-13 14:08 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.1 USDC | exact | 0xbECc98…93C8AD |
the checks, as of 2026-10-30 06:33 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-30 06:33 UTC | pass | 0 | daily-2026-10-30 |
| 2026-10-29 06:15 UTC | pass | 0 | daily-2026-10-29 |
| 2026-10-28 06:38 UTC | pass | 0 | daily-2026-10-28 |
| 2026-10-27 06:30 UTC | pass | 0 | daily-2026-10-27 |
| 2026-10-26 11:51 UTC | pass | 0 | daily-2026-10-26 |
| 2026-10-24 21:13 UTC | pass | 0 | daily-2026-10-24 |
| 2026-10-23 06:24 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-22 04:39 UTC | pass | 0 | daily-2026-10-22 |
| 2026-10-21 08:18 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 08:33 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 06:07 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 08:20 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-17 18:21 UTC | pass | 0 | daily-2026-10-17 |
| 2026-10-16 04:35 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 06:09 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 04:32 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 08:59 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 06:24 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 04:45 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 12:56 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 04:50 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 06:28 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 05:37 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 06:34 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 06:15 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 09:03 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 04:20 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 13:30 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 13:13 UTC | pass | 0 | new-after-daily-2026-10-01 |
Presence in a registry, not liveness of the service (method). Newest first.
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-01 06:22 UTC · method
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"pathParams": {
"ticker": "005930"
},
"queryParams": {}
},
"output": {
"type": "json",
"example": {
"data": {
"seed": {
"code": "005930",
"name": "삼성전자(주)"
},
"as_of": "2026-10-01",
"big_moves": [
{
"date": "2026-07-31",
"news": [
{
"title": "메모리 사이클 회복 기대감에 주주환원 정책까지…증권가, 삼성전자 목표가 ‘상향’",
"sentiment": 1
}
],
"close": 262500,
"return": 0.2681
}
],
"period_return": 0.2159
},
"source": "DeepSearch knowledge graph (Korean listed companies)",
"packType": "why-moving"
}
}
}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, "context why moving on x402.deepsearch.com". https://tollindex.com/e/x402-deepsearch-com-v1-context-why-moving-ticker-1e00aa. Accessed [access date].
BibTeX
@misc{toll-e-x402-deepsearch-com-v1-context-why-moving-ticker-1e00aa-2026-11-01,
author = {TOLL},
title = {context why moving on x402.deepsearch.com},
howpublished = {\url{https://tollindex.com/e/x402-deepsearch-com-v1-context-why-moving-ticker-1e00aa}},
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.