AI Tools

Using Perplexity for AI-Powered Research

Published Nov 9, 2026

Find tool documentation, inspect citations, and build an evidence table instead of copying an automated answer.

Overview

For learners who want to complete this practical exercise with inspectable sample data and explicit checks.

Define a bounded question and an access date.
Distinguish primary sources, secondary reporting, and marketing.
Record conclusions with their evidential limits.

You will build: A three-source official evidence table for a workplace tooling decision.

Prerequisites

A browser, Perplexity access, and a spreadsheet or Markdown editor.

Use ordinary search for this exercise. Pro Search/Research is optional and subject to account limits or payment; purchasing access is unnecessary.

Step-by-step tutorial

Conceptual practice workflow; not measured results.

Step 1. Choose a verifiable question

Example: a team needs to understand Copilot setup in VS Code and TXT-file input in an AI assistant. Research setup requirements rather than unsupported “best tool” rankings. Record the date you actually inspect each source because interfaces and plans change.

PROMPT · INSTRUCTIONS

Find official documentation for (1) setting up GitHub Copilot in VS Code and (2) Claude’s supported files. For each, give the primary URL, access prerequisites, and unresolved questions. Prefer vendor documentation rather than roundup blogs as final evidence.

Step 2. Open citations and read the context

Open each citation in a separate tab. Check the domain, product name, and whether the passage actually supports the claim. A real Visual Studio page does not establish VS Code setup. Mark blocked sources as inaccessible instead of filling gaps from memory.

Step 3. Build your own evidence table

TEXT

claim | official_url | supporting_section | accessed_on | unresolved
VS Code sign-in | <verified URL> | <section heading> | <actual date> | account limits
Claude file input | <verified URL> | <supported formats> | <actual date> | plan limits

The <...> markers are fields to fill after opening sources, not supplied URLs or facts. Keep one checkable claim per row. Add a third official source if account conditions need separate confirmation.

Step 4. Request a bounded synthesis

PROMPT · INSTRUCTIONS

From my checked evidence table, write a note of at most 150 words: verified findings, unknowns, and the next practical trial. Do not infer free features or quotas when the source does not specify them. Keep each relevant source URL next to its claim.

Expected result

Deliverable: an evidence table, an access date per source, and a short decision note.
No fabricated benchmark, quotation, or citation.

Verification

Each conclusion points to a supporting source passage.
Old, inaccessible, and unverified material is clearly marked.

Troubleshooting

A citation does not support the answer

Cause: The synthesis goes beyond its source.

Fix: Narrow or remove the claim and find adequate evidence before using it.

Results are mostly promotional

Cause: The question is broad or does not prioritize primary sources.

Fix: Specify the vendor and request documentation URLs; inspect each source independently.

Exercises & extensions

Compare two differently scoped searches and note which evidence changes.
Reuse the table in the research-assistant tutorial to build a small source collection.

Citations make checking possible; they do not prove correctness. Actual results depend on the query, access, and time.