Discover / api.mdataaccess.com
MDataAccess
□ No challenge detectedPay-per-request business, people, company, lead, and web intelligence for autonomous AI agents. Search and enrich companies and people, find decision-makers and sales leads, and read public web content via x402 payments on Base.
- Challenge detected
- 1 of the last 4 checks
- Median response
- 450 ms
- Last checked
- 17 Oct, 07:50 UTC
- In our index since
- 14 Oct 2026
Endpoint
curl -i https://api.mdataaccess.com # 402 Payment Required: pay with an x402 client (USDC on Base), # then send the same request again with the payment attached.
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/api.mdataaccess.com
Recent checks
14 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.17 Oct 2026
All 4 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 17 Oct, 07:50 UTC | No challenge detected | 200 | 339ms |
| 15 Oct, 19:10 UTC | No challenge detected | 200 | 717ms |
| 14 Oct, 12:00 UTC | No challenge detected | 200 | 248ms |
| 14 Oct, 08:45 UTC | Challenge detected | 402 | 450ms |
Questions
Did our last probe detect a payment challenge?
No. At our last probe on 17 Oct, 07:50 UTC, we detected no payment challenge.
What payment terms does MDataAccess advertise?
The listing advertises x402, Base and USDC. Check the seller's current payment challenge and authentication requirements before paying.
Where is MDataAccess listed?
In x402-list.com. Superstables first indexed it on 14 Oct 2026.
Something wrong on this page? Tell us.