Install Jentic One Beta

Connect the Hedge Submission API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hedge Submission API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhedgespecialty.com%2Fhedgespecialty" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhedgespecialty.com%2Fhedgespecialty" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Hedge Submission API.

Submit a commercial insurance risk as free text, PDFs, or structured JSON and start marketing it

Track a submission across its Instant Quote, Binding, and Specialty market lanes with asks, assumptions, and released quotes

Answer Hedge's outstanding requirements and carrier application questions in a batch or per session

Request and submit bind requests on a released quote, attaching pre-bind contingency documents

GET STARTED

Start building with Hedge Submission API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Hedge Submission API for, with concrete tasks.

★ Agent-Driven Insurance Submission

An AI agent working a broker's book calls the Hedge Submission API through Jentic to place a commercial risk: it creates a submission from structured JSON or sends free text and PDFs to the intake endpoint, and Hedge immediately matches appetite and opens the Instant Quote, Binding, and Specialty lanes. The agent then polls the submission's markets and quotes, answers outstanding requirements, and tracks bind readiness, acting on the same thread a human broker would receive by email. A machine credential names a producer_email so every submission is attributed.

Create a submission for a general liability risk, poll its markets for released quotes, answer any outstanding requirements, and report bind readiness

Appetite Check Before Placement

Before sending a risk, a brokerage checks which carriers will consider it by searching appetite by line of business, state, and class. The Hedge Submission API returns the programs Hedge would try and the supplemental questions a risk needs, so a broker can qualify a placement and gather answers up front instead of after a decline. This turns a cold submission into one that markets cleanly.

Search appetite for a restaurant general liability risk in Texas and return the programs Hedge would approach

Bind and Policy Retrieval

Once a quote is released, a broker requests a bind, attaches any pre-bind contingency documents, and submits the bind request to Hedge for placement, then retrieves the bound policy and its documents. The Hedge Submission API exposes bind readiness, bind requests, and the brokerage's bound policies with downloadable PDFs, so the whole place-to-bind step runs without leaving the broker's own system. Payment and invoice status is available on the same rail.

Create and submit a bind request for a released quote, then download the bound policy document PDF

Key Endpoints

70 endpoints — the hedge submission api submits commercial insurance risks to hedge programmatically and tracks each one from marketing to quote and bind.

METHOD

PATH

DESCRIPTION

POST

/broker/submissions

Create a submission from structured JSON

POST

/broker/intake

Send Hedge a risk as free text and/or PDFs

GET

/broker/submissions/{submission_id}/markets

The markets being tried, with asks, assumptions, and quotes

GET

/broker/submissions/{submission_id}/quotes

Every released quote on a submission, with each lane's status

POST

/broker/submissions/{submission_id}/bind-requests

Request to bind a released quote

GET

/broker/submissions/{submission_id}

Get one submission with status, markets, and documents

POST

/broker/appetite/search

Structured appetite search by query, lines, and state

GET

/broker/policies

List your brokerage's bound policies

POST

/broker/submissions

Create a submission from structured JSON

POST

/broker/intake

Send Hedge a risk as free text and/or PDFs

GET

/broker/submissions/{submission_id}/markets

The markets being tried, with asks, assumptions, and quotes

GET

/broker/submissions/{submission_id}/quotes

Every released quote on a submission, with each lane's status

POST

/broker/submissions/{submission_id}/bind-requests

Request to bind a released quote

GET

/broker/submissions/{submission_id}

Get one submission with status, markets, and documents

POST

/broker/appetite/search

Structured appetite search by query, lines, and state

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Hedge Submission API by hand means implementing OAuth 2.1 with PKCE for broker users or the client_credentials grant for machine clients, naming a producer_email on machine submissions, and pointing at the right production or staging host. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Hedge issues tokens with two scopes, broker_mcp for read and broker_submit for write, and all access is already pinned to your brokerage by the token. A Jentic rule can go finer and allow only the operations your agent needs, so it can read submissions, markets, and quotes without being able to create bind requests or submit new risks unless you add those operations.

Credential isolation

Your Hedge OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'submit an insurance risk' or 'check market appetite', and Jentic returns the matching Hedge operation with its input schema so the agent creates a submission or requests a bind without reading the reference docs.

FAQs

Specific to using Hedge Submission API through Jentic.

What authentication does the Hedge Submission API use?

The Hedge Submission API uses OAuth 2.1, per its OpenAPI spec: broker users authorize through the authorization-code flow with PKCE, and machine clients exchange an API key for a token through the client_credentials grant. Access tokens are scoped to your brokerage and carry a broker_mcp read scope or a broker_submit write scope. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's logs.

Can I track a submission to quote and bind with the Hedge Submission API?

Yes. After you create a submission, the API returns the markets being tried in three lanes (Instant Quote, Binding, and Specialty), every released quote, and a bind-readiness summary. You answer outstanding requirements in a batch, then create and submit a bind request on a released quote, and retrieve the bound policy once Hedge places it.

What are the rate limits for the Hedge Submission API?

The OpenAPI spec does not specify rate limits. Hedge also pushes submission events and thread messages to a registered webhook, so you can avoid tight polling; for current limits, see the Hedge API documentation at https://api.hedgespecialty.com/api/v1/docs.

How do I submit an insurance risk through Jentic?

Search Jentic with a query like 'submit a commercial insurance risk', add the Hedge Submission API from the directory, and store your OAuth credential once. Your agent calls the create-submission or intake operation, then polls the submission's markets and quotes and answers any requirements. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Hedge Submission API?

Yes. Write a rule that allows only the read operations, such as listing submissions and reading markets, quotes, and policies, so the agent can monitor placements but cannot create submissions, answer on your behalf, or request a bind unless you add those write operations, and every call it makes is logged. Hedge already scopes every token to your own brokerage, so there is no cross-tenant access to begin with.

Is there a Hedge MCP server?

Yes, Hedge offers an MCP connector that uses the same broker OAuth flow. You can also connect the Hedge Submission API directly through Jentic: your agent gets the full 70-endpoint surface without loading another server's tool definitions into its context, your credential is injected at call time by your self-hosted instance instead of living in a config file, and your rules decide which operations the agent may call.

Hedgespecialty Hedge Submission API

AI ReadinessFoundational (C+)59/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMDeal Pipelineoauth270 EndpointsREST

For Agents

Submit a commercial insurance risk to Hedge, then track its markets, quotes, and requirements and request a bind, all scoped to one brokerage. Turns a broker's email-style placement into structured API calls.

Use for: Submit a new commercial insurance risk to Hedge for a client, Check which markets have appetite for a class of business in a given state, Get the released quotes on a submission across all market lanes, Find out what a submission still needs before it can bind

Not supported: Does not sell insurance direct to consumers, underwrite risk, or process claims. Use for submitting commercial insurance risks through a broker and tracking them to quote and bind only.

The Hedge Submission API submits commercial insurance risks to Hedge programmatically and tracks each one from marketing to quote and bind. You create a submission from structured JSON or send free text and PDFs to the intake endpoint, and Hedge matches appetite and opens three market lanes: Instant Quote, Binding, and Specialty. From there you read the markets being tried, answer outstanding requirements, act on released quotes, and request a bind, all scoped to your own brokerage by the access token.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D-Signals: 4

50%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

14%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

47%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

33%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

91%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: ASignals: 1

85%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Hedge Submission API to your agent

Capabilities

Start building with Hedge Submission API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hedgespecialty Hedge Submission API

Jentic AI Readiness Score

Hedge Submission API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness