Install Jentic One Beta

Connect the Placetel API to your agent

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

Create an agent

Fetch all call center agents

Update an agent

Pick a call center call

Use Cases

Patterns agents use Placetel API for, with concrete tasks.

★ Developer Tools Operations

GET STARTED

Start building with Placetel API

Explore with Jentic One

View OpenAPI Document

Automated Call_Center_Agents Management

Automate call_center_agents operations by combining multiple Placetel API endpoints. Agents can fetch all call center agents and then update an agent in a single workflow.

Call GET /call_center_agents to fetch all call center agents, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Placetel 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 'create an agent', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

118 endpoints — --- introduction <h2>create custom integrations or automate your workflows with the placetel rest api.

METHOD

PATH

DESCRIPTION

POST

/call_center_agents

Create an agent

GET

/call_center_agents

Fetch all call center agents

PUT

/call_center_agents/{id}

Update an agent

GET

/call_center_calls

Fetch all call center calls

POST

/call_center_calls/{id}/{pick}

Pick a call center call

POST

/call_center_queues

Create a queue

GET

/call_center_queues

Fetch all call center queues

PUT

/call_center_queues/{id}

Update a queue

POST

/call_center_agents

Create an agent

GET

/call_center_agents

Fetch all call center agents

PUT

/call_center_agents/{id}

Update an agent

GET

/call_center_calls

Fetch all call center calls

POST

/call_center_calls/{id}/{pick}

Pick a call center call

POST

/call_center_queues

Create a queue

GET

/call_center_queues

Fetch all call center queues

PUT

/call_center_queues/{id}

Update a queue

Why Jentic?

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

Setup

Wiring Placetel by hand means learning its Authorization header token auth and hand-building requests across its call-center agent, call and queue endpoints yourself. Through Jentic you install once, import Placetel from the API Directory, store the token once, and your agent calls it.

Permission scoping

Placetel puts the resource id in the URL path (/call_center_agents/{id}, /call_center_queues/{id}), so a rule can pin your agent to one agent or queue: it reads and updates that resource and nothing else. You choose the operations it may call, so state-changing ones like updating a queue are not included unless you add them.

Credential isolation

Your Placetel 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 'list call center agents' or 'pick up a queued call', and Jentic returns the matching Placetel operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Placetel API through Jentic.

What authentication does the Placetel API use?

The Placetel API uses an API key passed in the `Authorization` header. 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 create an agent with the Placetel API?

Yes. Use the POST /call_center_agents endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Placetel 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 create an agent through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an agent'. Jentic returns the matching Placetel API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Placetel API have?

The Placetel API exposes 118 endpoints covering call_center_agents, call_center_calls, call_center_queues operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Placetel operations and credentials the agent may use. Placetel puts the resource id in the URL path, such as /call_center_agents/{id} and /call_center_queues/{id}, so a rule can pin the agent to a single agent or queue and let it read and update only that resource. You also choose which operations are exposed, so state-changing calls like updating a queue stay out of reach unless you add them.

Placetel De Placetel API

Name: Placetel API
Brand: Placetel API
Availability: InStock

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey118 EndpointsREST

For Agents

Programmatically create an agent, fetch all call center agents. Covers 118 operations with apiKey authentication.

Use for: I need to an agent, I want to fetch all call center agents, Search for an agent, Find all fetch all call center calls

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

--- Introduction <h2>Create custom integrations or automate your workflows with the Placetel REST API.</h2> To make a request to our API, you will need to specify an HTTP **method** and a **path**. Additionally, you can specify request **headers**, **query** and **body** parameters. The API will return the response status code, response headers, and dependening on status and resource a response bo. The API exposes 118 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: BSignals: 4

81%

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

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

22%

Example Density

How richly the API is illustrated with examples.

92%

Example Validity

Percentage of examples that conform to their schemas.

25%

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: D+Signals: 4

34%

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.

61%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1

79%

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Placetel API to your agent

Capabilities

Use Cases

Start building with Placetel API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Placetel De Placetel API

Jentic AI Readiness Score

Placetel 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