screen email derived
api.payperscreen.comCommunicationsderived
GET https://api.payperscreen.com/screen-email
passlisted in Coinbase#2 by calls of 5 on this host
0.02 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 90% / 90%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-12 15:40 UTC
- First observed by TOLLderived
- 2026-10-13
- Pricederived
- 0.02 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 1 time across 2 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.
screen email first appeared in TOLL's pulls on 2026-10-13.
At api.payperscreen.com, screen email takes GET requests, is listed in the Coinbase registry, and falls under communications by TOLL's rules.
screen email is priced at 0.02 USDC on Base.
Requests carry the query parameter email.
screen email answered the sweep of 2026-10-21 with a valid 402, passing 9 of 10 sweeps since 2026-10-13.
A response from screen email, as declared, includes email, redFlag, signals, flagCount and riskLevel.
screen email shares api.payperscreen.com with 4 other listed endpoints and is tied 2nd by calls with 3 others.
screen email takes 17% of the calls counted across api.payperscreen.com.
In the trailing 30 days: one call, one payer.
screen email was last called 1 day before the snapshot.
Closest in price to screen email within communications: linkedin reply at win.oneshotagent.com and sign at fractalai.net.co.
screen email is priced above 64% of comparable listings in communications.
5 listed endpoints on one host pay to the same wallet.
The seller's tags on screen email are compliance, sanctions, ofac and crypto.
Exactly this price appears on 154 other listings in communications.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.02 USDC | exact | 0xA81634…7C6f76 |
the checks, as of 2026-10-21 08: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-21 08:14 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 08:30 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 06:04 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 08:17 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-17 18:18 UTC | pass | 0 | daily-2026-10-17 |
| 2026-10-16 04:31 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 06:05 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 04:29 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 08:55 UTC | fail | 1 | daily-2026-10-13 |
| 2026-10-13 02:50 UTC | pass | 0 | new-after-daily-2026-10-12 |
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-12 15:40 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"email": "someone@example.com"
}
},
"output": {
"type": "json",
"example": {
"email": "someone@example.com",
"redFlag": false,
"signals": [],
"flagCount": 0,
"riskLevel": "low"
}
}
}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, "screen email on api.payperscreen.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-payperscreen-com-screen-email-1bc8e0/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-api-payperscreen-com-screen-email-1bc8e0-2026-10-13T14-08Z,
author = {TOLL},
title = {screen email on api.payperscreen.com},
howpublished = {\url{https://tollindex.com/e/api-payperscreen-com-screen-email-1bc8e0/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.