Samsara assets, attributes, tags, organization metadata, devices, and device-recovery operations. Generated from a point-in-time SHA-256 pin of Samsara current official consolidated OpenAPI 2025-10-23. Enroll the organization connection at the correct US, EU, or CA regional origin; the per-organization connection base overrides the representative US origin without exposing runtime routing as an operation argument. Use a manually enrolled Samsara API token with only the permission labels declared on each operation. All reads are uncached, sensitive reads are marked sensitive-read, every mutation is grant-off and approval-gated, all JSON responses stringify unsafe integers, and comma-separated versus exploded query arrays follow the official OpenAPI serialization contract. Beta, preview, and legacy operations are labeled explicitly. Driver-token issuance and the Samsara Functions code/runtime surface are excluded. Issues and work orders are not declared as Sources because the repository Source brief requires a separate human field-path verification gate.