Install Jentic One Beta

Connect the canhelpto public API to your agent

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

Open a support ticket on behalf of a customer with a subject and first message

Post public replies on an existing ticket so the conversation continues

Let a customer close or reopen their own ticket by its id

Collect a 1-to-5 CSAT rating when a ticket is resolved

Capture quick GOOD, NEUTRAL, or BAD feedback with a comment

GET STARTED

Start building with canhelpto public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use canhelpto public API for, with concrete tasks.

★ Agent-Run Support Triage

An AI support agent opens tickets, posts replies, and tracks resolved conversations for a single canhelpto workspace through Jentic. Because every call carries the workspace key in the X-API-Key header, the agent only ever touches that one workspace's tickets, and a rule can keep it on reading and replying while service-mode status changes stay with a human. The agent discovers the right operation by intent and calls it directly.

Open a ticket about a failing mobile checkout, post the first reply with a troubleshooting step, then read the ticket until the customer closes it.

Customer Self-Service Ticketing

A web app lets customers open support tickets, read the public replies on them, and close or reopen a ticket themselves. canhelpto handles one workspace per key, returns each ticket with its public replies, and lets the customer flip a ticket's status without any service-mode access. This keeps a lightweight help desk running behind a single embedded widget.

List the current customer's open tickets, read the latest replies on each, and reopen the one they say was closed too early.

Post-Resolution CSAT and Feedback

After a ticket is resolved, collect a 1-to-5 CSAT score from the link in the resolution email and capture quick GOOD, NEUTRAL, or BAD feedback with a comment. canhelpto exposes the CSAT rating endpoint publicly so the emailed link works without a key, while feedback and ticket operations stay behind the workspace key. Teams use this to measure support quality per resolved ticket.

Record a CSAT rating of 5 for a resolved ticket and log a GOOD feedback entry with the comment 'fast and clear'.

Key Endpoints

9 endpoints — the canhelpto api runs a lightweight support desk for one workspace: it opens tickets, lists a customer's tickets, reads a ticket with its public replies, and posts new replies on the conversation.

METHOD

PATH

DESCRIPTION

POST

/api/v1/tickets

Open a support ticket

GET

/api/v1/tickets

List a customer's tickets

GET

/api/v1/tickets/{ticketId}

Read a ticket with its public replies

POST

/api/v1/tickets/{ticketId}/replies

Post a reply on a ticket

PATCH

/api/v1/tickets/{ticketId}/status

Close or reopen a ticket

POST

/api/v1/feedback

Submit quick GOOD, NEUTRAL, or BAD feedback

GET

/api/v1/widget-config

Load the workspace widget configuration

POST

/api/v1/tickets

Open a support ticket

GET

/api/v1/tickets

List a customer's tickets

GET

/api/v1/tickets/{ticketId}

Read a ticket with its public replies

POST

/api/v1/tickets/{ticketId}/replies

Post a reply on a ticket

PATCH

/api/v1/tickets/{ticketId}/status

Close or reopen a ticket

POST

/api/v1/feedback

Submit quick GOOD, NEUTRAL, or BAD feedback

GET

/api/v1/widget-config

Load the workspace widget configuration

Why Jentic?

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

Setup

Wiring the canhelpto API by hand means handling its workspace key in the `X-API-Key` header, keeping the public widget key separate from the service key, and remembering the CSAT endpoint is open. Through Jentic you install once, import canhelpto from the API Directory, store the key once, and your agent calls it.

Permission scoping

canhelpto puts the ticket id in the URL path, so a rule can pin your agent to the ticket-read and reply operations and keep service-mode changes out. You choose the operations it may call, so status changes, reassignment, and category edits are not included unless you add them.

Credential isolation

Your canhelpto workspace 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 'open a support ticket' or 'collect a CSAT rating', and Jentic returns the matching canhelpto operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using canhelpto public API through Jentic.

What authentication does the canhelpto API use?

The canhelpto API authenticates with a workspace key sent in the `X-API-Key` header, per its OpenAPI spec. The public key (your widget id) opens what the widget can do, while service-mode actions such as changing a ticket's status need the workspace service key. The CSAT rating endpoint is public so the link in a resolution email works without a key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected only at call time.

Can I open and reply to support tickets with the canhelpto API?

Yes. The API opens a ticket, lists a customer's tickets, reads a ticket with its public replies, and posts new replies on it. A customer can also close or reopen their own ticket, while updating a ticket's status, priority, category, or assignee is a service-mode action that needs the service key.

What are the rate limits for the canhelpto API?

The OpenAPI spec does not specify rate limits for the canhelpto API. Check the vendor's agent documentation at https://canhelpto.com/docs/agents for current limits before pointing an agent at it.

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

Yes. Write a rule that allows only the ticket-read and reply operations, so the agent can open tickets, read them, and respond, but cannot run service-mode changes such as reassigning a ticket or editing its category. Every call carries your workspace key, is logged, and the agent never sees the key itself.

Is there a canhelpto MCP server?

You don't need an MCP server to give your agent the canhelpto API. Jentic connects it directly from the API Directory: import it, store your workspace key once, and your agent calls the ticket, reply, and feedback operations. You skip loading another server's tool definitions into the agent's context.

How do I handle support tickets with the canhelpto API through Jentic?

Add the canhelpto API from the Jentic API Directory and store your workspace key once. Then your agent searches by intent such as 'open a support ticket' and Jentic returns the matching operation with its input schema, so it can open the ticket and post the first reply. To run it on your own infrastructure, install Jentic One from its GitHub repo.

canhelpto public API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMCustomer SupportapiKey9 EndpointsREST

For Agents

Open and track customer support tickets, post replies, collect CSAT ratings, and read the widget configuration for one canhelpto workspace. Every call is scoped to the workspace that owns the API key.

Use for: Open a support ticket for a customer who reported a bug, List the tickets a customer has filed in this workspace, Post a reply to an open support ticket, Check whether a resolved ticket received a CSAT rating

Not supported: Does not handle live chat, email sending, or phone support. Use for workspace support tickets, replies, and CSAT feedback only.

The canhelpto API runs a lightweight support desk for one workspace: it opens tickets, lists a customer's tickets, reads a ticket with its public replies, and posts new replies on the conversation. Customers can close or reopen their own ticket, rate a resolved ticket from 1 to 5 for CSAT, and leave quick GOOD, NEUTRAL, or BAD feedback with a comment. Service-mode actions such as changing a ticket's status, priority, category, or assignee need the workspace service key, and the API also exposes the configuration the embedded web widget loads. Every request is scoped to the single workspace that owns the key.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 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).

75%

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.

42%

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

26%

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.

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

50%

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: C+Signals: 1

58%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the canhelpto public API to your agent

Capabilities

Start building with canhelpto public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

canhelpto public API

Jentic AI Readiness Score

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