> ## Documentation Index
> Fetch the complete documentation index at: https://bavlio.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Email deliverability check, SMTP-backed (x402-paid, $0.003 USDC)

> SMTP-backed inline validate. No ARQ. No user context. Idempotent.

Prefilter hard-rejects (bad syntax / reserved / placeholder / system) settle a
stable ``risk_level == "invalid"`` payload rather than raising — the agent
asked a question and got a definitive answer. Otherwise the SMTP verdict is
mapped into the unchanged DTO; a non-answer (SMTP unavailable) returns 503 so
x402 skips settlement.



## OpenAPI

````yaml https://api.bavlio.com/openapi.json post /api/x402/v1/email/validate
openapi: 3.1.0
info:
  title: Bavlio API
  description: >-
    Outreach automation API — lead enrichment, email campaigns, LinkedIn
    automation, and AI agent. Full docs at https://docs.bavlio.com.
  version: 1.0.0
  x-guidance:
    product: Bavlio Data API
    protocols:
      - x402
    description: >-
      Pay-per-call B2B data endpoints for AI agents. USDC on Base mainnet via
      x402 v2. See /openapi.json for pricing. Landing page + marketing details:
      https://bavlio.com/developers
    network: eip155:8453
    docs_url: https://docs.bavlio.com
  x-payment-merchant-address: '0xcca4725e0e931982830bff523b141e1a7a58d3e7'
servers: []
security: []
tags:
  - name: API Keys
    description: >-
      Create, list, and revoke API keys for programmatic access. JWT
      authentication required.
  - name: credits
    description: Credit balance, cost estimates, and transaction history.
  - name: campaigns
    description: Create, manage, launch, and monitor email campaigns.
  - name: campaign-personalization
    description: AI-powered email subject and body personalization for campaigns.
  - name: email-finder
    description: Find and verify email addresses for prospects.
  - name: sender-profiles
    description: Manage sender identity profiles for outreach.
  - name: sender-profile-chat
    description: Interactive chat for building sender profiles.
  - name: templates
    description: Email template CRUD.
  - name: suppression
    description: Do-not-contact suppression list management.
  - name: datasets
    description: Lead dataset listing, download, and updates.
  - name: user-extractions
    description: Uploaded lead file management and processing.
  - name: enrichment-chat
    description: Interactive chat for data enrichment sessions.
  - name: enrichment-processing
    description: Batch lead enrichment processing.
  - name: File Upload (CSV/Excel)
    description: Upload and preview CSV/Excel lead files.
  - name: connected-accounts
    description: LinkedIn account connections via Unipile.
  - name: linkedin-content
    description: LinkedIn post creation, scheduling, and management.
  - name: linkedin-playground
    description: Direct LinkedIn actions (profile lookup, messaging, engagement).
  - name: bavimail-proxy
    description: BaviMail domain, alias, and email management.
  - name: agent
    description: Bavi AI agent chat with SSE streaming.
  - name: notifications
    description: Notification preferences and delivery.
  - name: referral
    description: Referral code management and stats.
  - name: feedback
    description: User feedback submission.
  - name: authentication
    description: JWT token verification and user info.
  - name: users
    description: User quota and usage information.
  - name: Health
    description: Health checks and system status.
  - name: Personalization
    description: Core lead personalization engine.
  - name: Session Management
    description: Enrichment session lifecycle.
  - name: Session Processing
    description: Session data processing.
  - name: webhooks
    description: Inbound webhook handlers (Stripe, BaviMail, Unipile).
paths:
  /api/x402/v1/email/validate:
    post:
      tags:
        - x402
      summary: Email deliverability check, SMTP-backed (x402-paid, $0.003 USDC)
      description: >-
        SMTP-backed inline validate. No ARQ. No user context. Idempotent.


        Prefilter hard-rejects (bad syntax / reserved / placeholder / system)
        settle a

        stable ``risk_level == "invalid"`` payload rather than raising — the
        agent

        asked a question and got a definitive answer. Otherwise the SMTP verdict
        is

        mapped into the unchanged DTO; a non-answer (SMTP unavailable) returns
        503 so

        x402 skips settlement.
      operationId: email_validate_api_x402_v1_email_validate_post
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/EmailValidateRequest'
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/EmailValidateResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
components:
  schemas:
    EmailValidateRequest:
      properties:
        email:
          type: string
          format: email
          title: Email
          description: Email address to validate
      type: object
      required:
        - email
      title: EmailValidateRequest
    EmailValidateResponse:
      properties:
        email:
          type: string
          title: Email
        normalized:
          anyOf:
            - type: string
            - type: 'null'
          title: Normalized
        valid_format:
          type: boolean
          title: Valid Format
        has_mx:
          type: boolean
          title: Has Mx
        is_disposable:
          type: boolean
          title: Is Disposable
        is_role:
          type: boolean
          title: Is Role
        risk_level:
          type: string
          title: Risk Level
        reason:
          anyOf:
            - type: string
            - type: 'null'
          title: Reason
        backend:
          type: string
          title: Backend
      type: object
      required:
        - email
        - valid_format
        - has_mx
        - is_disposable
        - is_role
        - risk_level
        - backend
      title: EmailValidateResponse
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.