Defastra API

Name: Defastra API API
Brand: Defastra API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey2 EndpointsREST

For Agents

Score the fraud risk of an email address or phone number with deep enrichment checks covering deliverability, disposable detection, and social signals.

Quickstart

Get started with Defastra API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"check fraud risk of an email address"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Defastra API API.

Score the fraud risk of an email address with deep checks via POST /deep_email_check

Score the fraud risk of a phone number with deep checks via POST /deep_phone_check

Detect disposable or temporary email addresses during signup

Surface social and reputation signals attached to a phone number

GET STARTED

Start building with Defastra API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Defastra API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Defastra API, keeping it validated and agent-ready. Defastra is a fraud detection and risk-scoring service that runs deep checks against email addresses and phone numbers to surface signals such as disposable status, social presence, deliverability, and reputation. The API is intentionally narrow with two POST endpoints, one for email and one for phone, each returning a structured risk profile. Authentication is by API key passed in a header, making it well suited for synchronous calls during signup, checkout, and account-takeover screening.

Use Cases

Patterns agents use Defastra API API for, with concrete tasks.

★ Signup Fraud Screening

Block disposable, throwaway, or high-risk email signups before they create accounts. POST /deep_email_check returns a risk score plus signals like disposable status, deliverability, and social footprint, so the application can challenge or reject suspicious registrations within a single synchronous call.

Call POST /deep_email_check for an incoming signup email and reject the registration if the returned risk score exceeds the configured threshold.

Checkout Risk Decisioning

At checkout, score the supplied email and phone number to feed a fraud decision engine. Defastra returns deep signals beyond simple syntax validation, helping merchants distinguish stolen credentials from genuine customers without adding friction for low-risk orders.

Call POST /deep_email_check and POST /deep_phone_check for a checkout payload and route the order to manual review when either score is high.

Lead Quality Enrichment

Enrich inbound leads from forms or campaigns by running each contact through deep email and phone checks. Sales teams get a quality score and social context per lead, allowing low-quality records to be deprioritised before they hit the CRM.

For each new lead, call /deep_email_check and /deep_phone_check, then attach the returned scores and social signals to the CRM record.

AI Agent Integration via Jentic

An agent investigating a suspicious account can call Defastra through Jentic to get a structured risk view of the user's email and phone. Jentic resolves the API key from the vault and returns the scored response in one step, so the agent can incorporate the verdict directly into its reasoning.

Use Jentic to search for 'check fraud risk of an email', load the deep_email_check operation, and execute it for a user-supplied email.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for defastra api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/deep_email_check

Run deep fraud checks on an email address

POST

/deep_phone_check

Run deep fraud checks on a phone number

POST

/deep_email_check

Run deep fraud checks on an email address

POST

/deep_phone_check

Run deep fraud checks on a phone number

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Defastra API keys are stored encrypted in the Jentic vault. The agent calls the operation by name and Jentic injects the header at execution time, keeping the secret out of prompts and logs.

Intent-based discovery

Agents search for intents like 'check if an email is fraudulent' and Jentic returns the matching Defastra operation with its input schema, so the agent fills in the email or phone and executes.

Time to first call

Direct Defastra integration: a few hours to wire the API key, error handling, and a thin client. Through Jentic: under 15 minutes from search to first scored email.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

AbstractAPI

Suite of validation APIs covering email, phone, and IP risk in separate endpoints.

Choose AbstractAPI when you also need IP reputation, address validation, or holiday data alongside email and phone checks.

Complementary

Hunter API

Email finder and verifier focused on B2B prospecting rather than fraud scoring.

Use Hunter when the goal is finding or verifying business emails for outreach, not fraud screening.

Alternative

Emailable API

Email verification service with deliverability checks and bulk list cleaning.

Choose Emailable when bulk list verification and SMTP-level deliverability checks matter more than fraud risk scoring.

Alternative

Numverify API

Phone number lookup and validation focused on carrier and line type.

Choose Numverify when you only need carrier, country, and line-type validation rather than fraud risk signals.

FAQs

Specific to using Defastra API API through Jentic.

Why is there no official OpenAPI spec for Defastra API?

Defastra does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Defastra API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Defastra API use?

The Defastra API uses an API key passed in a request header. Through Jentic, the key is stored encrypted in the vault and injected at execution time, so the raw secret never enters the agent's prompt or memory.

Can I detect disposable email addresses with the Defastra API?

Yes. POST /deep_email_check returns disposable-email indicators alongside deliverability and social-presence signals, so signup flows can flag throwaway addresses in a single call.

Does the Defastra API check phone numbers as well as emails?

Yes. POST /deep_phone_check accepts a phone number and returns risk signals including reputation, social footprint, and validity. The two endpoints are usually used together for combined identity screening.

How do I screen a signup email through Jentic?

Run `pip install jentic`, search for 'check fraud risk of an email', load the /deep_email_check operation, and execute with the email value. Jentic returns the structured risk response your agent can act on.

What are the rate limits for the Defastra API?

The OpenAPI spec does not declare hard rate limits, so applied limits depend on your Defastra plan. Treat each /deep_email_check and /deep_phone_check call as billable and cache results for repeat lookups within a session.