geopolitical supply chain risk derived
geopoliticalpulse.theaslangroupllc.comMarket dataderived
GET https://geopoliticalpulse.theaslangroupllc.com/api/geopolitical/supply-chain-risk
no methodlisted in Coinbase and Binance#1 by calls of 10 on this host
0.2 USDC
per call, as the listing declares it on eip155:
- Validation state
- no method
- Uptime, 7 / 30 / 90 days
- — / — / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-16 02:43 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.2 USDC
- Networks
- 11
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 47 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.
geopoliticalpulse.theaslangroupllc.com serves geopolitical supply chain risk, a GET endpoint that TOLL places in market data, listed in both the Coinbase and Binance registries.
A call to geopolitical supply chain risk costs 0.2 USDC on Base, as declared.
Its declared input names no parameters.
For geopolitical supply chain risk the listing declares 14 accepts on Base, Solana, Polygon, Arbitrum and 7 others, to 4 different wallets.
geopolitical supply chain risk returns json; the example shows sector, analyst_assessment, overall_risk_level, maritime_chokepoints, critical_dependencies and decoupling_assessment.
geopolitical supply chain risk declares no HTTP method, so the daily sweep leaves it uncalled.
Of geopoliticalpulse.theaslangroupllc.com's 10 listings, geopolitical supply chain risk ranks tied 1st by calls with 9 others.
Of the calls counted across geopoliticalpulse.theaslangroupllc.com, geopolitical supply chain risk takes 10%.
geopolitical supply chain risk drew a single call from a single payer in the trailing 30 days.
The last call to geopolitical supply chain risk came 17 days before the snapshot, 2026-10-16.
Closest in price to geopolitical supply chain risk within market data: smart money netflow at api.nansen.ai and q verdict resource at www.ax1.vc.
geopolitical supply chain risk is near the top of prices in market data; 97% of comparable listings are cheaper.
The wallet paid by geopolitical supply chain risk is the payee of 973 endpoints across 78 hosts.
For 9 of the options on geopolitical supply chain risk, TOLL has no verified decimals and shows the raw amount. geopolitical supply chain risk declares exact and eip3009 as payment schemes.
Seller tags: supply-chain-risk, chokepoints, critical-minerals and semiconductors.
geopolitical supply chain risk dropped out of the registry at the pull of 2026-09-19 and was listed again on 2026-11-01.
The price of geopolitical supply chain risk is declared by 37 other listings in market data too.
the payment options, as of 2026-11-02 05:58 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.2 USDC | exact | 0x50ab20…4912fc |
| Coinbase | eip155: | USDC | 0.2 USDC | exact | 0x50ab20…4912fc |
| Coinbase | solana: | USDC | 0.2 USDC | exact | 985iFjbn…4B5KX1 |
| Coinbase | eip155: | USDC | 0.2 USDC | exact | 0x50ab20…4912fc |
| Coinbase | eip155: | USDC | 0.2 USDC | exact | 0x50ab20…4912fc |
| Coinbase | eip155: | USDC | 200000 smallest units, decimals unknown | exact | 0x50ab20…4912fc |
| Coinbase | eip155: | USDC | 200000 smallest units, decimals unknown | exact | 0x50ab20…4912fc |
| Coinbase | eip155: | USD₮0 | 200000 smallest units, decimals unknown | exact | 0x50ab20…4912fc |
| Coinbase | eip155: | USDC | 200000 smallest units, decimals unknown | exact | 0x50ab20…4912fc |
| Coinbase | algorand: | 31566704 | 200000 smallest units, decimals unknown | exact | 62A253YP…FWGI7I |
| Coinbase | xrpl: | XRP | 200000 smallest units, decimals unknown | exact | rMnHeutY…pPEh32 |
| Coinbase | xrpl: | 524C5553…000000 | amount not declared | exact | rMnHeutY…pPEh32 |
| Coinbase | eip155: | World Liberty Financial USD | 200000000000000000 smallest units, decimals unknown | exact | 0x50ab20…4912fc |
| Binance | eip155: | 0x8d0d00…f08b0d | 200000000000000000 smallest units, decimals unknown | eip3009 | 0x50ab20…4912fc |
the checks, as of 2026-10-30 07:44 UTC · method · pinnableendpoint answered HTTP none
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-30 07:44 UTC | no method | 0 | daily-2026-10-30 |
| 2026-10-29 07:25 UTC | no method | 0 | daily-2026-10-29 |
| 2026-10-28 07:47 UTC | no method | 0 | daily-2026-10-28 |
| 2026-10-27 07:36 UTC | no method | 0 | daily-2026-10-27 |
| 2026-10-26 12:55 UTC | no method | 0 | daily-2026-10-26 |
| 2026-10-24 22:18 UTC | no method | 0 | daily-2026-10-24 |
| 2026-10-23 07:37 UTC | no method | 0 | daily-2026-10-23 |
| 2026-10-22 05:53 UTC | no method | 0 | daily-2026-10-22 |
| 2026-10-21 10:14 UTC | no method | 0 | daily-2026-10-21 |
| 2026-10-20 09:44 UTC | no method | 0 | daily-2026-10-20 |
| 2026-10-19 07:21 UTC | no method | 0 | daily-2026-10-19 |
| 2026-10-18 09:28 UTC | no method | 0 | daily-2026-10-18 |
| 2026-10-17 19:33 UTC | no method | 0 | daily-2026-10-17 |
| 2026-10-16 05:40 UTC | no method | 0 | daily-2026-10-16 |
| 2026-10-15 07:20 UTC | no method | 0 | daily-2026-10-15 |
| 2026-10-14 05:33 UTC | no method | 0 | daily-2026-10-14 |
| 2026-10-13 10:08 UTC | no method | 0 | daily-2026-10-13 |
| 2026-10-12 07:31 UTC | no method | 0 | daily-2026-10-12 |
| 2026-10-11 06:04 UTC | no method | 0 | daily-2026-10-11 |
| 2026-10-10 14:12 UTC | no method | 0 | daily-2026-10-10 |
| 2026-10-09 06:34 UTC | no method | 0 | daily-2026-10-09 |
| 2026-10-08 08:02 UTC | no method | 0 | daily-2026-10-08 |
| 2026-10-07 07:16 UTC | no method | 0 | daily-2026-10-07 |
| 2026-10-06 08:06 UTC | no method | 0 | daily-2026-10-06 |
| 2026-10-05 07:28 UTC | no method | 0 | daily-2026-10-05 |
| 2026-10-04 10:07 UTC | no method | 0 | daily-2026-10-04 |
| 2026-10-03 05:04 UTC | no method | 0 | daily-2026-10-03 |
| 2026-10-02 14:22 UTC | no method | 0 | daily-2026-10-02 |
| 2026-10-01 07:21 UTC | no method | 0 | daily-2026-10-01 |
| 2026-09-30 06:38 UTC | no method | 0 | daily-2026-09-30 |
| 2026-09-29 18:58 UTC | no method | 0 | daily-2026-09-29 |
| 2026-09-28 05:46 UTC | no method | 0 | daily-2026-09-28 |
| 2026-09-25 20:30 UTC | no method | 0 | daily-2026-09-25 |
| 2026-09-23 06:08 UTC | no method | 0 | daily-2026-09-23 |
| 2026-09-22 06:18 UTC | no method | 0 | daily-2026-09-22 |
| 2026-09-21 06:41 UTC | no method | 0 | daily-2026-09-21 |
| 2026-09-20 19:20 UTC | no method | 0 | daily-2026-09-20 |
| 2026-09-19 04:43 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-18 10:36 UTC | pass | 0 | daily-2026-09-18 |
| 2026-09-17 04:39 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 04:39 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 04:37 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 04:33 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:31 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 06:47 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 10:20 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- back in Coinbase
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Binance
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-16 02:43 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {}
},
"output": {
"type": "json",
"errors": {
"400": {
"example": {
"error": "invalid request"
},
"description": "Invalid or missing parameter(s). Returned before the payment gate on paid requests, so a malformed call is never charged. JSON body: { error: <what is wrong and how to fix it> } plus usage hints."
},
"402": {
"description": "Payment required — x402 v2 challenge; the accepts array lists scheme, network, and amount. Retry the same request with a PAYMENT-SIGNATURE (v2) or X-PAYMENT (v1) header. Verification is free."
},
"500": {
"example": {
"error": "upstream_failed"
},
"description": "Unexpected server error. If a payment settled without a usable result, contact info@theaslangroupllc.com with the settlement tx hash for a re-run or credit."
}
},
"example": {
"sector": "semiconductors",
"analyst_assessment": "The semiconductor supply chain represents the most geopolitically contested industrial sector...",
"overall_risk_level": "CRITICAL",
"maritime_chokepoints": [
"Taiwan Strait",
"Strait of Malacca"
],
"critical_dependencies": [
{
"market_share": "90%",
"input_or_component": "TSMC advanced node wafers",
"concentration_country": "Taiwan",
"geopolitical_risk_level": "CRITICAL"
},
{
"market_share": "100%",
"input_or_component": "ASML EUV lithography",
"concentration_country": "Netherlands/EU",
"geopolitical_risk_level": "MODERATE"
}
],
"decoupling_assessment": {
"momentum": "ACCELERATING",
"beneficiary_countries": [
"US",
"India",
"Japan",
"EU"
]
}
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-11-02 05:58 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "geopolitical supply chain risk on geopoliticalpulse.theaslangroupllc.com", snapshot of 2026-11-02 05:58 UTC. https://tollindex.com/e/geopoliticalpulse-theaslangroupllc-com-api-geopolitical-supply-chain-risk-46e0b4/at/2026-11-02T05-58Z. Accessed [access date].
BibTeX
@misc{toll-e-geopoliticalpulse-theaslangroupllc-com-api-geopolitical-supply-chain-risk-46e0b4-2026-11-02T05-58Z,
author = {TOLL},
title = {geopolitical supply chain risk on geopoliticalpulse.theaslangroupllc.com},
howpublished = {\url{https://tollindex.com/e/geopoliticalpulse-theaslangroupllc-com-api-geopolitical-supply-chain-risk-46e0b4/at/2026-11-02T05-58Z}},
year = {2026},
month = {11},
note = {Pinned view of the snapshot of 2026-11-02 05:58 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.