This document explains Cloud Tasks pricing details.

A billable operation is an API call or push delivery attempt.

Note the following:

• API calls that work on multiple tasks are accounted for as multiple billable operations; for example, one list request fetching 25 tasks is charged as 25 billable operations.
• For pricing purposes, tasks are chunked by size (32 KB). For example, adding a task of 96 KB to a queue produces 3 billable operations, so it is billed the same way as adding 3 separate tasks under 32 KB each to the queue. This holds true for all other API calls and push delivery attempts.
• Every API call is at least one billable operation, including ListTasks requests that return no tasks.
• For batch task creations, the transaction cost is the sum of the individual costs for each task. We determine each task's cost by taking the larger of the request or response payload size, rounded up in 32 KB increments. Tasks that fail due to Google infrastructure errors, and where the SLO isn't met, aren't billed. Successful tasks and tasks that fail due to client errors are billed at standard rates based on size. The response_view (BASIC or FULL) you request for each task determines if the returned payload size is factored into the billing.
• Unlike batch task creations, batch task deletions are control operations that don't process task payloads. Each successfully deleted task, or a task deletion that fails due to a client error, is billed as exactly one flat operation. You aren't billed for deletion failures caused by Google infrastructure errors.
• When using HTTP Targets tasks, regular network costs apply.

• Read the Cloud Tasks documentation.
• Get started with Cloud Tasks.
• Try the Pricing calculator.
• Learn about Cloud Tasks solutions and use cases.