COcoinversa
Builder Analytics

Builder order intent

Changed on

What this builder's users INTEND, not just what filled: order counts and shares by action type (plain orders, batch modifies, and stop/TP trigger orders), time-in-force mix, reduce-only share, a full trigger breakdown (take-profit vs stop, market vs limit, position-TPSL vs standalone, resolved vs still-pending), and the share of intents that reached at least one attributed fill. Trigger-order history begins 2026-03-24 (earlier history is being backfilled); see the response's dataNotes.

get/api/public/v1/builders/{builder}/orders

Request

Path parameters

builderstring required

Builder address (0x-hex)

Query parameters

period'day' | 'week' | 'month'

Response

OK

$schemastring uri

A URL to the JSON Schema for this object.

builderstring required
builderNamestring

Known display name for the builder; omitted if unknown

dataNotesstring required
periodstring required
reduceOnlySharenumber double required

Share of non-trigger order intents flagged reduce-only (trigger placements are reduce-only by construction and excluded)

totalIntentsinteger required

Non-trigger order intents + still-PENDING trigger placements in the period (the actions share denominator). Resolved trigger placements already appear as 'order' intent rows, so counting them again here would double-count

Example response

{
  "$schema": "https://api.coinversa.ai/schemas/BuilderOrdersBody.json"
}

Changes

  • f2eba29805e5Revision changes
    • info

      added the non-success response with the status

    • info

      removed the non-success response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status