An upper bound is a maximum permitted size or value that a quantity cannot exceed. API designers use it to control numeric ranges, collection growth, and response sizes. section 5.3.1 section 5.7.1
Use upper bounds deliberately:
- For numeric fields, choose storage that covers the intended range while accounting for lower bounds and zero. section 5.3.1
- For maps, bound the number of keys and values, then limit individual key and value lengths. section 5.7.1
- Prefer separate structured fields over an ever-growing map with one aggregate character limit. section 5.7.1
Pagination with maxPageSize
A paginated API can return up to 10 results instead of requiring exactly 10. If matching rows are widely distributed, stopping at a time cutoff can preserve latency and continue from the next request. section 21.3.1
