Install Jentic One Beta

Connect the Telegram Finder API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Telegram Finder 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%2Ftelegram-finder.io%2Ftelegram-finder" | 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%2Ftelegram-finder.io%2Ftelegram-finder" | 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 Telegram Finder API.

Get rate limit information

Update contact

Delete contact

Create contacts (bulk)

Monitor Telegram Finder API operational status and events

GET STARTED

Start building with Telegram Finder API

Explore with Jentic One

View OpenAPI Document

Automated Account Management

Automate account operations by combining multiple Telegram Finder API endpoints. Agents can get account usage and then get specific contact in a single workflow.

Call GET /api/account/usage to get account usage, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Telegram Finder 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 none tokens manually.

Search Jentic for 'get rate limit information', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

11 endpoints — api documentation for telegram finder.

METHOD

PATH

DESCRIPTION

GET

/api/account/rate-limit

Get rate limit information

GET

/api/account/usage

Get account usage

GET

/api/contacts/{id}

Get specific contact

PUT

/api/contacts/{id}

Update contact

DELETE

/api/contacts/{id}

Delete contact

POST

/api/contacts

Create contacts (bulk)

GET

/api/contacts

Get user contacts

DELETE

/api/contacts

Delete contacts (bulk)

GET

/api/account/rate-limit

Get rate limit information

GET

/api/account/usage

Get account usage

GET

/api/contacts/{id}

Get specific contact

PUT

/api/contacts/{id}

Update contact

DELETE

/api/contacts/{id}

Delete contact

POST

/api/contacts

Create contacts (bulk)

GET

/api/contacts

Get user contacts

DELETE

/api/contacts

Delete contacts (bulk)

Why Jentic?

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

Setup

Wiring the Telegram Finder API by hand still means writing the HTTP client, rate-limit checks, and paging for its contacts endpoints yourself, even where it needs no credential. Through Jentic you install once, import the Telegram Finder API from the API Directory, and your agent calls it.

Permission scoping

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

Credential isolation

The Telegram Finder API needs no stored credential, so there is nothing for your Jentic One instance to hold. No secret ever enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'look up a contact' or 'check the rate limit', and Jentic returns the matching Telegram Finder API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Telegram Finder API through Jentic.

What authentication does the Telegram Finder API use?

The Telegram Finder API uses no authentication. 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 get rate limit information with the Telegram Finder API?

Yes. Use the GET /api/account/rate-limit endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Telegram Finder 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 get rate limit information through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get rate limit information'. Jentic returns the matching Telegram Finder API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Telegram Finder API have?

The Telegram Finder API exposes 11 endpoints covering account, contacts, enrich operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Telegram Finder API operations the agent may call. Because the contact id sits in the URL path (/api/contacts/{id}), you can pin the agent to a single contact so it only reads and updates that one and nothing else. You also choose the exact operations it may use, so destructive calls like deleting a contact are excluded unless you add them.

Telegram Finder API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact Managementnone11 EndpointsREST

For Agents

Programmatically get rate limit information, get account usage. Covers 11 operations.

Use for: I need to rate limit information, I want to account usage, Search for specific contact, Find all contact

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

API documentation for Telegram Finder. Rate limit - maximum 100 Telegram user search per hour. If you need higher quotas we can work to unblock them; contact valentin@telegram-finder.io. The API exposes 11 endpoints.

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

66%

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

69%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

61%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

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

84%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Telegram Finder API to your agent

Capabilities

Start building with Telegram Finder API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Telegram Finder API

Jentic AI Readiness Score

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