vending-machine-seven.vercel.app
Paid API · vending-machine-seven.vercel.app · found in a public list · checked since 2026-10-24
Live, payment required · latest check
Checks email format and mail domains, geolocates IPs, and makes safe HTTP HEAD requests.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in Validate email addresses: Check whether an address is well formed, can receive mail, or is disposable, role-based or risky.
GET https://vending-machine-seven.vercel.app/api/v/bundle-outbound$0.01 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. See 11 endpoints from vending-machine-seven.vercel.app.
Our checks
An unpaid request daily, from eastern North AmericaLast 2 checks, oldest to newest; room for 28 more
2 passed, 0 failed, 28 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-24 | 2 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-24 | 2 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing an unpaid request answered with a payment request (HTTP 402). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Payment terms
- Price per call
- $0.01
- Protocols
- x402
- Networks
- eip155:8453
- Terms changes, 90 days
- 0 in 1 day tracked
Price from the registry's payment terms; protocols and networks from its payment request at our checks. Current terms first seen 2026-10-24; 0 receiving-address changes. Definitions
Reported by the registry
- Payers, 30 days
- 2
- Paid calls, 30 days
- 2
The registry's own figures, not our measurements.
Access
- Our latest check
- Asked for payment (x402)
- Stated
- not stated
- Payment model
- Per call (asked for payment for our request)
- Currency
- USD (USDC, in its payment terms)since
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
What it says about itself
- For
- agentsfrom its listing's description, read 2026-10-24
- Takes
- email address, IP address, URLfrom its listing's description, read 2026-10-24
- Returns
- email format/MX check, IP geolocation, HTTP HEAD resultfrom its listing's description, read 2026-10-24
From the service's own text, put in short words by a small AI model and shown only where its own words support it (stated-facts/2): its claims, not checked by us. Anything not listed, it does not state. Definitions
Calls it declares
GET email ip url → service ok ms_total email ip
From the payment request it sent our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Messaging and communication / Email / Validate email addresses (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-24. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Purpose tags: none in the registry
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 64 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 87 ms |
What these figures do not show
- A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). It does not show that a paid call succeeds or returns useful results.
- Payer and call counts are the registry's own figures, not our measurements.
- The registry's description is not republished.
- Limited evidence: monitored for 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_0b09135347a246e7