Technical and developer support
VerifIP and DetectBT integration, rate limits and billing. First reply within 4 hours on Growth and Scale, 1 business day on Starter, no response target on Free.
contact@hextner.comEmail supportSales and custom plans
Volume pricing, custom rate limits, security questionnaires and procurement. We aim to reply within one business day.
contact@hextner.comContact salesFrequently askedquestions
The things engineers ask before wiring detection into a live product.
Integration is one HTTPS call from your server for VerifIP, and one script tag plus a server-side /verify call for DetectBT. The free tier is enough to try both on production traffic before you commit.
VerifIP is one HTTPS call, built to sit in the request path. If we cannot answer, you get an explicit 503 (X-VerifIP-Degraded) instead of a guessed verdict. The docs show a bounded retry followed by failing closed, and a 10-second client timeout keeps a slow network from hanging your request path. DetectBT does the opposite by default: if it cannot score a visitor, your server lets the request through, flagged.
Queried values (IP, email, phone, URL) are stored in your request logs for 90 days so you can review them in the console, then deleted. We do not build a cross-customer profile of anyone.
Yes. VerifIP and DetectBT are separate calls, priced separately. Use one, or call both on the same request and combine the two answers in your own code.
Neither product gives you a bare yes or no. Every VerifIP answer carries its signal_breakdown, the signals behind the score; DetectBT gives your server the verdict, a risk_score and the reason. Set your own thresholds in your own code.
VerifIP API requests beyond your plan's quota are refused with HTTP 429 until the quota resets or you upgrade. DetectBT never refuses your visitors: after a short grace allowance, evaluations pass through unscored. You are never charged more than your plan price.