LeadFlags
leadflags.com
What it is
LeadFlags is a deterministic lead-scoring API and web service that filters fake, low-intent, and risky inbound leads before they reach a CRM or call queue. It returns a score, quality level, risk flags, positive signals, and a recommended routing action. Predefined rules give the same output for the same input, without AI, enrichment, or profiling. JSON requests have no fixed schema; field aliases and optional mapping overrides support nonstandard keys. The service can identify missing or invalid contact details, disposable email, suspicious messages, and inconsistent fields. It is described as CRM-agnostic, with HubSpot and Salesforce named as examples. Requests require an X-API-Key header; Bearer authorization is not supported. Starter costs €39 a month for up to 1,000 leads, Growth €99 a month for up to 10,000, and Scale €249 a month for up to 50,000. Enterprise uses custom billing and terms. Annual billing offers a 20% discount.
Spec sheet
- What it does
- LeadFlags evaluates inbound leads and returns a numeric quality score, quality level, explanatory flags, positive signals and a recommended action.Read 15 Oct 2026 · leadflags.com
- Purpose
- The maker says it was built to answer consistently whether a lead is worth a sales call.Read 15 Oct 2026 · leadflags.com
- Intended users
- The site names marketing agencies, call centers, and lead sellers and buyers as audiences for consistent lead scoring.Read 7 Oct 2026 · leadflags.com
- Integrations
- LeadFlags describes itself as CRM-agnostic and says it can be used before any CRM or workflow; the site mentions HubSpot and Salesforce as examples.Read 7 Oct 2026 · leadflags.com
- Support
- The pricing page lists email support for Starter, fast support for Growth, priority support for Scale, and dedicated support for Enterprise.Read 7 Oct 2026 · leadflags.com
- Maker
- The About page describes why LeadFlags was built but does not state a maker name, headquarters, or founding date.Read 7 Oct 2026 · leadflags.com
- API access
- API requests use JSON and require an X-API-Key header; the docs say Bearer authorization is not yet supported.Read 7 Oct 2026 · leadflags.com
- Authentication
- API requests require an X-API-Key header obtained from the dashboard.Read 15 Oct 2026 · leadflags.com
- Bearer limitation
- Bearer authorization is documented as coming soon; X-API-Key is currently the supported method.Read 15 Oct 2026 · leadflags.com
- CRM positioning
- LeadFlags describes itself as CRM-agnostic and intended to sit before any CRM, call center or workflow.Read 15 Oct 2026 · leadflags.com
- Cross-field checks
- The API can flag mismatches such as name versus email, email domain versus website and source versus email type.Read 15 Oct 2026 · leadflags.com
- Custom thresholds
- Enterprise requests can pass mid and low query parameters to customize score cutoffs.Read 15 Oct 2026 · leadflags.com
- Deterministic scoring
- The documentation says identical input produces identical output using predefined, transparent rules.Read 15 Oct 2026 · leadflags.com
- Enterprise controls
- Enterprise plans list an IP allowlist, dedicated SLA and support, and custom score thresholds.Read 7 Oct 2026 · leadflags.com
- Features
- LeadFlags identifies signals such as missing or invalid contact details, disposable email, suspicious messages, and inconsistencies between fields.Read 7 Oct 2026 · leadflags.com
- Flexible input
- The API accepts JSON without a fixed schema, recognizes field aliases, and allows optional mapping overrides for nonstandard keys.Read 7 Oct 2026 · leadflags.com
- Flexible schema
- The API accepts arbitrary JSON without a fixed schema and detects fields through aliases.Read 15 Oct 2026 · leadflags.com
- Independent design
- The About page says the service operates independently from CRMs and marketing tools.Read 15 Oct 2026 · leadflags.com
- IP allowlist
- Enterprise can restrict accepted API traffic to authorized IP addresses.Read 15 Oct 2026 · leadflags.com
- JSON API
- The service exposes POST /api/score-lead and requires JSON request bodies.Read 15 Oct 2026 · leadflags.com
- Limit: API authentication
- Integrators cannot currently use Bearer authorization because the documentation says it is not yet supported.Read 15 Oct 2026 · leadflags.com
- Limit: no published licence
- The opened official documentation and About pages do not state an open-source licence or self-hosting option.Read 15 Oct 2026 · leadflags.com
- Limit: support guarantee
- The docs state ordinary email support has no guaranteed response time.Read 15 Oct 2026 · leadflags.com
- LinkedIn audience signal
- The public LinkedIn LeadFlags page showed one follower when the post was indexed.Read 15 Oct 2026 · linkedin.com
- LinkedIn launch
- LeadFlags’ LinkedIn post announces that the product is live as a deterministic lead-quality scoring API.Read 15 Oct 2026 · linkedin.com
- LinkedIn lock-in claim
- The launch post describes the service as having no CRM lock-in.Read 15 Oct 2026 · linkedin.com
- LinkedIn output
- The launch post says results include a normalized score, quality level, explanatory flags and a recommended action.Read 15 Oct 2026 · linkedin.com
- LinkedIn schema claim
- The LinkedIn post says the API has no fixed schema for inbound lead data.Read 15 Oct 2026 · linkedin.com
- LinkedIn stated use
- The LinkedIn announcement says the API is intended to filter low-quality, fake and spam leads before they reach pipelines.Read 15 Oct 2026 · linkedin.com
- Mapping overrides
- A reserved _leadflags_map object can map nonstandard payload keys to canonical fields.Read 15 Oct 2026 · leadflags.com
- Named CRM examples
- The product page names HubSpot and Salesforce as examples of systems that can receive routed results.Read 15 Oct 2026 · leadflags.com
- No AI enrichment
- LeadFlags states that scoring does not use AI, enrichment or profiling.Read 15 Oct 2026 · leadflags.com
- No CRM ownership
- The About page says LeadFlags does not manage pipelines, attribution or outreach.Read 15 Oct 2026 · leadflags.com
- Normalization endpoint
- The documentation describes a normalize-lead endpoint that reports detected fields, missing fields, conflicts and warnings.Read 15 Oct 2026 · leadflags.com
- Positive signals
- Positive outputs can identify business domains, consistent identity, quality messages and commercial intent.Read 15 Oct 2026 · leadflags.com
- Privacy approach
- The API documentation says geographic fields are used only for consistency checks and that LeadFlags does not profile leads.Read 7 Oct 2026 · leadflags.com
- Quality bands
- Scores map to strong, high, medium or low quality levels.Read 15 Oct 2026 · leadflags.com
- Rate limits
- The documentation gives example limits of 60 requests per minute for Starter, 300 for Growth and 1,000 for Scale.Read 15 Oct 2026 · leadflags.com
- Risk flags
- Documented risk checks include missing or invalid email, disposable email, missing or fake phone, suspicious messages and source problems.Read 15 Oct 2026 · leadflags.com
- Routing actions
- Recommended actions are high_priority, standard_priority, review or discard.Read 15 Oct 2026 · leadflags.com
- Scoring method
- The documentation says scoring uses predefined rules, produces the same output for the same input, and does not use AI, enrichment, or profiling.Read 7 Oct 2026 · leadflags.com
- Scoring output
- The API returns a score, quality level, risk flags, positive signals, and a recommended action for routing leads.Read 7 Oct 2026 · leadflags.com
- Support levels
- Starter has email support, Growth adds faster support, Scale has priority support and Enterprise lists dedicated support.Read 15 Oct 2026 · leadflags.com
- Supported lead fields
- Recognized data includes names, email, phone, messages, sources, country, job title, industry, company size and website.Read 15 Oct 2026 · leadflags.com
Plans and prices
Strong points and limits
Strong points
- Deterministic rules produce repeatable outputs
- Accepts flexible JSON without fixed schema
- Returns scores, flags, signals, and actions
- CRM-agnostic with HubSpot and Salesforce examples
- Annual billing offers a 20% discount
Limits
- No free plan
- Bearer authorization is not supported
- Starter limit is 1,000 leads monthly
- Enterprise pricing uses custom billing
Who it suits
LeadFlags suits marketing agencies, call centers, and lead sellers or buyers needing consistent rule-based screening before CRM or workflow routing. It fits teams that want API-based scoring without predictive modeling.
Verdict
LeadFlags provides transparent, repeatable screening through a flexible API and web service. Its paid plans scale by monthly lead volume, while authentication currently requires an X-API-Key header.
Where Specifiction places it
- Lead Scoring Software#8 of 248.2