Launching today
pixserp
Your LLM on the live web. One endpoint, ten answer shapes.
144 followers
Your LLM on the live web. One endpoint, ten answer shapes.
144 followers
pixserp is the AI-native search engine for builders. One endpoint, ten live-web answer shapes — search, news, images, places, shopping, flights, hotels, YouTube, transcripts, any URL — cited by default. Drop-in for the OpenAI SDK. Flat $1.50 / 1k requests.
pixserp
Hey Product Hunt 👋 I’m Lorenzo.
Pixserp started as the live‑web layer we needed for Teti AI.
We tried everything first — Serper, Exa, Tavily, self‑hosted Playwright.
Scrapers gave us raw HTML to clean.
AI search APIs handled one shape of question and shrugged at the rest.
So we built the endpoint we wished existed — and today we’re opening it up:
🌐 10 answer shapes, one call — web, news, images, places, shopping, flights, hotels, YouTube, transcripts, any URL.
🔌 Drop‑in for the OpenAI SDK — swap base_url, keep your code.
💸 Flat $1.50 / 1k on fast mode. No token roulette. (For reference: Perplexity Sonar Pro is ~$19/1k for the same workload.)
⚡ ~1.5s cited answers, SSE streaming.
🎁 $25 in credits for Product Hunt today.
Cheers! 🍻
One endpoint with ten answer shapes for live web data is a clean abstraction. It removes a ton of integration overhead for teams building on top of LLMs. We've been building in the customer success for developer tool companies space at RetainSure, and pixserp touches on something we think about a lot: how real-time web context changes what AI can reliably answer. Which answer shape do your users reach for most often?
pixserp
@shivam_jaiswal21 Thanks for the thoughtful question — and totally agree: having one endpoint with multiple answer shapes ends up being a much cleaner abstraction for teams building on top of LLMs.
What we do have is everything we’ve learned from running pixserp inside Teti, where it’s been powering live‑web queries in production for a while.
By the way, actually we have launched pixserp today and we are on Product Hunt, so external usage data is just starting to come in.
That said, we’re genuinely curious to see how developers outside our ecosystem will use it.
Different stacks tend to surface different “hot paths”, and that’s exactly what we want to learn from this launch.
So short answer: we have strong signals from Teti, but the next few days will tell us a lot about how broader teams integrate pixserp into their workflows.
How would you use it?
@lorenzn This looks sick! One thing I'm curious about how fresh is the live web data? Like if something changed an hour ago, does Pixserp pick it up immediately or is there any delay?
pixserp
@munis_abbas Great question. Pixserp queries live web sources at request time, so updates can show up very quickly. To keep responses fast and reliable, we apply smart freshness logic based on the type of request.
For time-sensitive checks, we can also force a fully live pull when needed, in this way if something changed an hour ago, pixserp will typically reflect it very quickly.
Mailwarm
An Interesting idea. If the results are truly consistent across all verticals, this could replace a lot of custom search integrations. I want to know how it performs on real time ranking and accuracy at scale.
pixserp
@thamibenjelloun nice to e-meet you! 👋
Glad you find the idea interesting! We’re already using into our main product, and so far it’s been performing reliably — both in real‑time ranking and at scale.
We’d really love to hear your feedback, so if you get a chance to try it out, we’d be happy to learn from your experience. 🚀