You may want to think about allowing the hash of the email to be sent so that PII isn't being transported.
It’s doing real time research so might be a bit tricky with a hash. Can you see a way around that?
Show HN: Yolodex – real-time customer enrichment API
21–25 of 25 posts
Re: Show HN: Yolodex – real-time customer enrichment API
#22let me know what use cases you have. i can update a tweak accordingly if it makes sense. anything goes. almost anything. nothing illegal.
thanks for the feedback
Re: Show HN: Yolodex – real-time customer enrichment API
#23I tested my main email account, and it found the wrong country, and in that country the wrong person (wrong name). Then I tested the email address of my boss, where it found a few fields of the company (address and business type), but not the person. Then I tried a complete bogus address and still got a "success" but without meaningful data: { "success": true, "email": "hjd28ebsgis63kdnrzdg@gmail.com", "enrichment_da…
Some work to do on precision and recall. Thanks for testing it out. Hah yes 2024 llm sounds right. I’m interested in what you think you’d use it for if you don’t mind sharing, and what you would benchmark it against.
I would use this to determine how likely a given email address will receive my mail. I build websites, where people create accounts and an awful lot of them provide unroutable email addresses. This is annoying for me and for the users. If I could give them a warning like "this email address looks like it isnt usable, are you sure?".
Re: Show HN: Yolodex – real-time customer enrichment API
#24Earlier quoted context omitted.
Some work to do on precision and recall. Thanks for testing it out. Hah yes 2024 llm sounds right. I’m interested in what you think you’d use it for if you don’t mind sharing, and what you would benchmark it against.
I would use this to determine how likely a given email address will receive my mail. I build websites, where people create accounts and an awful lot of them provide unroutable email addresses. This is annoying for me and for the users. If I could give them a warning like "this email address looks like it isnt usable, are you sure?".
Yes the coverage is not going to be near 100% so you’d get a lot of anger with this use case. There are some libs that will check via smtp if they are likely reachable, and some services. Is “verify your email” and option ie sending an email on signup as part of the signup flow an option?
Re: Show HN: Yolodex – real-time customer enrichment API
#25[dead]