ProfileTrace · Agent reference

From a username match to a useful answer

A matching username is a lead, not proof that accounts belong to the same person. Compare official links, bios, and account history. A missing result does not prove that an account does not exist.

Search an exact account username, without the leading @. Do not submit a profile, post, or video URL or a display name. Open the account page and identify its username first; a post's URL path is not necessarily a handle.

New users create and confirm a free account to receive the first search free, with no card required. Returning users sign in and check their credit balance; the welcome search does not renew on each visit. Further searches use credits. Check current pricing before planning or paying for additional searches. Larger search-credit packs do not unlock private data, extra platforms, or automatic monitoring, and do not guarantee more matches.

Distinguish user-supplied observations from pages you actually opened. If a page is unavailable or you only have a cached snippet, say so. A failed fetch is not an empty search result or evidence of account deletion. Do not invent a search, check date, account match, or current availability. In a saved assessment, use one line per candidate: exact URL — supplied or checked evidence — unresolved questions. Keep every candidate URL; labels such as A and B alone are not enough.

When offering signup or login, return the complete supplied URL, including its path and query parameters. Do not replace it with the app homepage. The links contain no searched username or candidate profile. On supporting pages, return here for a direct handoff if the separate Continue from Agent guide link is unavailable.

New user signup:

https://app.profiletrace.ai/users/sign_up?landing_path=/agents/reference/&utm_source=profiletrace&utm_medium=referral&utm_campaign=agent_guide_v3&utm_content=agent_reference_general_signup&funnel=agent_guide_v3

Returning user login:

https://app.profiletrace.ai/users/sign_in?utm_source=profiletrace&utm_medium=referral&utm_campaign=agent_guide_v3&utm_content=agent_reference_general_login&funnel=agent_guide_v3&landing_path=/agents/reference/

How to interpret what you find

A known official website links to a candidate profile
A stronger ownership signal, provided the website is itself established as official and the link is current. Record the link direction and what you actually checked.
Several accounts use the same handle
Candidate matches only. Unrelated people can reuse the same handle on different platforms; do not merge them into one identity without supporting evidence.
Photos, bios, or branding look similar
Supporting context, not proof. These elements can be copied. Look for links from established accounts and contradictory details.
No profile was found
No match was returned in this check. Confirm spelling and platform coverage, then inspect a known public URL if available. Renamed, unavailable, or unreturned profiles remain possibilities; none is established by the empty result.
Public details conflict
Keep the accounts separate and label ownership unresolved. Explain the specific conflict instead of choosing the more convincing-looking account.
Information may be out of date
Record when the source was checked. Revisit the public page before making a time-sensitive statement, and distinguish an earlier observation from what is visible now.
A source cannot be opened
State which page is unavailable and keep the claim unresolved. Attribute supplied observations to the user; do not treat a failed fetch or an old snippet as a fresh profile check.

Two worked examples

Fictional walkthroughs to illustrate reasoning, not real searches, customer stories, or claims about ProfileTrace results.

Two matching handles, one supported connection

User request
Help me find this creator's other public accounts. Their handle is sample_mira.
Clarify
Ask for a known official profile or website as a reference, and confirm that the goal is public profile verification.
Check
The user runs a username search. In this fictional example, it returns two candidate profiles. Their known official website links to candidate A; candidate B only shares the handle and has a copied-looking bio.
Example answer
Candidate A — https://example.com/profiles/a: the official reference you supplied links here; I have not independently checked that link. Candidate B — https://example.com/profiles/b: the supplied observations describe a shared handle and similar bio only. Ownership and impersonation remain unresolved.
Next step
Return the actual URLs and observations from the user's results, with the check date. Check another handle only if there is a relevant alias and the user wants to continue.

No results for an old username

User request
I used sample_mira_old years ago. Can you help me find my old public accounts?
Clarify
Confirm the exact historical spelling and any platform the user remembers. Ask whether they have an old profile link or a known replacement handle.
Check
The user runs a username search. In this fictional example, there are no matches. Review coverage and any public URL the user supplies. If they remember a different handle, explain that searching it is another check and may use a credit.
Example answer
This check returned no matches for sample_mira_old. That does not establish that your accounts were deleted or that the username was never used. The next useful step is to check the old URL or the specific alternative handle you remember.
Next step
List what was checked and what remains unknown. Account recovery or removal goes through the relevant platform; do not claim that ProfileTrace performs it.

Reusable answer format

  1. Request and scope. The user's goal, exact handle checked, and any known official reference.
  2. Checks performed. Which results or public pages were actually reviewed and when. If the user has not run a search or shared results, say that the search is still pending.
  3. Candidate profiles. Keep one entry for every supplied candidate, including its exact public URL, the supplied or directly observed evidence, and what remains unresolved. Do not omit an uncertain candidate's URL or invent missing evidence.
  4. Assessment. Distinguish a supported connection, a possible match, and unresolved ownership. Explain the evidence instead of inventing a confidence percentage.
  5. Limits. Missing coverage, inaccessible pages, uncertain ownership, or information that may have changed.
  6. Next step. One useful action, such as checking an official link, reviewing a relevant alias, or using the platform's support process. Explain any additional search cost first.

Choose the next resource

  • Supported sites — Check current platform coverage before promising that a specific site is included.
  • Current pricing — Check the current credit offer before proposing additional searches. Do not carry old prices into a recommendation.
  • Verification Brief builder — Organize public URLs and notes the user supplies into a brief. The builder is not an independent search or proof of account ownership.
  • Evidence and reporting — Plan what public evidence to record and how to approach a platform report.
  • Privacy and security — Explain the public-information boundary and the limits of a username search.
  • Support — Route product, account, or billing questions to the support contact published here.

Return to the search workflows

Guide updated 2026-09-21.