Skip to main content
PUT
Set your builder fee

Authorizations

X-Monaco-Signature
string
header
required

Ed25519 session-key request signing. Every authenticated request carries three headers: X-Monaco-PublicKey (64-char lowercase-hex session public key), X-Monaco-Timestamp (Unix milliseconds, within 30s of server time), and X-Monaco-Signature (hex ed25519 signature). The signature is over METHOD\npath?query\ntimestamp_ms\nSHA256_hex(body), where the body hash is the SHA-256 of the empty byte string when there is no body. Obtain the session keypair from POST /api/v1/auth/challenge followed by POST /api/v1/auth/verify.

Body

application/json
bps
integer<uint32>
required

New builder fee in basis points, from 0 up to the current builderFeeCapBps inclusive. 0 stops charging a builder fee.

Required range: x <= 100
Example:

10

Response

OK

builderFeeBps
integer<uint32> | null

The builder fee now stored, in basis points.

Required range: x <= 100
Example:

10

previousBuilderFeeBps
integer<uint32> | null

The builder fee this change replaced, in basis points. Equal to builderFeeBps when the request set the fee it already had, which changes nothing.

Required range: x <= 100
Example:

0

changesRemaining
integer<uint32> | null

Builder-fee changes this application can still make in the current rolling 24 hours (at most 2).

Required range: x <= 2
Example:

1

nextChangeAllowedAt
string<date-time> | null

RFC 3339 time at which the next builder-fee change becomes allowed, or null while changesRemaining is above 0.