passlisted in Coinbase#14 by calls of 21 on this host
0.05 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
- 3
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-10-08 06:08 UTC
- First observed by TOLLderived
- 2026-09-28
- Pricederived
- 0.05 USDC
- Networks
- 1
How has the volume on this endpoint moved?
With 21 endpoints listed on mart402.com, jp crypto tax is tied 14th by calls with 7 others.
jp crypto tax takes a json body with the field transactions.
A response from jp crypto tax, as declared, includes ok, note, tool, as_of, result, sample and 2 others.
jp crypto tax drew 3 calls from 2 unique payers in the trailing 30 days.
The last call to jp crypto tax came 4 days before the snapshot, 2026-10-08.
A call to jp crypto tax costs 0.05 USDC on Base, as declared.
3% of the host's counted calls go to it.
mart402.com serves jp crypto tax, a POST endpoint that TOLL places in market data, listed in the Coinbase registry.
jp crypto tax answered the sweep of 2026-10-11 with a valid 402, as at every sweep since 2026-09-28.
Closest in price to jp crypto tax within market data: analyze at svm402.com and q verdict resource at www.ax1.vc.
jp crypto tax is priced above 86% of comparable listings in market data.
Across market data, 8,999 endpoints carry counters and jp crypto tax out-counts 55% of them.
The payee wallet is shared by 23 listings on one host.
jp crypto tax dropped out of the registry at the pull of 2026-09-30 and was listed again on 2026-09-30.
The price of jp crypto tax is declared by 556 other listings in market data too.
the payment options, as of 2026-10-12 05:54 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.05 USDC | exact | 0xE3244a…bB3188 |
the checks, as of 2026-10-11 08:48 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-11 08:48 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 17:00 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 10:04 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 11:31 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 10:53 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 11:36 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 10:17 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 13:15 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 06:50 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 16:00 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 08:48 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 08:12 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 20:22 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 17:29 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-28 05:32 UTC | pass | 0 | new-after-daily-2026-09-28 |
Presence in a registry, not liveness of the service (method). Newest first.
- back in Coinbase
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-08 06:08 UTC · method · live
The input and output block
{
"input": {
"body": {
"transactions": [
{
"qty": 4,
"type": "buy",
"asset": "BTC",
"total_jpy": 4000000
},
{
"qty": 0.2,
"type": "sell",
"asset": "BTC",
"total_jpy": 210000
}
]
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"ok": true,
"note": "SAMPLE RESPONSE generated by the exact deterministic engine that serves production (jp-statutory has no LLM: same input always produces this byte-identical result, carrying the same rules_version and cited primary sources). Served free at /samples/{product} so you can verify the response shape, the rules_version field and the source citations before paying. No payment was taken. The sample_input shown is the catalog example input that produced this output.",
"tool": "jp-crypto-tax",
"as_of": "2026-08-21",
"result": {
"method": "total_average",
"loss_note": null,
"per_asset": [
{
"asset": "BTC",
"method": "total_average",
"fees_jpy": 0,
"proceeds_jpy": 210000,
"cost_of_sales_jpy": 200000,
"quantity_disposed": 0.2,
"quantity_year_end": 3.8,
"realized_income_jpy": 10000,
"year_end_valuation_jpy": 3800000,
"unit_price_year_end_jpy": 1000000
}
],
"income_classification": "雑所得(その他雑所得)が原則(FAQ 2-2)",
"total_realized_income_jpy": 10000
},
"sample": true,
"sources": [
"https://www.nta.go.jp/publication/pamph/pdf/0023012-176.pdf"
],
"summary": "1資産・総平均法: 年間実現損益 10,000円(雑所得)",
"billable": true,
"breakdown": [],
"disclaimer": "仮定条件に基づく概算試算。税務相談・手続代行・法律相談ではない。申告・届出への使用不可。確定額は官公署または税理士・社会保険労務士等に確認のこと。",
"assumptions": [
"国税庁の「暗号資産の計算書」様式は単価の1円未満を切り上げる運用が知られており、割り切れない単価では本エンジンの厳密計算と数円の差が生じうる(様式再現モードは将来課題)"
],
"not_covered": [
"DeFi(流動性提供・レンディング)・NFT",
"ハードフォーク・エアドロップの取得価額",
"マイニング・ステーキング・レンディング報酬の取得時所得",
"事業所得該当性の判定(収入300万円超+帳簿保存)",
"信用取引・証拠金取引の建玉管理",
"国外取引所の年間取引報告書がない場合の残高照合",
"法人税(法定評価方法が異なる)"
],
"sample_input": {
"transactions": [
{
"qty": 4,
"type": "buy",
"asset": "BTC",
"total_jpy": 4000000
},
{
"qty": 0.2,
"type": "sell",
"asset": "BTC",
"total_jpy": 210000
}
]
},
"rules_version": "2026.08.18",
"carried_forward": [],
"unverified_rules": []
},
"description": "JSON: per-asset cost of sales, year-end unit price and valuation, realized income (misc income), optional incremental-tax estimate"
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-12 05:54 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "jp crypto tax on mart402.com", snapshot of 2026-10-12 05:54 UTC. https://tollindex.com/e/mart402-com-v1-jp-crypto-tax-a436dd/at/2026-10-12T05-54Z. Accessed [access date].
BibTeX
@misc{toll-e-mart402-com-v1-jp-crypto-tax-a436dd-2026-10-12T05-54Z,
author = {TOLL},
title = {jp crypto tax on mart402.com},
howpublished = {\url{https://tollindex.com/e/mart402-com-v1-jp-crypto-tax-a436dd/at/2026-10-12T05-54Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-12 05:54 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.