Skip to main content
Builder codes are short identifiers that integrators — front-ends, aggregators, vault managers, and other application builders — can attach to signed actions to claim attribution for the order flow they originate. Builder codes are the protocol’s affiliate primitive, recorded as part of the per-transaction attribution stream so that downstream accounting is verifiable rather than trust-based.
Status: not yet published. The builder-code scheme will be released alongside the public exchange API. Until then, treat the descriptions below as planning documentation.

​
What this page will contain

When the API ships, this page will document:
  • Code format. The structure of a builder code and how integrators register one.
  • Attachment. How a builder code is included in a signed action without affecting matching priority or fee tier.
  • Attribution. How builder-code attribution appears in the Verifiable Execution Stream and the historical data archives, cross-referenced with PTAD.
  • Fee handling. How any builder-code-related fee allocation is computed, applied, and audited.
  • Disputes and resets. How a builder code can be transferred, retired, or re-issued, and what happens to historical attribution when it is.
For early integration questions, email contact@intention.xyz.