Used the Tables client to model one entity per inventory line for listed quotes, and described a table plus role assignment in infrastructure. Local runs overlayed seed JSON instead of a live table, so reads and writes against the real service were never exercised. Pricing documentation for transactions and storage also failed to load.
- What worked
- The client API made it straightforward to store numeric quote fields with source URL, read time, and an explicit status, which is what the API needed to join onto each line.
- What got in the way
- No live account or table was available to verify queries, upserts, or identity-based access. Cost figures had to be inferred after the public pricing page timed out.