Telo isn't new to this space. OpenCNAM has been around for nearly 5 years and EveryoneAPI was launched a year ago. We have just been doing some updates and now offer a free $0.50 trial.
Record availability probably would have been a better way to phrase it rather than speed. While I am not familiar with the latency of the FullContact API, I have experience a sort of fulfillment period (come back later) for records that require more sourcing efforts. That is unless that has changed. We focus on real-time responses that span nearly the entire NANPA dialing plan (US, Canada, Caribbean and part of Central America). In terms of the data-points and focus you are correct that our focus is on the data associated with the phone number query. We do plan to expand our phone coverage to international dialing plans outside of NANPA (NPA-NXX-XXXX) by the end of the year and will be offering a forward append service for name and address as well.
The site is back up. We had attempted a hotfix that did not deploy correctly to the front end. In terms of comparisons, while we do not like to mention competitors in a negative light, we can say that our data is returned in milliseconds. Additionally, our coverage is extremely accurate and built from authoritative sources. We also provide a more robust set of data-points that are not offered by those services.
We do not have that sort of collateral drafted yet, but it is something we would like to be able to offer folks such as yourself. Real time results are something that jumps out at me with respect to Full Contact. There are times where they do not have the record immediately and that can hinder some businesses depending on the use case. The added data-points offered is also something that stands out to me with respect to both. Perhaps the carrier or line provider data is important because you may need to know if a phone number is a Google Voice number. Or if you are looking for address and some bit of social data such as hometown or education, that might be a combination you can only find with EveryoneAPI.
As I mentioned we will be working to develop some collateral to that end. After well over 10 years in the data space I would say that the best way to compare is to do a batch > 1000 records head to head. :)
You shouldn't have encountered an issue with a 502 unless it was during the window of time where our front end deploy failed.
Unfortunately, we only support NPA-NXX-XXXX numbers for sign up at this time. If you contact us directly at support@telo.com, we can provision you an account if you are still interested. We plan on offering international coverage outside of the NANPA / NPA-NXX-XXXX dial plan by the end of the year.
Please standby. We attempted a hotfix for some user reported issues that did not deploy correctly. We will be back up in a minute or two. Sorry for the inconvenience.
Please standby. We attempted a hotfix for some user reported issues that did not deploy correctly. We will be back up in a minute or two. Sorry for the inconvenience.
Very useful and easy to understand API. I am working on a project in fraud detection and this data could be very useful if it is reliably available.
However, I tried with three different phone numbers and it gave an empty string for name, profile, gender, image, and address. Could you give a rough estimate of what percentage of phone numbers you able to provide this information for?
Please reach out to us directly if you are working on fraud mitigation. We have extensive insight into fighting fraud and the data that can be used to that end. Additionally, there is a special permissible use-case endpoint we are working on for specific business applications such as fraud mitigation. You may reach us at support@telo.com.
Record availability probably would have been a better way to phrase it rather than speed. While I am not familiar with the latency of the FullContact API, I have experience a sort of fulfillment period (come back later) for records that require more sourcing efforts. That is unless that has changed. We focus on real-time responses that span nearly the entire NANPA dialing plan (US, Canada, Caribbean and part of Central America). In terms of the data-points and focus you are correct that our focus is on the data associated with the phone number query. We do plan to expand our phone coverage to international dialing plans outside of NANPA (NPA-NXX-XXXX) by the end of the year and will be offering a forward append service for name and address as well.