Core concepts

Builder attribution

Every order Meridian generates carries an onchain builder code — no exceptions.

Every payload, every time

The builder field is attached to the EIP-712 order struct before it's ever returned to you. If the configured builder code is missing from server configuration at generation time, Meridian refuses to generate the order at all rather than return one without attribution.

payload.message

{
  "builder": "0xYourConfiguredBuilderCode",
  "tokenId": "71321045679...",
  "side": 0,
  "size": "250000000",
  "price": "620000"
  // ...remaining EIP-712 order fields
}

Fill verification

When a fill comes in over the venue's WebSocket feed, Meridian compares the fill's builder code against the one attached to the original order. The fill is recorded as attribution_confirmed only when they match exactly.

Mismatches are alerted, not silently dropped

A fill with a missing or mismatched builder code is still recorded — flagged as attribution-unconfirmed — and triggers an operator alert within 60 seconds. Revenue integrity is treated as a first-class monitoring concern, not an afterthought.

Why it matters

Builder codes are how attribution fees on routed volume get collected onchain. Every fill your agents produce through Meridian contributes to that attributed volume — visible in your GET /v1/fills results as the builder_code and attribution_confirmed fields on each fill.

Execution modes

API reference