You've already done the hard part.

You already have the companies. We find the person most likely to answer — the one a BDR can write, the one a floor can dial — we knock on the mailbox or the line, and we charge you when someone is home.

The address goes through MillionVerifier. We only mark it sendable when the result is ok and the quality is good, and when the identity gate ties that person to that domain.

The receiving mail server accepted the mailbox during verification. It is evidence the address resolves, not evidence the person reads it.

A last check that the name we found and the address we built belong to the same company as the domain you sent. It is why some verified addresses still come back not sendable.

You get a no-find: an empty result, and no credit committed. Nothing is queued for later.

No. Credits are committed per delivered row — email 2, phone 4, both 8. The reservation for missing or discarded rows is released.

Yes, twenty is the maximum per call. The call reserves the row meter for those domains and commits only delivered rows.

Either the verifier graded it below good, or the identity gate did not match. That candidate is discarded and not billed.

You send companies you already have. We return one person per domain.

Company domains you already have, and whether you need email, phone, or both. A number on the row still needs your own clearance to dial.

The companies are already on the campaign sheet. When you ask for phone we come back with the person who can say yes and a work number we classified. The headset still needs your own clearance. A miss does not bill, and a dead morning on a bought list is what we are trying to spare you.

No. It works from any company domain; there is no vertical assumption in the lookup.

Around forty seconds is typical for a batch, and the call is synchronous. Set a client timeout of forty-five to sixty seconds.

The call answers 402 with the required and available amounts before anything runs. Buy credits from Packs and retry the same request.