Agent ValidationPOST

Agent Validate

Agent-First Single Email Validation Endpoint. Query Parameters: format: "llm" returns ultra-minimal JSON (~15 tokens), "standard" returns full details detailed: True runs full pipeline (DNS + SMTP + blocklist), False runs blocklist only Example LLM response (format=llm): { "status": "valid", "confidence": 0.98, "recommendation": "send" } Recommendation values: - "send": Email is safe to send to (verdict=allow) - "quarantine": Email is suspicious, review manually (verdict=review) - "drop": Email is invalid or dangerous (verdict=block) Authentication: API key via APIGatewayMiddleware (upstream) Use POST /v1/agent/validate when you need this capability from your application or backend. It accepts a JSON request body. Query parameters are available for request scoping and filtering.

Endpoint

Use this full URL directly in server-side integrations, scripts, or internal tooling.

POST request

https://api.dropfakes.com/api/v1/agent/validate

Full endpoint URL

POST https://api.dropfakes.com/api/v1/agent/validate

Authorization

This section explains how this endpoint should be called in the current API version.

No authorization required

This endpoint is documented as public in this version of the API reference. No bearer token is required.

Authorization

Authorization: dk_live_*****

Code examples

Start with curl, then use the language sample that matches your backend.

curl

curl -X POST "https://api.dropfakes.com/api/v1/agent/validate?format=standard&detailed=false" \
  -H "Content-Type: application/json" \
  -d '{
  "email": "person@example.com"
}'

Parameters

Query string parameters and request body fields are listed together for faster scanning.

Name	Location	Type	Required	Description	Default
format	query	llm \| standard	No	Response format: 'llm' for token-optimized (15 tokens), 'standard' for verbose	standard
detailed	query	boolean	No	Run full validation (DNS + SMTP + blocklist) vs. simple (blocklist only)	false
email	body	string (email)	Yes	Body field for `email`.	-

Success response

The primary success status for this operation is 200.

Status 200

Successful Response

200 application/json

{
  "email": "person@example.com",
  "domain": "example.com",
  "disposable": false,
  "verdict": "allow",
  "riskScore": 0.08,
  "checkedAt": "2026-03-21T10:15:00.000Z"
}

Error response

Use this example to handle validation and request errors safely on the client or backend.

Status 422

Validation Error

422 application/json

{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}