Discover / api.probekit.dev
api.probekit.dev
■ Challenge detectedParse and evaluate a domain's SPF record: the include and redirect tree, qualifiers and the RFC 7208 limit of ten DNS lookups, with coded findings. Use when an agent must tell whether SPF is valid, why mail from a service fails SPF, or whether one more include would exceed the lookup limit.
- Listed price
- $0.01
- Challenge detected
- 1 of the last check
- Median response
- 615 ms
- Last checked
- 25 Oct, 12:23 UTC
- In our index since
- 25 Oct 2026
Endpoint
curl -i https://api.probekit.dev/v1/mail/spf # 402 Payment Required: pay with an x402 client (USDC on Base), # then send the same request again with the payment attached.
7 listed endpoints · on x402 Bazaar
Checks and payment terms on this page refer to the endpoint above. Other listed endpoints have not been checked individually.
Base URLhttps:
- GET/mail
/dmarc$0.01Look up the DMARC record of a domain or its organisational domain and explain policy, subdomain policy, alignment and reporting addresses, with coded findings. Use when an agent must tell whether a domain is protected against spoofing, which policy it enforces, or why DMARC reports do not arrive. - GET/mail
/spf$0.01Parse and evaluate a domain's SPF record: the include and redirect tree, qualifiers and the RFC 7208 limit of ten DNS lookups, with coded findings. Use when an agent must tell whether SPF is valid, why mail from a service fails SPF, or whether one more include would exceed the lookup limit. - GET/mail
/dkim$0.01Fetch and validate the DKIM public key record at selector._domainkey for a domain: key type, key size, revocation and syntax, with coded findings. Use when an agent knows the selector (s= in a DKIM-Signature header) and must confirm that the key is published and usable. It does not verify message signatures. - GET/mail
/mx$0.01List a domain's mail servers in preference order and detect null MX (RFC 7505) and MX targets that do not resolve, with coded findings. Use when an agent must find where mail for a domain is delivered or why a domain cannot receive mail. - POST/mail
/check /bulk$0.048Run the mail configuration check (MX, SPF, DMARC) on up to 20 domains in one request. Results keep the input order, and items that fail for a technical reason come with a token for a free retry. Use when an agent must audit many domains at once, for example a customer list or a portfolio of brands. - GET/mail
/check$0.03One report on a domain's mail setup: MX, SPF and DMARC, plus DKIM for the selectors you give, with coded findings and an overall status. Use when an agent needs a complete overview of a domain's email authentication and delivery configuration in one call instead of four. - GET/dns
/lookup$0.005Resolve chosen DNS record types (A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV) for a name through public resolvers, with TTL, observation time and the resolver that answered. Use when an agent needs the current public DNS answer for a name, for example to confirm that a record change is visible or to read a TXT verification record.
A dash means the listing gives no price or method. Copy buttons copy the full URL.
Showing 7 of 7 listed endpoints.
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/api.probekit.dev
Recent checks
All 1 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 25 Oct, 12:23 UTC | Challenge detected | 402 | 615ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 25 Oct, 12:23 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.
What price is recorded for api.probekit.dev?
Its listed price is $0.01.
What payment terms does api.probekit.dev advertise?
The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Where is api.probekit.dev listed?
In x402 Bazaar. Superstables first indexed it on 25 Oct 2026.
Something wrong on this page? Tell us.