docs: keep polling guidance contract-driven

Author: karlwaldman

EXAMPLES.md

@@ -456,12 +456,10 @@ def monitor_prices():
             elif price.value < limits['low']:
                 send_alert(commodity, price.value, limits['low'], 'BELOW')
 
-        # 30 minutes fits the free plan: 48 requests/day against a 50/day
-        # allowance. On Developer and above use 300 (5 minutes), which matches
-        # how often spot prices actually change - nothing we publish moves
-        # faster than ~2.5 minutes, so a shorter timer returns the same number.
+        # Example caller-selected interval. Derive production polling from the
+        # account's current limit/reset response and the source timestamps.
         # See https://docs.oilpriceapi.com/guides/rate-limiting#how-often-to-poll
-        time.sleep(1800)
+        time.sleep(1800)
 
 if __name__ == '__main__':
     print("Starting price monitor...")

docs/PERFORMANCE_GUIDE.md

@@ -235,36 +235,26 @@ while True:
 
 **Solution:**
 ```python
-# Match the interval to your plan AND to how fast the data moves.
+# Match the interval to the account limit and how fast the data moves.
 import time
 
 while True:
     price = client.prices.get("WTI_USD")
     print(f"WTI: ${price.value}")
-    time.sleep(1800)   # 30 min -> 48 requests/day, fits the free plan
-                       # Developer and above: 300 (5 minutes)
+    # Example interval; derive this from current limit/reset metadata.
+    time.sleep(1800)
 ```
 
-**Pick the interval from your plan:**
-
-| Plan | Quota | Poll every | Requests/day |
-| --- | --- | --- | --- |
-| Free | 50 / day | **30 minutes** | 48 |
-| Developer | 10,000 / month | 5 minutes | 288 |
-| Starter | 50,000 / month | 5 minutes | 1,440 |
-| Professional+ | 100,000+ / month | 5 minutes | 2,880 |
-
-Polling faster than the data changes cannot return new information. Measured
-over a week: `BRENT_CRUDE_USD` updates about every 2.5 minutes, `WTI_USD` and
-`NATURAL_GAS_USD` about every 5, and refined products such as `DIESEL_USD`
-about twice a day. Above Developer, extra quota is better spent on more
-commodity codes than on a shorter timer.
+Choose the interval from the current account response and the source timestamps
+returned with the data. Polling faster than the source changes cannot return new
+information, while a hard-coded schedule can exceed an account's current
+allowance when product limits change.
 
 ⚠️ **`get_multiple()` currently issues one HTTP request per code**, so it
 consumes quota per commodity rather than per call. Until that is batched
 (api#7240), a loop over `get()` and a call to `get_multiple()` cost the same.
-The REST API itself accepts up to 20 codes in a single request that counts
-once — see the rate-limiting guide if you are close to your quota.
+See the rate-limiting guide for the current REST batching contract if you are
+close to your quota.
 
 **Better Solution (for streamed updates):**
 ```python