Email Headers
Read raw email headers and find sender spoofing.
Call it
The first response is 402 with the exact price and every rail you can
pay with. Pay, repeat the request with the proof, and you get the result.
curl -X POST https://api.glianalabs.com/v1/tools/email-headers \
-H 'content-type: application/json' \
-d '{"headers":"From: Billing <[email protected]>\nReturn-Path: <[email protected]>\nAuthentication-Results: mx.example.org; spf=pass; dkim=pass; dmarc=fail"}'When to use it
Use when an agent triages a suspicious message, or checks whether a notification really came from who it claims. Inputs: headers (required - the raw block, up to 100,000 characters). Returns From, Return-Path, Reply-To and their domains, the DKIM signing domain, the SPF/DKIM/DMARC verdicts recorded by the receiving server, the Received hop count, and findings[]. The important part is ALIGNMENT, not pass/fail: SPF can pass for an envelope domain the reader never sees while the visible From is someone else, which is the mechanic behind most display-name spoofing. Authentication-Results is written by the receiving server, so a forged block can claim anything.
What it costs
$0.0030 per successful call — flat, with no plan, minimum or monthly fee. A call that fails validation is refused before it runs, so it is never charged.
Not sure this is the right endpoint? GET /v1/consult?intent=… is
free and answers that.
Often used with this
Email Verify
$0.0020Check an email address can receive mail, without sending any.
Osint Brief
$0.0120Profile a contact or an organisation from open sources, in one call, and say why it looks the way it does.
Domain Lookup
$0.0020Who registered a domain, how old it is, and where its DNS points, in one call.