Public SQL

Read-only SQL over public corpora

Scry is a public-data SQL surface: read-only SQL over source-native public corpora, with schema discovery, provenance, freshness, and vectors for agents.

What you get

Scry gives agents and researchers a read-only SQL interface over public source material: papers, forums, social archives, scholarly metadata, public records, and source-native tables. Identifiers, sources, timestamps, and provenance come back with every row, so results stay reproducible.

Public sources

Query Hacker News with SQL hackernews.items Every Hacker News story and comment, queryable with read-only SQL — source-native records, timestamps, authors, scores, and a live tail.Query Reddit with source-native SQL reddit.comments The public Reddit archive — posts and comments queryable with read-only SQL by subreddit, author, timestamp, text, and score.Query Manifold Markets with SQL manifold.markets The full Manifold prediction-market corpus — every market, every bet, every comment — queryable with read-only SQL and kept minutes-fresh from the live API.Query public mailing-list archives with SQL mailing_lists.messages Public mailing-list and Usenet archives — the Linux kernel list, GNOME, Fedora, extropians, SL4, and about 51,000 more lists — threaded and queryable with read-only SQL by list, author, date, and text.Query forum archives with SQL forums.posts About 36 million posts and comments across roughly 4,300 forum sites — LessWrong, the EA Forum, DEV, DataSecretsLox, crypto-governance forums, and a long crawl-discovered tail — queryable with read-only SQL by site, thread, author, and text.Query Stack Exchange with SQL stackexchange.posts Questions and answers across the Stack Exchange network — Stack Overflow, Mathematics, and every other landed site — queryable with read-only SQL by site, tag, author, score, and text.

Example queries

Trace a phrase on Hacker News with SQL A Scry query pattern for tracing a public phrase through Hacker News by month, distinct authors, and inspectable source rows.Find the first use of a phrase on Reddit with SQL A Scry query pattern for locating the earliest occurrences of a phrase in a subreddit, with author, timestamp, score, and the full comment row attached.Recover a prediction market's full price path with SQL A Scry query pattern for reconstructing a Manifold market's probability history bet by bet, from the per-bet prob_before and prob_after fields.Chart a community's drift along a meaning axis with SQL A Scry query pattern that mints two parallel pole sentences as vectors, takes the balanced axis between them, and averages every LessWrong chunk's projection quarter by quarter, centered on the era mean.

API contract

  • Read-onlyRun read-only SQL over Scry corpus surfaces.
  • SchemaUse GET /v1/scry/schema before constructing SQL.
  • QueryUse POST /v1/scry/query with Content-Type: text/plain.
  • LimitsStart with a bounded probe and include LIMIT in exploratory queries.

Docs

HTTP API The Scry API is the MCP endpoint: plain HTTPS JSON-RPC, one URL, no client library. Raw HTTP routes ride underneath for services that want them.Turing-complete search Scry search computes: recursive SQL and fixpoint programs run unbounded iteration with conditional branching over the corpus, under budgets and deadlines you set. Graph walks, negation, whole-population aggregates — the answer, not a page of links.Schema, provenance, and freshness Inspect Scry schema, source-native tables, provenance fields, freshness state, and query-visible corpus surfaces before running broad research queries.

Schema and workflows

POST /v1/scry/query The synchronous SQL-over-HTTPS endpoint for Scry: send bounded read-only SQL (ClickHouse dialect) as text and receive one JSON document or a typed HTTP error within the advertised execution ceiling. Asynchronous agent research with public SQL A Scry workflow for agents that inspect schema, run bounded SQL, preserve records, and return evidence with sources attached.Run a personal query over public data Use a personal Scry API key to run read-only SQL over an enabled public corpus relation and save the rows you need.