Check the reputation and risk score of any email address via MPP micropayment.
What it does
This endpoint, hosted on the Locus MPP (Micropayment Protocol) gateway, wraps the Abstract API Email Reputation service. It accepts an email address and returns reputation and risk-score data for that address — useful for fraud prevention, signup validation, and lead qualification workflows.
The endpoint is a POST to `/abstract-email-reputation/check` and requires a JSON body with a single `email` field. Payment is settled per-call (intent: charge) via the Tempo L2 method using pathUSD. The advertised price is 6,000 base units of pathUSD (6 decimals), which equals $0.006 per request. The underlying API reference and additional documentation are available at Abstract API's docs site.
Note: The probe only tested HEAD and GET methods, both of which returned 404. The OpenAPI spec explicitly defines the endpoint as POST-only, so the 404s on HEAD/GET do not indicate the endpoint is down — they simply reflect that only POST is routed. The root domain also returns 404 with a helpful JSON message pointing to skill and llms.txt files, which is normal for Locus MPP gateways.
Capabilities
Use cases
- —Validate email addresses at signup to filter disposable or risky accounts
- —Score inbound leads by email reputation before routing to sales
- —Flag high-risk email addresses in fraud-prevention pipelines
- —Enrich CRM records with email reputation metadata
- —Gate access or features based on email trustworthiness
Fit
Best for
- —Agents needing per-call email reputation checks without API key management
- —Fraud and risk teams integrating email scoring into automated workflows
- —Developers who want pay-per-use pricing without monthly commitments
Not for
- —Bulk email list cleaning (per-call pricing adds up quickly at scale)
- —Full email deliverability testing including SMTP verification (scope is reputation/risk only)
Quick start
curl -X POST https://abstract-email-reputation.mpp.paywithlocus.com/abstract-email-reputation/check \
-H "Content-Type: application/json" \
-d '{"email": "user@example.com"}'Example
Request
{
"email": "user@example.com"
}Endpoint
Quality
The OpenAPI spec provides a clear request schema, pricing, and intent metadata. However, the probe did not capture a 402 challenge on the actual POST endpoint, no response schema is documented, and no example response is available. External docs links exist but were not crawled. The endpoint is likely live for POST but unconfirmed.
Warnings
- —Probe only tested HEAD/GET which returned 404; POST was not probed, so liveness for the correct method is unconfirmed.
- —No response schema is provided in the OpenAPI spec — the 200 response has only a description with no body schema.
- —Example response is unavailable; the actual shape of reputation/risk data is undocumented in the provided material.
- —External documentation at docs.abstractapi.com and beta.paywithlocus.com was not crawled.
Citations
- —The endpoint is POST-only and accepts a JSON body with an 'email' field.https://abstract-email-reputation.mpp.paywithlocus.com
- —Payment intent is 'charge' via 'tempo' method at 6000 base units of pathUSD ($0.006 per call).https://abstract-email-reputation.mpp.paywithlocus.com
- —Part of the Abstract API Email Reputation service.https://www.abstractapi.com/api/email-reputation-api
- —API reference documentation is available at docs.abstractapi.com.https://docs.abstractapi.com/email-reputation