VerifyPulse
Controlled scam-risk decision support

Explainable scam link and message risk intelligence for India-focused teams.

VerifyPulse helps customer-safety, support, lending, payment, and merchant teams assess suspicious links and messages with available evidence and clear next steps. It is designed to support—not replace—a client’s final fraud, payment, or regulatory decision.

Explore a controlled pilotRead current API documentation

What is available today

The production scanner uses multiple evidence paths. Each result is service-aware: a lack of live AI analysis is not presented as proof that submitted content is safe.

⌁

URL and message forensics

Checks can identify suspicious URL structure, brand-domain mismatch, credential/OTP pressure, payment pressure, and other scam signals.

◈

Historical reputation evidence

Known URL/domain evidence is checked against the maintained historical reputation index before live AI analysis is needed.

◎

Explainable result contract

Results can include risk level, confidence interpretation, evidence labels, recommended next steps, and an honest service-status boundary.

How a safer review flow works

01 — SubmitA user or support agent submits a suspicious URL or message.
02 — Check evidenceLocal forensics, historical reputation, and available enrichment are evaluated.
03 — Assist when availableExternal AI analysis may assist with ambiguous content within the request budget.
04 — Explain and routeThe result gives evidence and safe next steps; the client keeps its own final decision process.

Current B2B URL-scan API

The maintained B2B route currently accepts credential-free HTTP(S) URLs. It uses API-key authentication, scope checks, correlation IDs, and basic rate-limit headers. Broader integration modes should be agreed during a controlled pilot.

Request shape

POST https://www.verify-pulse.com/api/v1/scan
X-API-Key: YOUR_API_KEY
X-VerifyPulse-Key-Id: YOUR_KEY_ID
Content-Type: application/json

{
  "url": "https://example.com/suspicious-link"
}

Response boundary

{
  "correlation_id": "request-correlation-id",
  "status": "SUSPICIOUS",
  "threat_level": "MEDIUM",
  "scam_type": "Unknown",
  "confidence": 0,
  "message": "Analysis complete.",
  "action_steps": []
}
Important: The example fields show the supported B2B response shape, not a promised verdict for any particular URL. Do not use the result alone to automatically block a payment or account action.

Trust and pilot boundaries

Data and security discussion

Review the Trust Center for current input safeguards, B2B metadata-only operational events, and limits that are deliberately not overstated.

Risk-management discussion

Review Risk Management for degraded responses, evidence layers, and the boundary between VerifyPulse decision support and a client’s final controls.

Service transparency

The Status page shows exactly which public checks are visible and what each one does—not a hidden blanket uptime claim.

Start narrowly

A first controlled pilot should use one measurable scam-communication workflow and a pre-agreed limited capacity.

Business contact

For a controlled pilot or business API discussion, email narayanglokhande2007@gmail.com with the intended use case and approximate request volume. Fit, data fields, safeguards, and capacity are reviewed before onboarding.