legacy v1listed in Coinbase#3 by calls of 5 on this host
0.1 USDC
per call, as the listing declares it on eip155:
- Validation state
- legacy v1
- Uptime, 7 / 30 / 90 days
- 0% / 0% / 0%
- Calls, trailing 30 days
- 5
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-09-11 08:15 UTC
- First observed by TOLLderived
- 2026-09-10
- 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 2 times across 29 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.
The sweep of 2026-09-15 found it on x402 v1.
At api.itsgloria.ai, pm scorings takes GET requests, is listed in the Coinbase registry, and falls under market data by TOLL's rules.
A call to pm scorings costs 0.1 USDC on Base, as declared.
Callers of pm scorings supply the query parameters tier, limit, event_id and market_id.
It declares object output but gives no example.
pm scorings drew 5 calls from 2 unique payers in the trailing 30 days.
The last call to pm scorings came 5 days before the snapshot, 2026-09-11.
Among the 5 endpoints on api.itsgloria.ai, pm scorings is 3rd by calls.
pm scorings takes 20% of the calls counted across api.itsgloria.ai.
Among comparable prices in market data, pm scorings sits above 87% of them.
Closest in price to pm scorings within market data: distribution balance exchanges relative at x402.glassnode.com and smart money netflow at api.nansen.ai.
The wallet paid by pm scorings is the payee of 5 endpoints on one host.
pm scorings out-counts 77% of the 5,288 endpoints in market data that carry counters.
The price of pm scorings is declared by 282 other listings in market data too.
the payment options, as of 2026-09-15 21:20 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.1 USDC | exact | 0xCa1271…89cd0c |
the checks, as of 2026-09-15 03:55 UTC · method · pinnableendpoint answered HTTP 402
x402_version· the body declares x402 version 2
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 03:55 UTC | legacy v1 | 1 | daily-2026-09-15 |
| 2026-09-14 03:54 UTC | legacy v1 | 1 | daily-2026-09-14 |
| 2026-09-13 03:54 UTC | legacy v1 | 1 | daily-2026-09-13 |
| 2026-09-12 06:09 UTC | legacy v1 | 1 | daily-2026-09-12 |
| 2026-09-11 09:33 UTC | legacy v1 | 1 | 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-09-11 08:15 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"tier": {
"type": "string",
"required": false,
"description": "Filter by tier: SKIP | WATCH | TRADE"
},
"limit": {
"type": "string",
"required": false,
"description": "Max rows to return (1-500, default 50)"
},
"event_id": {
"type": "string",
"required": false,
"description": "Filter by event id"
},
"market_id": {
"type": "string",
"required": false,
"description": "Filter by market id"
}
}
},
"output": {
"type": "object"
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 21:20 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "pm scorings on api.itsgloria.ai", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/api-itsgloria-ai-pm-scorings-0b2ad8/at/2026-09-15T21-20Z. Accessed [access date].
BibTeX
@misc{toll-e-api-itsgloria-ai-pm-scorings-0b2ad8-2026-09-15T21-20Z,
author = {TOLL},
title = {pm scorings on api.itsgloria.ai},
howpublished = {\url{https://tollindex.com/e/api-itsgloria-ai-pm-scorings-0b2ad8/at/2026-09-15T21-20Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 21:20 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.