Install Jentic One Beta

Connect the Curacel Health Developer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Curacel Health Developer 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%2Fcuracel.co%2Fcuracel" | 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%2Fcuracel.co%2Fcuracel" | 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 Curacel Health Developer API.

Submit health insurance claims to insurers for auto-adjudication

Create and track pre-authorization requests and their decisions

Look up an enrollee's benefits and utilisation over a period

Configure insurer plans, plan benefits, and care-type mappings

GET STARTED

Start building with Curacel Health Developer API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Curacel Health Developer API for, with concrete tasks.

★ Agent-Submitted Insurance Claims

An AI agent embedded in an electronic medical record system can file claims through Jentic without a developer wiring the calls: it creates a claim for an enrollee, links supporting attachments, and reads the claim's details to confirm it reached the insurer for adjudication. The same flow surfaces pre-authorization status so the agent knows whether a procedure is covered before submitting.

Create a claim for an enrollee, link a supporting attachment, and fetch the claim details to confirm it was received

Pre-Authorization Workflows

Providers often need approval before delivering a procedure, and Curacel handles the round trip. A pre-authorization request is created against an enrollee and plan, and its status can be polled until the insurer approves or declines. This lets a clinic confirm coverage up front and attach the authorization to the eventual claim.

Create a pre-authorization request for a procedure and retrieve its approval status

Enrollee Benefits and Eligibility

Before treatment, staff need to know what an enrollee's plan covers and how much they have already used. Curacel returns an enrollee's benefits and sums their utilisation over a period, so an agent can confirm remaining coverage and the right plan benefit before a claim is filed.

Fetch an enrollee's benefits and sum their utilisation over the current period to confirm remaining coverage

Key Endpoints

36 endpoints — the curacel health api submits health insurance claims to insurers for auto-adjudication and manages the records around them.

METHOD

PATH

DESCRIPTION

POST

/v1/claims

Create a claim

GET

/v1/claims

Fetch a list of claims

GET

/v1/claims/{id}

Get the details of a single claim

POST

/v1/pa-requests

Create a pre-authorization request

POST

/v1/enrollees

Create or update an enrollee

GET

/v1/encounters

List encounters

GET

/v1/providers

Get providers

POST

/v1/claims

Create a claim

GET

/v1/claims

Fetch a list of claims

GET

/v1/claims/{id}

Get the details of a single claim

POST

/v1/pa-requests

Create a pre-authorization request

POST

/v1/enrollees

Create or update an enrollee

GET

/v1/encounters

List encounters

GET

/v1/providers

Get providers

Why Jentic?

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

Setup

Wiring the Curacel Health API by hand means handling its bearer token, the login exchange for a temporary access token, and the split between its production and sandbox hosts. Through Jentic you install once, import Curacel from the API Directory, store the token once, and your agent calls it.

Permission scoping

Curacel puts the claim id, enrollee id, and plan id in the URL path, so a rule can pin your agent to the claim and enrollee reads and writes it needs. Destructive operations like attachment deletion or enrollee status changes stay out of that set unless you add them.

Credential isolation

Your Curacel token 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 'file a claim' or 'check enrollee benefits', and Jentic returns the matching Curacel operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Curacel Health Developer API through Jentic.

What authentication does the Curacel Health API use?

The Curacel Health API authenticates with a bearer token per its OpenAPI spec: you send an Authorization header carrying the API key from your account dashboard, and you can exchange login credentials for a temporary access token through the auth endpoint. Through Jentic the token is stored once, encrypted, by your own Jentic One instance and injected at call time.

Can I submit insurance claims with the Curacel Health API?

Yes. You can create a claim for an enrollee, link supporting attachments to it, list claims, and fetch a single claim's details to track adjudication. Pre-authorization requests and enrollee benefit lookups round out the claims workflow.

What are the rate limits for the Curacel Health API?

The OpenAPI spec does not define rate limits for the Curacel Health API. Check the Curacel documentation at https://docs.curacel.co for current limits.

Is there a Curacel MCP server?

You don't need an MCP server to connect your agent to the Curacel Health API. Jentic imports it directly from the API Directory: store your key once and your agent can submit claims, create pre-authorization requests, and look up enrollee benefits. Operations are discovered on demand without loading another server's tool definitions into context.

Can I limit what my agent is allowed to do with the Curacel Health API?

Yes. Write a rule that allows only the operations the task needs, such as creating claims and reading claim details, so destructive operations like deleting attachments or changing enrollee status are not included unless you add them. Every call the agent makes is logged.

How do I submit a claim with the Curacel Health API through Jentic?

Search Jentic for 'submit a health insurance claim', and it returns the matching Curacel operations with their input schemas. Your agent creates the claim, links any attachments, and reads the claim details to confirm receipt. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Curacel Health Developer API

AI ReadinessFoundational (C)56/100

See full scorecard

Official vendor OpenAPI document · agent-readyHealthcareEhr Emrbearer36 EndpointsREST

For Agents

Submit health insurance claims to insurers and track their adjudication: raise pre-authorization requests, register enrollees, and check benefits and utilisation. Configure insurer plans, plan benefits, providers, and encounters.

Use for: I want to submit a health insurance claim, Create a pre-authorization request for a procedure, Check an enrollee's benefits and utilisation, Register a new enrollee on a plan

Not supported: Does not handle appointment scheduling, clinical charting, or pharmacy dispensing. Use for health insurance claims, pre-authorization, and enrollee administration only.

The Curacel Health API submits health insurance claims to insurers for auto-adjudication and manages the records around them. It lets electronic medical record systems and insurer platforms create claims, raise pre-authorization requests, register enrollees, and look up their benefits and utilisation. Insurer plans, plan benefits, providers, and encounters round out a workflow that moves a claim from submission to a tracked decision.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

90%

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).

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: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

53%

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: FSignals: 4

45%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

58%

OperationId Quality

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

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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

72%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Curacel Health Developer API to your agent

Capabilities

Start building with Curacel Health Developer API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Curacel Health Developer API

Jentic AI Readiness Score

Curacel Health Developer 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