card, license and attribution for release 2026-08-02

README.md

@@ -115,21 +115,24 @@ trades = knowable.congress_trades(since="2026-01-01", ticker="NVDA")
 The SDK wraps the HTTP contract below, so an SDK query and a direct API query
 return identical rows.
 
-**Status: the read API is not hosted yet.** The FastAPI app and a client both
-exist and are tested against real release bytes, but no public endpoint serves
-them today. Use the Parquet paths above until that lands. The contract, so you
-can write against it now:
+**The read API is live at
+<https://knowable-api-production.up.railway.app>.** It serves the verified
+release through one sealed read-only DuckDB connection. The unversioned
+Congress route also carries a small MIT-licensed Kadoa current tail; dated
+release routes remain immutable. Contract:
 
 ```
 GET /v1/{resource}?cursor=&limit=&as_of=
-    -> {"data": [...], "next_cursor": str|null, "as_of": timestamp}
+    -> {"data": [...], "next_cursor": str|null,
+        "resume_cursor": str|null, "as_of": timestamp}
 
 resources: congress/trades, house/filings, senate/filings,
-           insider/transactions, fund/holdings, coverage
+           sec/form4, sec/holdings, coverage
 ```
 
-`as_of` applies the point-in-time bound server-side. Paging is keyed on
-`(published_at, id)`, so a cursor stays valid across releases.
+`as_of` applies the point-in-time bound server-side. Persist `resume_cursor`
+after every non-empty page so a caught-up client does not re-download the same
+short tail. The token is opaque and versioned.
 
 ## What it covers