Cool idea. The pricing model reminds me of my time working in algorithmic trading, haha. I'll try this out for some queries I wanted to run.
I suppose the scraping you're doing is a huge part of your value proposition, but I would like to gently nudge you in the direction of making the datasets available via p2p (e.g. a torrent) like how Wikipedia distributes its snapshots in the spirit of democratizing access to data that is becoming increasingly walled off. Also, I think another potential benefit that kind of bulk sharing would have is relieving the congestion from those doing the equivalent operation to extract data via the querying interface.
Please have a 'readable version' option so I don't have to exhaust myself parsing the sites layout. I get that it's unique but most of us just want to work out what you're offering in 5-10 seconds of our time.
I'd bet that no one, not even the site's [human] creators, has ever read that homepage end to end. At best, it might have been handed over to a swarm of reviewer agents.
Scry, keyword action that allows a player to look at a specific number of cards from the top of their library and then arrange those cards in any order, placing any number of them on the bottom of the library and the rest on top.
Pricing model is hard to understand at a glance. It uses a term "second of query time" which is not a conventional term and not defined anywhere. Also, all pricing related pages seem to be LLM-generated and are hard to read for a human.
Please, just explain in your own words, how the pricing works, without using made up terms invented by an LLM.
Hi, yes. New users right now get free credit. When the server isn't burdened, queries are currently ~free (under $.01 per second, when most are well under a second). We're just trying to learn here how to use this thing productively together.
As load increases, the price goes up. There's also exponential egress pricing because Scry is a place where computation happens, not a metaphorical torrent. I'm still tweaking things, balancing between multi-user server load, giving normal active human users lots of priority and no fear in using it hard and deliberately, and fair pricing for agents and automated heavy workflows people set up in the background.
This is a very good thing, thanks! Have you talked with any of the smaller search engines like Kagi, Qwant, Brave, Mwmbl, DDG, etc to have this supplement the quality of their results? This seems like a big step towards breaking Google and Bing's dominance in search.
> Furthermore, search companies aren't even pursuing text-to-SQL anymore (several have talked to me)... they made up their minds during the traumatic 2024 text-to-sql days. They were just too early.
Can you expand on this? Is text-to-sql a deadend? (I personally think it is, having worked on a project at $work. But curious to hear about others experience.)
I suppose the scraping you're doing is a huge part of your value proposition, but I would like to gently nudge you in the direction of making the datasets available via p2p (e.g. a torrent) like how Wikipedia distributes its snapshots in the spirit of democratizing access to data that is becoming increasingly walled off. Also, I think another potential benefit that kind of bulk sharing would have is relieving the congestion from those doing the equivalent operation to extract data via the querying interface.
Also HN: This site is doesn't look like other sites, awful to read.
Will it be added? Are you forced to use a traditional search engine to make it in the leaderboard?
https://scry.io/deepsearchqa
https://www.kaggle.com/benchmarks/google/dsqa
Please, just explain in your own words, how the pricing works, without using made up terms invented by an LLM.
As load increases, the price goes up. There's also exponential egress pricing because Scry is a place where computation happens, not a metaphorical torrent. I'm still tweaking things, balancing between multi-user server load, giving normal active human users lots of priority and no fear in using it hard and deliberately, and fair pricing for agents and automated heavy workflows people set up in the background.
Can you expand on this? Is text-to-sql a deadend? (I personally think it is, having worked on a project at $work. But curious to hear about others experience.)