recipient api redeem reward derived
api.loyalspark.onlineMarket dataderived
POST https://api.loyalspark.online/x402-gateway/recipient-api/redeem-reward
passlisted in Coinbase#14 by calls of 32 on this host
0.01 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 50% / 79% / 86%
- Calls, trailing 30 days
- 62
- Unique payers, trailing 30 days
- 15
- Last called
- 2026-10-11 11:16 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 1
How has the volume on this endpoint moved?
Among the 32 endpoints on api.loyalspark.online, recipient api redeem reward is 14th by calls.
Its declared input names no parameters.
A response from recipient api redeem reward, as declared, includes ok and resource.
Over 30 days: 62 calls, 15 payers, about 4 calls per payer.
recipient api redeem reward was last called 2 days before the snapshot.
The declared price is 0.01 USDC on Base.
recipient api redeem reward takes 2% of the calls counted across api.loyalspark.online.
TOLL files recipient api redeem reward under market data: a POST endpoint on api.loyalspark.online, listed in the Coinbase registry.
recipient api redeem reward answered the sweep of 2026-10-30 with a valid 402, passing 32 of 37 sweeps since 2026-09-11.
Closest in price to recipient api redeem reward within market data: markets mid at smx.space and stonk screener invoke at api.solenrich.com.
recipient api redeem reward is priced above 40% of comparable listings in market data.
Across market data, 8,872 endpoints carry counters and recipient api redeem reward out-counts 97% of them.
The payee wallet is shared by 32 listings on one host.
The price of recipient api redeem reward 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 | 0x40a8Cd…F4ad8b |
the checks, as of 2026-10-30 11:14 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:14 UTC | pass | 0 | daily-2026-10-30 |
| 2026-10-29 10:51 UTC | pass | 0 | daily-2026-10-29 |
| 2026-10-28 11:15 UTC | malformed | 2 | daily-2026-10-28 |
| 2026-10-27 10:52 UTC | malformed | 2 | daily-2026-10-27 |
| 2026-10-23 11:19 UTC | malformed | 2 | daily-2026-10-23 |
| 2026-10-21 20:53 UTC | malformed | 2 | daily-2026-10-21 |
| 2026-10-19 11:04 UTC | malformed | 2 | daily-2026-10-19 |
| 2026-10-18 19:18 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-16 08:53 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 10:50 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 08:41 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 13:33 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 10:58 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 09:39 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 17:49 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 11:02 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 12:37 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 11:52 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 12:35 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 11:08 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 13:53 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 07:19 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 16:28 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 09:12 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 08:39 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 20:46 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-23 07:43 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 07:56 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 08:18 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 06:17 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-17 06:08 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 06:07 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 06:24 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 05:53 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 05:46 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 08:03 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 12:00 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-11 11:16 UTC · method · live
The input and output block
{
"input": {
"body": {},
"type": "http",
"method": "POST",
"headers": {
"x-api-key": "rwk_..."
},
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"ok": true,
"resource": "recipient-api/redeem-reward"
}
}
}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, "recipient api redeem reward on api.loyalspark.online", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-loyalspark-online-x402-gateway-recipient-api-redeem-reward-be24d3/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-api-loyalspark-online-x402-gateway-recipient-api-redeem-reward-be24d3-2026-10-13T14-08Z,
author = {TOLL},
title = {recipient api redeem reward on api.loyalspark.online},
howpublished = {\url{https://tollindex.com/e/api-loyalspark-online-x402-gateway-recipient-api-redeem-reward-be24d3/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.