At this level
town.delve.contact ยท 9- town.delve.contact.defs defs not from the namespace authority Associates a profile with the positional index of the contact import input in the call to `app.bsky.contact.importContacts`, so clients can know which phone caused a particular match.
- town.delve.contact.dismissMatch procedure not from the namespace authority Removes a match that was found via contact import. It shouldn't appear again if the same contact is re-imported. Requires authentication.
- town.delve.contact.getMatches query not from the namespace authority Returns the matched contacts (contacts that were mutually imported). Excludes dismissed matches. Requires authentication.
- town.delve.contact.getSyncStatus query not from the namespace authority Gets the user's current contact import status. Requires authentication.
- town.delve.contact.importContacts procedure not from the namespace authority Import contacts for securely matching with other users. This follows the protocol explained in https://docs.bsky.app/blog/contact-import-rfc. Requires authentication.
- town.delve.contact.removeData procedure not from the namespace authority Removes all stored hashes used for contact matching, existing matches, and sync status. Requires authentication.
- town.delve.contact.sendNotification procedure not from the namespace authority System endpoint to send notifications related to contact imports. Requires role authentication.
- town.delve.contact.startPhoneVerification procedure not from the namespace authority Starts a phone verification flow. The phone passed will receive a code via SMS that should be passed to `app.bsky.contact.verifyPhone`. Requires authentication.
- town.delve.contact.verifyPhone procedure not from the namespace authority Verifies control over a phone number with a code received via SMS and starts a contact import session. Requires authentication.