SERCH is the search Utah uses: one search box over the web and over security, code and research sources, with a cited answer when you ask for one. There are no ads and no trackers. Open it at https://aithatsee.com/serch. https://aithatsee.com/search opens the same page.
Suggestions under the box come from public data only (Wikipedia titles, SERCH’s own index and CVE ids in the CISA KEV catalog), never from other people’s searches.
Lenses
Under the box, a lens chooses which kind of source to search:
- All, the default: the sources follow what you asked. A CVE id goes to vulnerability records and a package name to package registries.
- Security: vulnerability records and catalogs.
- Docs: documentation.
- Code: repositories, packages and programming discussion.
- Papers: research papers and preprints.
- News: recent reporting and discussion.
- Forums: discussion threads.
When a query names a technology, its official documentation ranks first, whichever lens is on. On a results page you can also keep only recent results: Past day, Past week, Past month, Past year or a Custom range. Results without a stated date are then left out, and a notice says how many.
| Lens | Sources, as SERCH lists them now |
|---|---|
| All | Wikipedia, Mwmbl, Wiby, Hacker News, General web (background) |
| Security | CVE.org, OSV, CISA KEV, ENISA EUVD, MITRE |
| Docs | npm, DevDocs, Read the Docs, Error code references |
| Code | Hacker News, GitHub, npm, crates.io, PyPI, Maven Central, DevDocs, Read the Docs, Error code references |
| Papers | arXiv, Crossref, OpenAIRE, Europe PMC |
| News | Hacker News, GDELT (background), SERCH news index, General web (background) |
| Forums | Hacker News |
SERCH index, SERCH’s own index of public pages it has read, answers in every lens. The !facts bang searches Wikipedia and Wikidata. Sources marked “background” are slower, so SERCH does not hold the first results back for them.
Operators
Operators go in the search box with your words:
| Operator | What it does |
|---|---|
site:example.com | Only results from that site. A path narrows it (site:example.com/docs) and *. takes in every subdomain (site:*.gov). |
-site:example.com | Leaves that site out. |
"exact phrase" | Only results with those words, in that order. |
-word -"a phrase" | Leaves out results that contain it. |
filetype:pdf ext:pdf | Only files of that type. |
before:2024 after:2024-03 | Only results published or updated before or after a year, a month (YYYY-MM) or a day (YYYY-MM-DD). |
intitle:word | The word is in the page title. |
inurl:word | The word is in the page address. |
OR | | Either word. |
\ at the start | Goes straight to the first result. |
Identifiers, code and punctuation, such as CVE-2024-3094, tokio::spawn or libxz.so.5, are matched exactly and never spell-corrected.
Bangs
A bang is a word that starts with !, anywhere in your search. These keep you on SERCH and choose a lens or a source:
| Bang | Searches |
|---|---|
!cve !sec !security | The Security lens |
!nvd | CVE.org, OSV, KEV and EPSS for a CVE |
!kev | The CISA Known Exploited Vulnerabilities catalog |
!osv | The OSV vulnerability database |
!ghsa | GitHub advisory ids, through OSV, NVD and CVE.org |
!gh !github | SERCH’s GitHub repository results |
!npm | npm packages, with the package panel |
!pypi !pip | PyPI packages, by exact name |
!crates !cargo | crates.io |
!mdn | MDN, through the documentation index |
!se !stackexchange | The Forums lens |
!code | The Code lens |
!docs | The Docs lens |
!forums | The Forums lens |
!w !wiki !wikipedia | Wikipedia |
!wd !wikidata | Wikidata |
!facts | The Facts lens |
!arxiv | arXiv |
!papers !scholar | The Papers lens |
!doi | Crossref, to look up a DOI |
!openalex | The Papers lens |
!hn | Hacker News |
!news | The News lens |
!own | SERCH’s own index only |
These send your search to another site:
| Bang | Goes to |
|---|---|
!g !google | |
!b !bing | Bing |
!ddg !duckduckgo | DuckDuckGo |
!brave | Brave Search |
!sp | Startpage |
!yt !youtube | YouTube |
!maps !osm | OpenStreetMap |
!wa | Wolfram Alpha |
!r !reddit | |
!a !amazon | Amazon |
!gs | Google Scholar |
!so !stackoverflow | Stack Overflow |
A bang that leaves never goes by itself: the page says “You are leaving SERCH for …”, says what that site will receive, and lets you choose Stay on SERCH instead. !gh stays on SERCH while !g leaves. A bang SERCH does not know is ignored and the rest of your words are searched.
Keyboard shortcuts
Press ? on SERCH to see them. They can be turned off there, with Keyboard shortcuts on.
| Key | Does |
|---|---|
/ | Go to the search box |
j or ↓ | Next result |
k or ↑ | Previous result |
Enter or o | Open the result |
' | Open the result in a background tab |
d | Search this result’s site |
s | Look up this result’s site |
t | Back to the top |
? | Show these shortcuts |
Esc | Leave the search box, close a sheet |
Private search
Choose Private search on the SERCH home page. Searches are then sent by POST, so they stay out of the address bar, your browser history and the Referer header that sites you open would otherwise receive.
Your choices in Settings, including answers, safe search and the sites you raise or block, are “Kept in this browser only: no account, no cookie”.
Answers with citations
On a results page, Get an answer writes a short answer from the pages SERCH found and read. Every sentence cites the passage it comes from, by number, and SERCH checks each sentence before it is shown: a citation to a passage that does not exist is removed, a sentence left without a valid citation is dropped unless it says what the sources do not cover, and a sentence whose cited passage lacks its words or numbers is left out.
Summarize this page, under a result, does the same for that one page. In Settings, Answers sets when answers appear: Only when I ask, Automatically for questions ending in ? or Off.
The API for developers
Everything the page does is available as JSON over HTTPS, without an API key:
| Endpoint | Returns |
|---|---|
GET /serch/api/v1/search?q= | Results as JSON. POST with a JSON body works too. Parameters include vertical (the lens), freshness, from and to, page, count, include_domains and exclude_domains. |
POST /serch/api/v1/answer | A cited answer, streamed as Server-Sent Events: sources, then delta text and citations, then done. |
GET /serch/api/v1/sources | The sources SERCH searches, and its retention statement. |
GET /serch/api/v1/health | Each source’s last status, the size of SERCH’s index and the day’s budgets: 200 when all is well, 503 when degraded. |
GET /serch/suggest?q= | Suggestions in the OpenSearch format. |
GET /opensearch.xml | Lets a browser add SERCH as a search engine. |
curl 'https://aithatsee.com/serch/api/v1/search?q=CVE-2024-3094&vertical=security'
Each address can make 30 searches, 8 answers and 120 suggestion requests a minute; past that, SERCH answers 429 with a Retry-After header. Errors come as {"error": "<code>", "message": "<plain words>"}. Answers pause for the rest of the day when SERCH’s daily model budget is used up. Utah’s own API and terminal are covered in API and terminal.
How SERCH keeps your searches
“No ads. No trackers.” SERCH fetches site icons and pictures itself, so your browser does not contact those sites while you read results. A bang that leaves SERCH sends your search to that site, where its own privacy rules apply.
This is SERCH’s retention statement, read from SERCH as this page loads:
SERCH never stores your IP address or account with your searches: your address is used only by one-minute rate-limit counters, and a daily-changing one-way hash of it is kept for at most 2 hours to limit paid web lookups. To find results, SERCH sends your search to the sources listed on its sources page. Results are cached under a one-way hash of the search, with no identity: result lists and answers for 10 minutes (news) to 6 hours, each source's reply for up to 7 days, and a backup copy for up to 7 days for outages. Pages that SERCH's sources return are kept in SERCH's own index for up to 30 days; a page you ask SERCH to summarise is read once and not kept. Logs hold only a keyed one-way hash of the search (the key changes daily), timings and which sources answered; request addresses are not logged. Cloudflare keeps these logs for 7 days.
What Utah keeps for your account is in the Privacy policy. If SERCH is not answering, Status shows its health as Search (SERCH).
