Workflow

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.

Answer shape

The source material is public; the query session is yours. Scry exposes enabled source-native relations through an API key and returns reproducible rows.

Steps

  • 1Create or use a Scry API key.
  • 2Inspect context and the live schema.
  • 3Choose an enabled relation and run bounded read-only SQL.
  • 4Keep returned source-native IDs and provenance fields with your notes.

SQL

Treat this as a starting query. Inspect the live schema before widening it.

SELECT hn_id, title, original_author, original_timestamp, uri
FROM hackernews.items
WHERE title != ''
ORDER BY hn_id DESC
LIMIT 20;

Schema

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.hackernews.items The enabled source-native Hacker News relation: public IDs, authors, timestamps, scores, payload text, and links.

Sources

Hacker News Every Hacker News story and comment, queryable with read-only SQL — source-native records, timestamps, authors, scores, and a live tail.