For example this is how we both connect: https://zap.store/api/trust/npub1dtgg8yk3h23ldlm6jsy79tz723p4sun9mz62tqwxqe7c363szkzqm8up6m/npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9

(Give it a little time, it's slow right now)

Our connections with higher signal on our social graph are nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft and others (you follow them and they follow me)

Why an API, when all other approaches do it client-side? IMO makes no sense to pull a ton of data and heavy calculation client-side, certainly with less awareness of weights in the social graph. With this API you get a small number of npubs you can then pull contact lists from client side and verify the API is not bullshitting you.

I am currently working on making it way faster (will use a more specialized DB). Let me know if this interests you