Customers and sessions
Keep customer records and fitting sessions together in the fitter dashboard.
ELDRICK · For professional fitters
Run fittings, manage customers, and turn launch-monitor sessions into clear equipment recommendations with ELDRICK.
Fitter dashboard
Keep customer records and fitting sessions together in the fitter dashboard.
Review fitting recommendations and turn them into practical club builds.
Manage the products available to your fitting operation.
Review fitting activity and outcomes from the fitter dashboard.
Marshal
Marshal turns TrackMan and compatible launch-monitor data into one-tap ELDRICK fittings. Pairing and setup are available inside the protected fitter app, not on a public setup page.
Supported scan UI
The scan interface currently lists these monitors:
Monitor support describes the listed scan workflow and does not claim a direct hardware integration.
Developer interfaces
Send a launch-monitor session into the ELDRICK fitter workflow. Marshal uses the authenticated session-ingest path; access is configured inside the fitter app.
Submit golfer specifications and swing metrics to the public v1 API for driver or iron fitting recommendations.
Connect an MCP-compatible client to the documented endpoint for supported ELDRICK tools.
Use the documented command-line examples to call the fitting API and configure compatible MCP clients.
Public API results displayed to end users must include the attribution required by the API documentation.
Approved dataset facts
ELDRICK is trained on 80,000 fittings. ELDRICK has done 25k+ fittings.
Questions
The fitter dashboard brings together customers, fitting sessions, recommendations, club builds, inventory, and fitting analytics.
Marshal is the fitter-facing workflow that sends TrackMan and compatible launch-monitor session data into an ELDRICK fitting. Setup is available inside the protected fitter app.
The supported scan interface currently lists Trackman, FlightScope, GC Quad, Mevo, and Foresight.
Public API v1 supports driver and iron fittings. Its documentation covers the fitting endpoint, required attribution, command-line examples, and developer integration details.