Contract
{
"type": "object",
"required": [
"email"
],
"properties": {
"email": {
"type": "string",
"description": "Email address to score"
}
},
"additionalProperties": false
}{
"type": "object",
"properties": {
"email": {
"type": "string",
"description": "The email address exactly as submitted, echoed back."
},
"domain": {
"type": "string",
"description": "The domain portion of the submitted email address."
},
"factors": {
"type": "array",
"items": {
"type": "object",
"properties": {
"detail": {
"type": "string",
"description": "Human-readable explanation of the signal."
},
"factor": {
"type": "string",
"description": "Short machine-readable signal name."
},
"impact": {
"type": "number",
"description": "Point contribution to reputation_score; observed both positive (10, 18) and negative (-40, -10)."
}
},
"additionalProperties": true
},
"description": "The individual signals that produced reputation_score, e.g. reputable provider, valid MX records, disposable domain, suspicious local part."
},
"risk_level": {
"type": "string",
"description": "Observed values: 'low' and 'critical'. Likely also takes intermediate values (e.g. 'medium'/'high') the two captured fixtures did not exercise -- treat as an open string, not a fixed two-value enum."
},
"email_valid": {
"type": "boolean",
"description": "Whether the address is syntactically valid and has a resolvable domain."
},
"provider_type": {
"type": "string",
"description": "Observed values: 'major_provider' (gmail.com) and 'disposable' (mailinator.com). Other categories are likely but unconfirmed by the two fixtures captured."
},
"reputation_score": {
"type": "number",
"description": "0-100 trust score. Observed 78 (low risk, gmail.com) and 10 (critical risk, a disposable domain) across the two fixtures captured."
}
},
"description": "The email reputation result, as returned at routing.responseResultPath ($.output).",
"additionalProperties": true
}Pricing
Every real charge, itemised. A model that quietly omits one is a slow financial leak, so nothing here is rolled up, and a charge that only applies to some inputs says so rather than being added in.
Prices in this catalog are the provider's own list price, not your bill: Omnial MCP charges provider cost plus a platform markup on top, so what you are charged is higher than the figure shown. For the exact amount a specific call will cost, run omnial_execute with dry_run: true; that number includes the markup and is what we hold while the call runs. It is a quote, not a cap on the charge.
| Charge | Rate |
|---|---|
Per call Flat, regardless of what comes back | $0.0486486 |
- Cost basis
- Not recorded
This tool's catalog entry does not record how its final bill is determined, so we will not tell you whether its cost is fixed before the call or reported by the provider afterwards. Either way what is held is a quote rather than a cap: you are charged what the call actually costs, bounded at 2x the quote.
- Updated
- Sep 23, 2026
