Skrap API documentation

#Quickstart

1. 1

   Create an API key

   In the app, open Settings → API keys & MCP and create a key (paid plans). Export it as SKRAP_API_KEY so the samples below run as-is.

   Get an API key
2. 2

   Verify your first email

   Base URL https://api.skrap.ai. Send JSON, get JSON.

   cURLNode.jsPython

   Copy

   curl -X POST "https://api.skrap.ai/api/v2/verify-email" \  -H "x-api-key: $SKRAP_API_KEY" \  -H "Content-Type: application/json" \  -d '{"email":"[email protected]"}'

3. 3

   Read the result

   Branch on status. You are charged only for valid and risky answers.

   Response · 200Copy

   1{2  "email": "[email protected]",3  "status": "valid",            // valid | risky | invalid | unknown4  "retryable": false,           // true: unknown for a temporary reason — try later5  "domainInfo": { "domain": "example.com", "hasMxRecords": true },6  "score": 95,                  // 95 valid · 10–70 risky (by risk reason) · 0 invalid · null unknown7  "checks": {8    "syntax": true,9    "mxFound": true,10    "smtp": "accepted",         // accepted | rejected | inconclusive | not_checked11    "catchAll": false,12    "disposable": false,13    "roleAccount": false,14    "freeProvider": false15  },16  "riskReasons": [],            // risky only: catch_all, catch_all_unconfirmed, role_account, disposable17  "didYouMean": null            // typo hint, e.g. "[email protected]" for "[email protected]"18}

#Authentication

Every request carries your secret key in the x-api-key header.

x-api-key: sk_live_…

• Create a key in the app under Settings → API keys & MCP (paid plans). Keys are shown in full only to you; store them like passwords.
• Send it on every request in the x-api-key header. Keys on a team spend the team's shared credits.
• Optional per-key controls: an IP allowlist (exact IPs or IPv4 ranges such as 10.0.0.0/8) and an expiry date. Requests from other IPs get 403 IP_NOT_ALLOWED; expired keys get 401 API_KEY_EXPIRED.

#Credits

Credits are shared with the web app. You only pay for useful results.

#Rate limits

Responses carry standard rate-limit headers. Over the limit you get 429 RATE_LIMITED with a Retry-After header — wait that many seconds and retry.

#Verification statuses

#Errors

Errors use HTTP status codes and a JSON body with a stable code you can branch on.

1{2  "error": "Not enough credits",3  "code": "INSUFFICIENT_CREDITS",4  "details": { "required": 1, "available": 0 }5}