Install Jentic One Beta

Connect the Tellescope Healthcare API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tellescope Healthcare 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%2Ftellescope.com%2Ftellescope" | 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%2Ftellescope.com%2Ftellescope" | 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 Tellescope Healthcare API.

Submit a support ticket

Create an agent record

List agent records

Get an agent record by ID

Update an agent record

GET STARTED

Start building with Tellescope Healthcare API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Tellescope Healthcare API for, with concrete tasks.

★ Communications Operations

Use the Tellescope Healthcare API to perform communications operations programmatically. The API provides 24 endpoints covering core functionality including submit a support ticket, create an agent record, create multiple agent records.

Call POST /agent-records/submit-ticket to submit a support ticket

Automated AgentRecords Management

Automate agentrecords operations by combining multiple Tellescope Healthcare API endpoints. Agents can create an agent record and then create multiple agent records in a single workflow.

Call POST /agent-record to create an agent record, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Tellescope Healthcare API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'submit a support ticket', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

24 endpoints — tellescope is a healthcare platform api providing tools for agent records, ai conversations, allergy codes, and analytics.

METHOD

PATH

DESCRIPTION

POST

/agent-records/submit-ticket

Submit a support ticket

POST

/agent-record

Create an agent record

POST

/agent-records

Create multiple agent records

GET

/agent-records

List agent records

GET

/agent-record/{id}

Get an agent record by ID

PATCH

/agent-record/{id}

Update an agent record

DELETE

/agent-record/{id}

Delete an agent record

POST

/ai-conversations/send-message

Send a message to an AI conversation

POST

/agent-records/submit-ticket

Submit a support ticket

POST

/agent-record

Create an agent record

POST

/agent-records

Create multiple agent records

GET

/agent-records

List agent records

GET

/agent-record/{id}

Get an agent record by ID

PATCH

/agent-record/{id}

Update an agent record

DELETE

/agent-record/{id}

Delete an agent record

POST

/ai-conversations/send-message

Send a message to an AI conversation

Why Jentic?

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

Setup

Wiring the Tellescope Healthcare API by hand means provisioning its API key, attaching it to every call against api.tellescope.com/v1, and building the paging and retry handling for agent records and conversations yourself. Through Jentic you install once, import the Tellescope Healthcare API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The Tellescope Healthcare API puts the agent record id in the URL path (/agent-record/{id}), so a rule can pin your agent to one record: it can read and patch that record and nothing else. You choose the operations it may call, so destructive ones like deleting a record are not included unless you add them.

Credential isolation

Your Tellescope API key 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 a ticket' or 'read an agent record', and Jentic returns the matching Tellescope Healthcare API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Tellescope Healthcare API through Jentic.

What authentication does the Tellescope Healthcare API use?

The Tellescope Healthcare API uses an API key passed in the `apiKey` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I submit a support ticket with the Tellescope Healthcare API?

Yes. Use the POST /agent-records/submit-ticket endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Tellescope Healthcare API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I submit a support ticket through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'submit a support ticket'. Jentic returns the matching Tellescope Healthcare API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Tellescope Healthcare API have?

The Tellescope Healthcare API exposes 24 endpoints covering agentrecords, aiconversations, allergycodes operations.

Can I limit what my agent is allowed to do with the Tellescope Healthcare API?

Yes. Because you run Jentic One yourself, your own rules decide which Tellescope Healthcare API operations and credentials the agent may use. Since the agent record id sits in the URL path (/agent-record/{id}), a rule can pin the agent to a single record so it can only read and patch that record and nothing else. You choose the exact operations it may call, so destructive ones like DELETE /agent-record/{id} stay out of reach unless you add them.

Tellescope Healthcare API

AI ReadinessFoundational (C+)58/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail DeliveryapiKey24 EndpointsREST

For Agents

Programmatically submit a support ticket, create an agent record. Covers 24 operations with apiKey authentication.

Use for: I need to submit a support ticket, I want to an agent record, Search for multiple agent records, Find all agent records

Not supported: Does not handle payments, crm, or developer tools - use for communications only.

Tellescope is a healthcare platform API providing tools for agent records, AI conversations, allergy codes, and analytics. The API exposes 24 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

30%

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.

50%

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: C-Signals: 4

51%

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.

59%

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

33%

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: CSignals: 1

54%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Tellescope Healthcare API to your agent

Capabilities

Start building with Tellescope Healthcare API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tellescope Healthcare API

Jentic AI Readiness Score

Tellescope Healthcare 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