legacy v1listed in Coinbase#1 by calls of 2 on this host
0.01 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
- 2
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-09-14 19:58 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 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.
At the sweep of 2026-09-15 it answered with the x402 v1 protocol, which the registry no longer indexes.
memory add memory, a POST endpoint on staging.toolkit.dev, appears in the Coinbase registry; TOLL's taxonomy puts it in the "other" category.
memory add memory is priced at 0.01 USDC on Base.
Requests carry a json body with the field content.
memory add memory declares object output without an example.
The registry's counters give memory add memory 2 calls and 2 unique payers over 30 days, every call from a different payer.
memory add memory was last called 1 day before the snapshot.
staging.toolkit.dev lists 2 endpoints; memory add memory is tied 1st by calls with 1 other.
Of the calls counted across staging.toolkit.dev, memory add memory takes 50%.
It is cheaper than 36% of comparable listings in the "other" category.
Closest in price to memory add memory within the "other" category: merchants at www.x402scan.com and wallets transactions at api.zerion.io.
The wallet paid by memory add memory is the payee of 2 endpoints on one host.
The price of memory add memory is declared by 428 other listings in the "other" category 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.01 USDC | exact | 0x0cC2CD…2DF82F |
the checks, as of 2026-09-15 04:28 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 04:28 UTC | legacy v1 | 1 | daily-2026-09-15 |
| 2026-09-14 04:24 UTC | legacy v1 | 1 | daily-2026-09-14 |
| 2026-09-13 04:23 UTC | legacy v1 | 1 | daily-2026-09-13 |
| 2026-09-12 06:39 UTC | legacy v1 | 1 | daily-2026-09-12 |
| 2026-09-11 10:10 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-14 19:58 UTC · method · live
The input and output block
{
"input": {
"body": {
"content": {
"type": "string",
"required": true,
"description": "The content to store in memory"
}
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"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, "memory add memory on staging.toolkit.dev", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/staging-toolkit-dev-api-tool-memory-add-memory-39ebb1/at/2026-09-15T21-20Z. Accessed [access date].
BibTeX
@misc{toll-e-staging-toolkit-dev-api-tool-memory-add-memory-39ebb1-2026-09-15T21-20Z,
author = {TOLL},
title = {memory add memory on staging.toolkit.dev},
howpublished = {\url{https://tollindex.com/e/staging-toolkit-dev-api-tool-memory-add-memory-39ebb1/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.