# Pragmatic Email Validator

> Validates that an email address meets pragmatic format and length expectations. Rejects RFC-compliant emails incompatible with modern email services and technologies.

RFC 5322 permits email formats that no major mail provider actually supports. This validator operates in the practical middle ground — accepting what will actually work while rejecting theoretical-only formats.

## Docs

- [README](https://github.com/devpartners/pragmatic-email-validator/blob/main/README.md): Project overview, architecture, and API documentation
- [API Reference](https://api.pragmaticemailvalidator.com/openapi/v1.json): OpenAPI specification
- [Providers](https://api.pragmaticemailvalidator.com/api/v1/providers): Supported email provider definitions and rules
- [llms-full.txt](https://pragmaticemailvalidator.com/llms-full.txt): Detailed API usage guide for LLMs

## API Base URL

- Production: `https://api.pragmaticemailvalidator.com`

## Key Endpoints

- `POST /api/v1/validate` — Validate a single email address
- `GET /api/v1/validate?email={email}` — Validate via query string
- `POST /api/v1/validate/matrix` — Validate against all providers
- `GET /api/v1/providers` — List all supported providers with rules
- `GET /api/v1/providers/{providerId}` — Get a specific provider's rules
- `GET /api/v1/providers/export?format=jsonl` — Export providers as JSONL

## Source Code

- GitHub: [devpartners/pragmatic-email-validator](https://github.com/devpartners/pragmatic-email-validator)
- Language: C# / .NET 10
- Frontend: React / TypeScript / Vite
- License: MIT