Agents In Use
What’s new todayLast update
0 use cases added today

Grok Bot researches Italian family records

@APompliano says his Grok Bot genealogy researcher used family details to investigate Italian ancestors, wrote archive-request emails in Italian and found birth, marriage and tax records plus ship manifests.

Source published x.comHow we sourceAgent: Grok Bot
OUR ADAPTATION

Suggested prompt

Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.

Investigate my family history using the names, relationships, locations and stories I provide. Cite records, flag uncertain matches and ask before contacting archives.

Evidence at a glance

Sourced account
Source poster / publisher
@APompliano
Original account
Read the source ↗
Published
Source link checked
Reported result
@APompliano reports finding previously unknown relatives and fresh family-history details, supported by records the bot found. He identifies family connections to Sulmona and Trieste, Italy.
Human involvement
The poster created the bot, supplied family knowledge and set the research goal. Approval or sending checkpoints for correspondence and review of individual records are not described.

A linked account supports attribution. It does not mean we independently reproduced its result.

Report an issue with this caseOpen correction email

Opens your email app with the case link included. Nothing is sent automatically.

How the agent did it

  1. The poster created a Genealogist Bot using Grok Bot.
  2. He supplied names, relationships, locations and family stories, then asked for research as far back as possible.
  3. The bot wrote Italian emails requesting scans of physical records from Italian archive keepers.

@APompliano says he used Grok Bot to set up a "Genealogist Bot" to investigate his family history. He supplied names, relationships, locations and stories about older relatives who immigrated to America. His request was to go as far back through the family lineage as possible and report what it found.

The account describes the bot writing emails in Italian for archive record keepers in Italy, asking them to scan physical records and send them to him. He says the bot found marriage licenses, birth certificates, tax documents and ship manifests. The post does not specify which records came from those archive requests, so the discoveries should not all be attributed to replies from archivists.

He reports learning about previously unknown relatives and finding new details behind family stories, including connections to Sulmona and Trieste. These are his reported discoveries, not independently checked genealogical conclusions.

The human contribution was the initial family knowledge and the research goal. The capture does not describe approval checkpoints for correspondence, show the records themselves or explain how conflicting identities were resolved. It supports a firsthand account of agent-led archival research, without establishing that every family connection was verified.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: X · @APompliano

Frequently asked questions

What information did the poster provide?

He supplied names, relationships, geographic locations and family stories about older relatives who immigrated to America.

Which records did the bot reportedly find?

The poster lists marriage licenses, birth certificates, tax documents and ship manifests. He does not say which discoveries came from archive correspondence.

Did the source show the underlying records?

No. The capture reports the discoveries but does not include the records or explain how individual family connections were checked.

More details

Remaining steps

  1. The poster reports that the bot found marriage licenses, birth certificates, tax documents and ship manifests.

About this account

The bot pursued the family-history investigation and wrote Italian archive requests. The post attributes the record discoveries to the bot but does not map individual finds to archive replies.

Reviewed Scout's verbatim X public API capture supplied on 2026-11-01 in the 19:00 batch, including author bio and publication context. Used with explicit source permission; did not open X. No self-thread continuation was reviewed. Outcomes are self-reported, not independently reproduced. No exact task prompt was shared; the suggested prompt is an editorial addition.

Credit: @APompliano

Source published

Added to Agents In Use

Source checked

Tools and topics

Grok Bot · Email

Genealogy · Archives · Family history

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.