Building a Local SQLite Archive of DuckDB Tweets and Their API Costs

A developer built a small standard-library Python script that pages through a Twitter search for DuckDB-related posts and stores them in SQLite, keyed by tweet ID so re-runs avoid duplicates. The query is filtered to English, non-reply posts with at least 20 likes to keep the archive focused on well-engaged content. The author notes that the API bills per tweet returned at 15 credits each, with a 15-credit minimum per request, and that 100,000 credits equal one dollar. A full page of 20 tweets costs about $0.003, and a first run of 15 pages came to roughly $0.045. The writeup also highlights a mistake that made a second run cost as much as the first, which the author explores in the article. The author works on the TwitterAPI.io service being used and says the code and figures come from their own runs.