recipient api prepare transfer derived
api.loyalspark.onlineMarket dataderived
POST https://api.loyalspark.online/x402-gateway/recipient-api/prepare-transfer
passlisted in Coinbase#6 by calls of 27 on this host
0.005 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
- 426
- Unique payers, trailing 30 days
- 27
- Last called
- 2026-09-15 18:49 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.005 USDC
- Networks
- 1
How has the volume on this endpoint moved?
The registry's counters give recipient api prepare transfer 426 calls and 27 unique payers over 30 days, about 16 calls per payer.
recipient api prepare transfer out-counts 99% of the 5,288 endpoints in market data that carry counters.
Of api.loyalspark.online's 27 listings, recipient api prepare transfer ranks 6th by calls.
It accounts for 8% of the calls counted across the host.
The last call to recipient api prepare transfer came on the day of the snapshot, 2026-09-15.
recipient api prepare transfer is a POST endpoint at api.loyalspark.online, listed in the Coinbase registry and filed by TOLL under market data.
recipient api prepare transfer is priced at 0.005 USDC on Base.
The listing declares an input block with no named parameters.
recipient api prepare transfer answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
A response from recipient api prepare transfer, as declared, includes ok and resource.
Closest in price to recipient api prepare transfer within market data: gas at base-gas-x402-production.up.railway.app and chain erc20 transfers at api.onesource.io.
recipient api prepare transfer is priced above 24% of comparable listings in market data.
The wallet paid by recipient api prepare transfer is the payee of 27 endpoints on one host.
The price of recipient api prepare transfer is declared by 483 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.005 USDC | exact | 0x40a8Cd…F4ad8b |
the checks, as of 2026-09-15 07:04 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-09-15 07:04 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:31 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:20 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 10:29 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 14:49 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-09-15 18:49 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/prepare-transfer"
}
}
}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, "recipient api prepare transfer on api.loyalspark.online", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/api-loyalspark-online-x402-gateway-recipient-api-prepare-transfer-f811af/at/2026-09-15T21-20Z. Accessed [access date].
BibTeX
@misc{toll-e-api-loyalspark-online-x402-gateway-recipient-api-prepare-transfer-f811af-2026-09-15T21-20Z,
author = {TOLL},
title = {recipient api prepare transfer on api.loyalspark.online},
howpublished = {\url{https://tollindex.com/e/api-loyalspark-online-x402-gateway-recipient-api-prepare-transfer-f811af/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.