canonical: https://jentic.com/apis/plaud.ai/plaud

# Plaud Partner API

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.

## For AI agents

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

## Scope

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

## Capabilities

- Get Partner Access Token
- Refresh Partner Access Token
- Submit Transcription Task

## Use cases

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

Example prompt: Call POST `/oauth/partner/access-token` to get partner access token

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

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

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

## Key endpoints

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

## Key resources

- **Authentication** — Partner authentication and token management endpoints.
- **Transcription** — AI transcription task submission and result retrieval endpoints (Beta).

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 35 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/plaud.ai/plaud/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 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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

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

## FAQ

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