passlisted in Coinbase#80 by calls of 128 on this host
0.01 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
- 2
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-09-29 08:59 UTC
- First observed by TOLLderived
- 2026-09-23
- 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 35 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.
Among the 128 endpoints on agents.daedalusdevelopmentgroup.com, browser proof is tied 80th by calls with 45 others.
Its declared input names no parameters.
browser proof returns json; the example shows ok.
The registry's counters give browser proof 2 calls and 2 unique payers over 30 days, every call from a different payer.
browser proof was last called 4 days before the snapshot.
Each call is priced at 0.01 USDC, payable on Base.
browser proof is a POST endpoint at agents.daedalusdevelopmentgroup.com, listed in the Coinbase registry and filed by TOLL under scraping.
browser proof answered the sweep of 2026-10-03 with a valid 402, as at every sweep since 2026-09-23.
Closest in price to browser proof within scraping: firecrawl scrape at vaaya.ai and contacts at agents.dyoeway.org.
Among comparable prices in scraping, browser proof sits above 33% of them.
The payee wallet is shared by 128 listings on one host.
The seller's tags on browser proof are ai-agents, x402, agent-commerce and mcp-security.
The price of browser proof is declared by 272 other listings in scraping too.
the payment options, as of 2026-10-02 22:12 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x8AfBD5…830Bc6 |
the checks, as of 2026-10-03 03:49 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-03 03:49 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 12:58 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 06:15 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 04:21 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 17:55 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 03:48 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-27 09:41 UTC | pass | 0 | daily-2026-09-27 |
| 2026-09-26 12:33 UTC | pass | 0 | daily-2026-09-26 |
| 2026-09-25 19:31 UTC | pass | 0 | daily-2026-09-25 |
| 2026-09-23 05:14 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-23 05:05 UTC | pass | 0 | new-after-daily-2026-09-22 |
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-29 08:59 UTC · method · live
The input and output block
{
"input": {
"body": {},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"ok": true
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-02 22:12 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "browser proof on agents.daedalusdevelopmentgroup.com", snapshot of 2026-10-02 22:12 UTC. https://tollindex.com/e/agents-daedalusdevelopmentgroup-com-v1-browser-proof-018f81/at/2026-10-02T22-12Z. Accessed [access date].
BibTeX
@misc{toll-e-agents-daedalusdevelopmentgroup-com-v1-browser-proof-018f81-2026-10-02T22-12Z,
author = {TOLL},
title = {browser proof on agents.daedalusdevelopmentgroup.com},
howpublished = {\url{https://tollindex.com/e/agents-daedalusdevelopmentgroup-com-v1-browser-proof-018f81/at/2026-10-02T22-12Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-02 22:12 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.