Install Jentic One Beta

Connect the Plaud Partner API to your agent

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

Get Partner Access Token

Refresh Partner Access Token

Submit Transcription Task

Use Cases

Patterns agents use Plaud Partner API for, with concrete tasks.

★ Communications Operations

Use the Plaud Partner API to perform communications operations programmatically. The API provides 5 endpoints covering core functionality including get partner access token, refresh partner access token, get partner user access token.

Call POST /oauth/partner/access-token to get partner access token

GET STARTED

Start building with Plaud Partner API

Explore with Jentic One

View OpenAPI Document

Automated Authentication Management

Automate authentication operations by combining multiple Plaud Partner API endpoints. Agents can refresh partner access token and then get partner user access token in a single workflow.

Call POST /oauth/partner/access-token/refresh to refresh partner access token, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Plaud Partner 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 basic, bearer tokens manually.

Search Jentic for 'get partner access token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — plaud partner api for authentication, user token management, and ai transcription services.

METHOD

PATH

DESCRIPTION

POST

/oauth/partner/access-token

Get Partner Access Token

POST

/oauth/partner/access-token/refresh

Refresh Partner Access Token

POST

/open/partner/users/access-token

Get Partner User Access Token

POST

/open/partner/ai/transcriptions

Submit Transcription Task

GET

/open/partner/ai/transcriptions/{transcription_id}

Get Transcription Result

POST

/oauth/partner/access-token

Get Partner Access Token

POST

/oauth/partner/access-token/refresh

Refresh Partner Access Token

POST

/open/partner/users/access-token

Get Partner User Access Token

POST

/open/partner/ai/transcriptions

Submit Transcription Task

GET

/open/partner/ai/transcriptions/{transcription_id}

Get Transcription Result

Why Jentic?

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

Setup

Wiring the Plaud Partner API by hand means handling its basic auth for token exchange, its bearer auth for partner calls, choosing between the global and Japan hosts, and building the transcription request-and-poll plumbing yourself. Through Jentic you install once, import Plaud from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The Plaud Partner API delivers a transcription id in the URL path (/open/partner/ai/transcriptions/{transcription_id}) while other calls take their input in the request body, so a rule can pin your agent to one transcription for reads and otherwise scope by operation: limit it to the operations it needs, such as submitting a transcription or fetching its result. You choose which operations it may call.

Credential isolation

Your Plaud partner credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get a partner access token' or 'transcribe an audio recording', and Jentic returns the matching Plaud operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Plaud Partner API through Jentic.

What authentication does the Plaud Partner API use?

The Plaud Partner API uses basic, bearer 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 partner access token with the Plaud Partner API?

Yes. Use the POST /oauth/partner/access-token endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Plaud Partner 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 partner access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get partner access token'. Jentic returns the matching Plaud Partner API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Plaud Partner API have?

The Plaud Partner API exposes 5 endpoints covering authentication, transcription operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Plaud Partner operations and credentials the agent may use. You can scope it by operation, allowing only what it needs, such as submitting a transcription task or fetching a transcription result, while excluding the token-exchange calls. Since the transcription id sits in the URL path of GET /open/partner/ai/transcriptions/{transcription_id}, a rule can also pin reads to a single transcription rather than any id.

Plaud Partner API

Name: Plaud Partner API
Brand: Plaud Partner API
Availability: InStock

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsVoice Telephonybasic, bearer5 EndpointsREST

For Agents

Programmatically get partner access token, refresh partner access token. Covers 5 operations with basic, bearer authentication.

Use for: I need to partner access token, I want to refresh partner access token, Search for partner user access token, Find all submit transcription task

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

Plaud Partner API for authentication, user token management, and AI transcription services. Plaud is an AI voice recorder platform supporting offline and online conversational intelligence. The API exposes 5 endpoints secured with basic, bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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.

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

71%

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.

50%

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

35%

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 Plaud Partner API to your agent

Capabilities

Use Cases

Start building with Plaud Partner API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Plaud Partner API

Jentic AI Readiness Score

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