btc jpy derived
api.myceliasignal.comMarket dataderived
GET https://api.myceliasignal.com/oracle/price/btc/jpy
passlisted in Coinbase#13 by calls of 176 on this host
0.01 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 5
- Unique payers, trailing 30 days
- 3
- Last called
- 2026-10-08 06:27 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 1
How has the volume on this endpoint moved?
btc jpy shares api.myceliasignal.com with 175 other listed endpoints and is tied 13th by calls with 14 others.
btc jpy declares an input block that names no parameters.
A response from btc jpy, as declared, includes pair, price, method and sources.
The registry's counters give btc jpy 5 calls and 3 unique payers over 30 days.
btc jpy was last called 5 days before the snapshot.
On Base, btc jpy asks 0.01 USDC per call.
btc jpy, a GET endpoint on api.myceliasignal.com, appears in the Coinbase registry; TOLL's taxonomy puts it in market data.
btc jpy answered the sweep of 2026-10-30 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to btc jpy within market data: price at svm402.com and address current balance at api.nansen.ai.
btc jpy is priced above 40% of comparable listings in market data.
Across market data, 8,872 endpoints carry counters and btc jpy out-counts 78% of them.
Its payee wallet receives for 192 listed endpoints on one host.
The price of btc jpy is declared by 2,674 other listings in market data too.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0xD59383…96700d |
the checks, as of 2026-10-30 11:46 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-30 11:46 UTC | pass | 0 | daily-2026-10-30 |
| 2026-10-29 11:24 UTC | pass | 0 | daily-2026-10-29 |
| 2026-10-28 11:50 UTC | pass | 0 | daily-2026-10-28 |
| 2026-10-27 11:26 UTC | pass | 0 | daily-2026-10-27 |
| 2026-10-23 11:56 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-21 21:24 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-19 11:39 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-16 09:25 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 11:25 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 09:14 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 14:06 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 11:33 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 10:12 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 18:23 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 11:45 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 13:26 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 12:37 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 13:17 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 11:42 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 14:22 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 07:40 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 16:48 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 09:30 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 08:58 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 21:04 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-23 07:58 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 08:11 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 08:34 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 06:32 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-17 06:23 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 06:21 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 06:37 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:06 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 05:58 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 08:15 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 12:47 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-08 06:27 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {}
},
"output": {
"type": "json",
"example": {
"pair": "BTCJPY",
"price": "12500000",
"method": "median",
"sources": [
"binance",
"coinbase",
"kraken",
"bitstamp",
"gemini",
"okx",
"bitfinex",
"bullish",
"gateio"
]
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "btc jpy on api.myceliasignal.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-myceliasignal-com-oracle-price-btc-jpy-d259c1/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-api-myceliasignal-com-oracle-price-btc-jpy-d259c1-2026-10-13T14-08Z,
author = {TOLL},
title = {btc jpy on api.myceliasignal.com},
howpublished = {\url{https://tollindex.com/e/api-myceliasignal-com-oracle-price-btc-jpy-d259c1/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.