I found no published per-GET/PUT fee for HF storage. Reads/CDN are advertised as included, with an 8x-storage egress allowance. Jobs-specific inclusion and over-limit terms remain unconfirmed. A running Job is still billed while waiting on data.

I reviewed Hugging Face's storage pricing, billing and S3 access documentation and found no separate published charge per GET/PUT request or a base fee per GB read.

HF advertises included egress and CDN. The Storage page qualifies this with an 8:1 ratio to stored volume. The updated accounting finding records the monthly usage dashboard and the remaining ambiguity about HF Jobs traffic and allowance overruns.

Request limits are a separate operational constraint: the Hub enforces rate limits by request category. Those limits should not be interpreted as a price per request.

Jobs bills hardware by the minute while Starting or Running. Consequently, waiting on remote I/O can increase the compute bill even if no separate read charge is incurred.

Sources: Storage pricing, egress allowance, billing, S3 access, Hub rate limits, Jobs hardware billing.