--- title: Supported sources — PeopleBlade description: Supported PeopleBlade contact sources, exact capability boundaries, and availability status. canonical_url: https://peopleblade.com/sources last_updated: 2026-09-11T00:00:00.000Z --- # Supported PeopleBlade sources > Public CLI · npm 0.4.1 PeopleBlade combines local contact stores, reviewed Ghostget projections, and official owner archives in one source-aware SQLite graph. “Supported” does not mean “unbounded”: each path below names what enters the graph, what stays out, and whether it is ready now. ## Beeper, clearly bounded Contacts and candidate search are ready through Ghostget's pinned adapter 2.4.0 on macOS and Linux. `contacts.search@1` uses the pinned official Beeper CLI 0.6.2; `contacts.list@3` and `messaging.search@2` use fixed Desktop-loopback reads. Read-only in PeopleBlade. It never sends messages or imports message bodies, attachments, reactions, media, credentials, or local paths. Body-free interaction counts are a separate limited capability: macOS arm64 only, exporter 1.1.0, and complete one-to-one conversations only. The counts may understate history. A history participant absent from the current contact page remains a distinct relationship-only resource under its exact account-scoped coordinate; PeopleBlade never joins it by name or another fuzzy field. Ghostget supports broader Beeper messaging and actions; PeopleBlade exposes none of those mutations. Adapter pin: Ghostget 0.18.13 · `beeper-local` 2.4.0. CLI route: `contacts.search@1` · Beeper 0.6.2. Desktop routes: `contacts.list@3` · `messaging.search@2` · fixed loopback. Limited interaction coordinate: exporter 1.1.0 on macOS arm64. [Review Ghostget's public Beeper guide](https://ghostget.com/providers/beeper/) or [read PeopleBlade's product boundaries](https://peopleblade.com/about.md). ## Source directory ### Apple Contacts — Ready Reads the Mac's local Address Book as a consistent contact snapshot. Each Apple contact is authoritative. Two Apple cards that share a field stay separate until a person reviews them. - Path: Local database - Availability: macOS · Full Disk Access may be required - Capabilities: Contacts, Structured fields, Local reconciliation ### iMessage — Ready Builds interaction history from content-free Messages metadata already on the Mac. Only exact normalized email or phone handles can link. Message bodies are never read. - Path: Local metadata - Availability: macOS · local Messages database - Capabilities: Interaction counts, Reciprocity, Last contact ### Google Contacts — Ready Syncs saved Contacts and Other contacts as separate, fully paginated collections. The contact-only projection never scans Gmail or reads message bodies. - Path: Official API via Ghostget - Availability: Google contact scopes · Ghostget authorization - Capabilities: Saved contacts, Other contacts, Dates and events ### Beeper — Ready Imports account-aware contacts and stages bounded contact or conversation candidates for explicit review. Read-only in PeopleBlade. It never sends messages or imports message bodies, attachments, reactions, media, credentials, or local paths. - Path: contacts.search@1 via pinned official Beeper CLI 0.6.2 · contacts.list@3 + messaging.search@2 via fixed Desktop-loopback reads - Availability: Beeper Desktop and pinned CLI on macOS or Linux - Capabilities: Contacts, Candidate search - Operation route: `contacts.search@1` — Pinned official Beeper CLI 0.6.2 - Operation route: `contacts.list@3` — Fixed Desktop-loopback read - Operation route: `messaging.search@2` — Fixed Desktop-loopback read - Limited capability: Body-free interaction counts — macOS arm64 only. Separate bounded exporter 1.1.0; complete one-to-one conversations only, so counts may understate history. - Reviewed coordinate: Ghostget 0.18.13 · adapter 2.4.0 · Beeper CLI 0.6.2 ### WhatsApp — Ready Syncs exact account-scoped contacts and lower-bound interaction metadata. Display-name overlap never merges identities; a shared exact phone joins records only through a recorded identity decision. Message bodies are not imported. - Path: Linked device via Ghostget - Availability: User-approved linked-device pairing - Capabilities: Contacts, Interaction counts, Linked-device sync ### LinkedIn — Ready Imports connections and body-free message-participant metadata from the official ZIP export, then reads one imported connection's Contact info through Ghostget from your signed-in browser profile. Exact member profile URLs anchor identities. Names alone never do. Connection lists are never collected from a signed-in browser. - Path: Official data archive - Availability: Owner-supplied LinkedIn ZIP - Capabilities: Connections, Exact profiles, Message participants, Contact info ### Instagram — Ready Imports reviewed relationship, message-participant, and synced-contact paths from Accounts Center JSON. Archive records may be structurally parsed and integrity-hashed; message text is not retained. Names alone remain unresolved. - Path: Official data archive - Availability: Owner-supplied Accounts Center JSON archive - Capabilities: Relationships, Participants, Synced contacts ### X data archive — Bounded metadata Builds a graph from account, follower, following, and body-free interaction coordinates. Unresolved numeric peers stay inert evidence. Post and direct-message bodies are not persisted. - Path: Official data archive - Availability: Owner-supplied X data archive - Capabilities: Followers, Following, Body-free graph metadata ### X live mutuals — Blocked safely Reserved for a future bounded, account-bound mutual-follow capability. No API or scraping fallback exists while an exact reviewed Ghostget operation is unavailable. - Path: Not enabled - Availability: Unavailable until a bounded Ghostget route exists - Capabilities: No live import ### Telegram — Validation pending A strict Telegram Desktop JSON importer is designed but not yet enabled. Support waits for validation against a real owner-supplied export artifact. - Path: Not enabled - Availability: Unavailable pending a real export fixture - Capabilities: Artifact validation TODO ## Why the boundaries matter - **Local authority.** The full graph lives in SQLite on your machine; optional cloud sync is a bounded projection. - **Source-aware identity.** Exact provider coordinates can anchor a person. Names, fuzzy candidates, and unverified handles cannot. - **Inspectable import evidence.** Each run records its source, completeness limits, and implementation version. ## Sitemap See the full [markdown sitemap](https://peopleblade.com/sitemap.md) or the [XML sitemap](https://peopleblade.com/sitemap.xml).