agproxy
Paid API · agproxy.shveik.dev · found in a public list · checked since 2026-10-17
Live, payment required · latest check
Fetches one URL from a residential IP and returns the raw status, headers and body.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/3). What this means
Placed in Fetch past blocks: Fetch pages through proxies or past bot protection and anti-scraping checks.
POST https://agproxy.shveik.dev/x402/fetch$0.016 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. See 47 endpoints from shveik.dev.
Our checks
An unpaid request weekly, from eastern North AmericaLast 3 checks, oldest to newest; room for 27 more
3 passed, 0 failed, 27 not run.
Checked weekly. Weekly: fewer than 5 payers, or no usage figure.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-17 | 3 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-17 | 3 | 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.016
- Protocols
- x402, mpp
- Networks
- eip155:8453solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpeip155:137
- Terms changes, 90 days
- 0 in 5 days tracked
Price from the registry's payment terms; protocols and networks from its payment request at our checks. Current terms first seen 2026-10-17; 0 receiving-address changes. Definitions
Reported by the registry
- Payers, 30 days
- 4
- Paid calls, 30 days
- 12
The registry's own figures, not our measurements.
Access
- Our latest check
- Asked for payment (x402, MPP)
- 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
Listing
In the capability tree: Web access and automation / Fetch and extract pages / Fetch past blocks (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/5): ✓ says what it does; ✓ its latest check passed; ✗ fewer than 5 payers in 30 days (registry figure).
Purpose tags: none in the registry
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpeip155:137 | 508 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpeip155:137 | 335 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpeip155:137 | 538 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 4 days (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_849ad02926a6d19f