Skip to main content
Human guide: work with your agent → Find a LinkedIn profile candidate, then verify that it identifies the intended person. This task ends with an accepted URL or a documented unresolved match.

​
Before you start

Keep the person’s known name, company, domain, email, and location where available. Distinguish known evidence from guesses. More candidates do not necessarily mean stronger identity evidence.

​
1. Discover a route for the inputs you have

Inspect a returned identifier with deepline describe <returned-id> --json. Read its required inputs and result shape. Do not infer a fixed Google, Apollo, or scraper chain from the requested outcome. For reverse lookup, search with the actual input type, such as an email. Inspect the corresponding contract before running it.

​
2. Ask for one bounded candidate review

Supply the known identity separately. If custom code is needed, check that Play before running the pilot. Use the authoring guide.

​
3. Evaluate the candidate

Compare the returned person and company evidence with the supplied identity. A matching name alone is insufficient for a common-name case. Name variants expand the search. they do not verify a person. Preserve conflicting candidates for review. Do not turn the first search result into a confirmed profile without the required evidence.
The accepted URL and supporting identity refer to the intended person. Otherwise, keep an unresolved result with the missing or conflicting evidence.
Only then use the URL in a work-email lookup. Ask your agent which evidence resolved the identity before expanding to a file.