GEDX402 Search
Paid API · search.gedx402.com · found in a public registry · checked since 2026-10-16
Live, payment required · latest check
POST https://search.gedx402.com/v1/search$0.042 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. See 36 endpoints from gedx402.com.
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.
Details
Payment terms
- Price per call
- $0.042
- Protocols
- x402
- Networks
- eip155:8453eip155:137eip155:42161eip155:480solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
- Terms changes, 90 days
- 0 in 2 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
- 2
- Paid calls, 30 days
- 4
The registry's own figures, not our measurements.
Listing
In the capability tree: Search and information / Web search / Web search results (primary). Placed by a small AI model, where agents with the tasks it serves would look first (placement-ai/2, tree/3) on 2026-10-17. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/3): ✗ what it does is unclear to our placement; ✓ its latest check passed; ✗ fewer than 5 payers in 30 days (registry figure).
Purpose tags: searchtavilyserpweb-searchwinner
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453eip155:137eip155:42161eip155:480solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp | 372 ms |
cloudflare:LHR |
Live, valid payment request HTTP 402 | eip155:8453eip155:137eip155:42161eip155:480solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp | 346 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 2 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_a838f7e8080eae34