/l2beat/projects/costs

POST /api/l2beat/projects/costs

Price: 1 credit

Get L2BEAT onchain costs per scaling project (calldata, blobs, compute, overhead)

How to use it

Get the onchain costs that Ethereum layer-two scaling projects pay to post data and proofs to L1, over a chosen time window. Each project carries the cost split into calldata, blobs, compute, and overhead, expressed in gas, ETH, and USD, plus the number of L2 user operations. Omit 'project' to get all projects ranked by total USD cost, or pass a slug for a single project.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• project string nullable — Project slug to return costs for a single project; omit for all projects (examples: "base")
• count integer required — Max number of projects to return (min: 1)
• range string — Time window for the onchain cost aggregation (default: "30d"; one of: "1d", "7d", "30d", "90d", "180d", "1y", "max")

Response

• @type string (default: "L2beatProjectCosts")
• id string required
• gas object nullable
  • @type string (default: "L2beatCostBreakdown")
  • overhead number nullable
  • calldata number nullable
  • compute number nullable
  • blobs number nullable
  • total number nullable
• eth object nullable
  • @type string (default: "L2beatCostBreakdown")
  • overhead number nullable
  • calldata number nullable
  • compute number nullable
  • blobs number nullable
  • total number nullable
• usd object nullable
  • @type string (default: "L2beatCostBreakdown")
  • overhead number nullable
  • calldata number nullable
  • compute number nullable
  • blobs number nullable
  • total number nullable
• uops_count integer nullable
• synced_until integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Project not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.