canonical: https://jentic.com/apis/tellescope.com/tellescope

# Tellescope Healthcare API

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.

## For AI agents

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

## Scope

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

## Capabilities

- Submit a support ticket
- Create an agent record
- List agent records
- Get an agent record by ID
- Update an agent record
- Delete an agent record

## Use cases

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

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **AgentRecords** — Manage agent records and support tickets
- **AIConversations** — AI-powered conversations and decision generation
- **AllergyCodes** — Manage allergy code references
- **Analytics** — Analytics frames, queries, and custom reports

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 58 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 82 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 33 / 100
  - AI Discoverability: 54 / 100
- **View full report:** https://jentic.com/apis/tellescope.com/tellescope/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

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