Skip to main content
Polymarket V2 trades include a builder field identifying which order routing service executed the trade. This endpoint is both the Builder ranking and the canonical public Builder directory. It returns each Builder’s display name and code, and it can resolve an exact display name case-insensitively. Builder profile metadata is synced from Polymarket’s public builder metadata. Local fill, fee, and volume stats come from Polynode’s indexed OrderFilled events. Builders can appear with metadata before their local stats row is refreshed; in that case stats_pending is true and local volume fields are null. volume is the canonical total builder volume. It counts the outcome shares attributed to the builder, with one share represented as $1 of par notional. This matches Polymarket’s builder-volume convention over the same CLOB V2 history. Polymarket may show additional legacy volume from before onchain V2 builder attribution; Polynode does not import that historical total.

Request

Query parameters

sort and name are case-insensitive. Responses retain canonical Builder names and codes.

Example

Response fields

builder_name, builder_logo, builder_verified, and the local-volume fields are nullable. external_volume is separate public profile context and is never substituted into volume. Buy and sell volume use the same share-notional basis and add to total builder volume. Use external_active_users for the current public builder user-count signal.

Find a Builder by name

Names are matched exactly after trimming whitespace and without case sensitivity. Because display names are not guaranteed to be unique, retain the returned builder_code as the stable identifier.
The directory supports 300 rows per request. This loop follows has_more and prints a tab-separated directory without assuming how many Builders currently exist.