/l2beat/projects/search

POST /api/l2beat/projects/search

Price: 10 credits

Search and list L2BEAT scaling projects ranked by value secured (TVS)

How to use it

List Ethereum layer-two scaling projects tracked by L2BEAT, ranked from highest to lowest value secured (TVS). Optionally filter by name, project type (layer2/layer3), rollup category (Optimistic Rollup, ZK Rollup, Validium, Optimium, Other), maturity stage (Stage 0/1/2), host chain, technology provider/stack, purpose, virtual machine (EVM, WasmVM), or data availability layer (Ethereum, Celestia). Set 'archived' to list sunset projects that are no longer operating instead of active ones. Each result carries the project's risk pillars, badges, stage, and TVS. Use the slug from a result to fetch full project details.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of results (min: 1)
• query string nullable — Filter projects by name (case-insensitive substring)
• type string nullable — Filter by project type, e.g. 'layer2' or 'layer3'
• category string nullable — Filter by exact rollup category (examples: "Optimistic Rollup", "ZK Rollup", "Validium", "Optimium", "Other")
• stage string nullable — Filter by maturity stage (examples: "Stage 0", "Stage 1", "Stage 2")
• host_chain string nullable — Filter by host chain (case-insensitive)
• provider string nullable — Filter by technology provider/stack (case-insensitive)
• purpose string nullable — Filter by project purpose (case-insensitive)
• vm string nullable — Filter by virtual machine (case-insensitive) (examples: "EVM", "WasmVM")
• da_layer string nullable — Filter by data availability layer (case-insensitive substring) (examples: "Ethereum", "Celestia")
• archived boolean — Return archived (sunset / no longer operating) projects instead of active ones (default: false)

Response

• @type string (default: "L2beatProject")
• id string required
• name string required
• alias string nullable
• type string nullable
• host_chain string nullable
• category string nullable
• stage string nullable
• providers array (default: [])
• purposes array (default: [])
• is_archived boolean (default: false)
• is_under_review boolean (default: false)
• badges array (default: [])
  • @type string (default: "L2beatProjectBadge")
  • id string nullable
  • type string nullable
  • name string nullable
  • description string nullable
• risks array (default: [])
  • @type string (default: "L2beatProjectRisk")
  • name string required
  • value string nullable
  • sentiment string nullable
  • description string nullable
• tvs object nullable
  • @type string (default: "L2beatProjectTvs")
  • total number nullable
  • native number nullable
  • canonical number nullable
  • external number nullable
  • ether number nullable
  • stablecoin number nullable
  • btc number nullable
  • other number nullable
  • rwa_restricted number nullable
  • rwa_public number nullable
  • associated number nullable
  • change_7d number nullable
  • associated_tokens array (default: [])
    • @type string (default: "L2beatProjectToken")
    • symbol string required
    • icon string 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 — The entity was not found, or a precondition failed 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.