Agent ValidationPOST

Agent Validate Batch

Agent-First Batch Validation Endpoint. Accepts raw JSON array of email strings (up to 1,000 for LLM format, 100 for standard). No CSV parsing or multipart file uploads — AI agents cannot easily generate these. Query Parameters: format: "llm" returns ultra-minimal JSON, "standard" returns full details Example request body (format=llm): { "emails": ["a@b.com", "c@d.com", "e@f.com"] } Example LLM response (format=llm): { "results": [ {"status": "valid", "confidence": 0.98, "recommendation": "send"}, {"status": "invalid", "confidence": 0.10, "recommendation": "drop"}, {"status": "risky", "confidence": 0.45, "recommendation": "quarantine"} ], "total": 3, "processed": 3 } Authentication: API key via APIGatewayMiddleware (upstream) Use POST /v1/agent/validate/batch 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/batch

Full endpoint URL

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

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/batch?format=standard" \
  -H "Content-Type: application/json" \
  -d '{
  "emails": [
    "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, 'standard' for verbose	standard
emails	body	string (email)[]	Yes	Body field for `emails`.	-

Success response

The primary success status for this operation is 200.

Status 200

Successful Response

200 application/json

{
  "results": [
    {
      "email": "person@example.com",
      "verdict": "allow",
      "riskScore": 0.08,
      "disposable": false
    }
  ],
  "total": 100,
  "processed": 1
}

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"
    }
  ]
}