Skip to main content
POST
๐Ÿ’Ž Builder Performance Aggregate
Experimental. This endpoint returns data only on chains past the Glamsterdam hard fork. Hoodi forks first; mainnet returns 404 until it forks. The request and response may change before the mainnet release. See Glamsterdam API.

Authorizations

Authorization
string
header
required

Authorization header with value: Bearer YOUR_TOKEN. Refer to the API Keys section to create your API key.

Body

application/json
builder
Builder Public Key ยท object
required

Select builders by one of these options. Every endpoint that uses this selector requires a Scale or Enterprise plan:

  • builder_pubkey: One builder, by its public key, as in execution_payload.builder_pubkey. The best way to follow one builder over time.
  • builder_index: The builder that holds this index now. To select the builder of a past slot, use that slot's builder_pubkey.
  • builder_execution_address: Every builder that withdraws to this execution layer address. Use it for all the builders of one operator.
  • builder_entity: Every builder that withdraws to an address that beaconcha.in curated under this name. Optionally include builder_sub_entity. Matching is case-sensitive.

Note: When a builder exits and withdraws its whole balance, the chain gives its index to the next new builder, so one index can name different builders over time. Every option therefore resolves to builder public keys, and a proposal counts for a builder only from the epoch it took the index until the epoch the next builder took it. The builder registry exists from the Glamsterdam hard fork on. An option that matches no builder returns 404. A builder that matches but has nothing in the result returns an empty list or zero counts, not 404.

range
Fixed Window ยท object
required
chain
enum<string>
default:mainnet

The Ethereum chain to query.

Available options:
mainnet,
hoodi

Response

Successful response.

Response containing the delivery and settlement record of the selected builders over the evaluation window.

data
object
required
range
object
required

The time span actually covered by the returned results โ€” from the first to the last matching data point โ€” specified in slots, epochs, and Unix timestamps.

This reflects the data that was found, not the range that was queried. When the response is 200 but no data is found, it falls back to the requested range, or to the full available history if no range was given. Some endpoints answer 404 instead when no data is found.

For arbitrary (custom) time-range queries the queried range is expanded outward to whole UTC days, so the covered range may be wider than requested. As stated above, the reported range still reflects the data that was actually found โ€” a touched UTC day with no data for the selected validators will not extend it.