Run intake end to end
Open a fill session for an insured, answer questions in free-form text, or pre-fill from a prior ACORD, dec page, or application PDF.
Bindly Workspace API
The Bindly workspace API gives your agency programmatic access to Bindly. Start an intake session for an insured, answer the intake conversationally or extract it from PDFs you already have, fill and download the ACORD forms, review the risk flags, and submit the finished packet to Hedge, all from your own tools. Anything your team does by hand in Bindly, a script or an assistant can do through the API.
What you can do
Section titled “What you can do”Fill and download forms
Generate the filled ACORD application PDFs from the collected answers and download each one, ready to review or send.
Review risk, then submit
Read the underwriter-facing risk flags, then hand the finished session to Hedge on your workspace’s connected account and get the submission id back.
Work from AI tools
Connect an MCP-capable assistant to run the same lifecycle in natural language. The REST API, CLI, and MCP connector have full parity.
Three ways to integrate
Section titled “Three ways to integrate”Pick the surface that fits how you work. They share one API and one workspace identity.
bindly CLIA command line tool for people and scripts. Install, sign in once, and run the whole lifecycle, from session to submission, in your terminal.
REST APIJSON over HTTPS with a workspace API key or a bearer token. Call the /org endpoints directly from your backend.
MCP connectorA Model Context Protocol connector for AI tools like Claude, ChatGPT, Cursor, and Claude Code. Fill intake and submit in natural language.
Base URL
Section titled “Base URL”All REST endpoints live under a single host, at the /org prefix:
https://engine.bindly.insureEvery request is authenticated, either with a workspace API key (bsk_...) or a
short-lived OAuth 2.1 bearer token, and all data is scoped to the workspace the
credential belongs to. See Authentication for both options.
Next steps
Section titled “Next steps”QuickstartGo from zero to your first intake session and Hedge submission in a few minutes.
AuthenticationWorkspace API keys, the OAuth 2.1 device flow, browser sign-in, and dynamic client registration.
ConventionsStatus codes, error shapes, and how data is scoped to your workspace.
API ReferenceEvery endpoint, request, and response, generated from the OpenAPI spec.