Page Questions and Answers - Just 1 click away
Turn web pages into quick, repeatable decisions. Configure questions once, run them on matching pages, and review focused answers in the browser popup.
Use cases · How it works · Example · Get started · Privacy
Page QnA is decision support, not a source of verified facts. Check important answers against the original page.
Create a question set for a website and run it on matching pages. For example:
- Job application screening: Scan many postings for clearance requirements, experience thresholds, work location, travel, or relocation to focus on roles worth pursuing.
- Resume-to-job matching: Compare a job description with your background. Check for required skills such as Python, Java, or SQL, the expected career level, and required certifications or degrees.
- Academic research: Review papers for methodology, experimental versus observational design, sample sizes, datasets, funding statements, or conflict-of-interest disclosures.
- Real estate comparison: Check listings for HOA fees, pet policies, FHA approval, financing requirements, and stated insurance or flood-risk concerns.
- Events and opportunities: Review conferences, events, or grants for open deadlines, in-person or virtual format, fees, scholarships, and eligibility requirements.
- Candidate qualification: Help recruiters compare applicants with role requirements, including certifications, minimum experience, work-region eligibility, and relevant background.
- Travel and booking comparison: Compare flights, hotels, or rentals for free cancellation, baggage restrictions, included breakfast, policies, and fees.
These are examples, not preloaded question sets. You create the questions and criteria that fit your needs.
- Save your Jev API key in Page QnA's Setup page.
- Create a question set for a website domain. Optionally add a CSS selector to target the relevant page section and additional context for your questions.
- Open a page on that domain and click the Page QnA toolbar icon.
- Page QnA reads the selected page text and sends it, your additional context, and your questions to the TypeSafe API.
- Review the answers in the popup, alongside the questions they address.
Each website can have its own question set. If a page's domain is not configured, Page QnA tells you so instead of running an unrelated set of questions.
Page QnA supports TypeSafe's three question primitives:
- Choice: Choose one answer from a list you define, such as
remote,hybrid, oronsite. - Score: Rate the page against an ordered scale, such as
poor,partial, orstrong. - Noul: Judge a yes/no statement, with optional criteria describing what should count as yes or no. The result can be uncertain; a negative answer means the page did not support the statement, not necessarily that the statement is false in the real world.
Write focused instructions and distinct criteria. When absence of a statement matters, ask whether the page explicitly mentions it. For example, “Does the listing explicitly say sponsorship is unavailable?” is safer than inferring sponsorship policy from silence.
See TypeSafe's primitives documentation for details on question types and criteria.
Adapt questions like these to the role and the details you want to compare:
| Question | Type | Example criteria |
|---|---|---|
| Does the posting explicitly require security clearance? | Noul | Define what counts as yes and no |
| Is there an explicit 3+ years of experience requirement? | Noul | Define what counts as yes and no |
| Is the role remote, hybrid, or onsite? | Choice | remote, hybrid, onsite, unspecified |
| Does the role require travel or relocation? | Noul | Define what counts as yes and no |
| How closely does this role match my target role? | Score | poor, partial, strong |
Ask whether a page explicitly states a requirement instead of treating missing information as proof that the requirement does not apply. Keep each question focused and make answer criteria distinct.
- Install or load Page QnA in your browser, then click its toolbar icon. If it has not been configured, the Setup page opens.
- Add your Jev API key in the Setup tab. You can get a key from the TypeSafe console.
- Open the QnA tab and create a website configuration. Enter the hostname, such as
linkedin.com, rather than a full URL with a path. - Add your questions, instructions, and criteria. A question set can include Choice, Score, and Noul questions.
- Optionally add a CSS selector to limit extraction to the relevant part of the page. Without one, Page QnA uses the page's available text. You can also provide additional context to apply to the questions.
- Save the configuration, open a matching page, and click the Page QnA icon to run it.
Selectors are specific to a site's page structure and may stop working when that site changes. Test a selector on a representative page; remove or revise it if the extracted text is incomplete.
This repository provides source builds for Chromium-based browsers and Firefox. With Node.js and npm installed:
npm install
npm run devFor Firefox development, use npm run dev:firefox. To create production builds, run npm run build or npm run build:firefox. WXT build output is written to .output/.
- When you run Page QnA, it reads text from the active webpage, using your configured selector when present and otherwise the page's available text.
- The extracted text, your configured questions, and any additional context are sent to
https://api.typesafe.aifor processing. Do not use Page QnA on pages containing information you do not want to send to an external service. - Your Jev API key and configurations are stored in local browser extension storage. Access is restricted to trusted extension contexts, but this is not encryption against someone with access to your browser profile or extension pages.
- Answers depend on the page text available to Page QnA and how clearly questions are written. Missing information, ambiguous wording, or page changes can affect results. Verify high-impact decisions using the original source.
- No questions are configured: Open Setup, select QnA, and add or check the configuration for the page's hostname.
- The answer misses relevant details: Confirm the text is present on the page, adjust the CSS selector, and make the instructions and criteria more specific.
- The request fails: Check your internet connection and Jev API key, then try again. The API key must be configured before Page QnA can answer questions.
