canonical: https://jentic.com/apis/podsqueeze.com/podsqueeze

# Podsqueeze API

Podsqueeze is a repurposing tool for podcasters that uses AI to turn episodes into content like transcripts, summaries, and social media posts. The API exposes 1 endpoints secured with bearer authentication.

## For AI agents

Programmatically process episode. Covers 1 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for ai and machine learning only.

## Capabilities

- Process Episode
- Access Podsqueeze API resources via REST API
- Access Podsqueeze API resources via REST API

## Use cases

### AI and Machine Learning Operations

Use the Podsqueeze API to perform ai ml operations programmatically. The API provides 1 endpoints covering core functionality including process episode.

Example prompt: Call POST / to process episode

### Data Retrieval and Monitoring

Query Podsqueeze API endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows without manual intervention.

Example prompt: Query the Podsqueeze API API to retrieve current data and verify the response contains expected fields

### AI Agent Integration via Jentic

AI agents discover and call Podsqueeze 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 bearer tokens manually.

Example prompt: Search Jentic for 'process episode', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/` | Process Episode |

## Key resources

- **Episodes** — Episode processing and management

## 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:** 0 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 94 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 0 / 100
- **View full report:** https://jentic.com/apis/podsqueeze.com/podsqueeze/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 Podsqueeze API by hand means setting up bearer auth against its Cloud Functions host and posting episode jobs to a single endpoint yourself. Through Jentic you install once, import the Podsqueeze API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Podsqueeze exposes a single POST operation that takes the episode details in the request body rather than pinning a resource in the URL path, so scope the agent to just that process-episode operation. That one operation is the whole allowed set, so the agent can do nothing beyond what you grant it.
- **Credential handling:** Your Podsqueeze 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.
- **Discovery method:** Agents search Jentic by intent such as 'process a podcast episode', and Jentic returns the matching Podsqueeze operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Openai** — Alternative ai ml API
- **Anthropic** — Alternative ai ml API
- **Cohere** — Complementary ai ml API
- **Huggingface** — Complementary ai ml API

## FAQ

### What authentication does the Podsqueeze API use?

The Podsqueeze API uses a Bearer token 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 process episode with the Podsqueeze API?

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

### What are the rate limits for the Podsqueeze 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 process episode through Jentic?

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

### How many endpoints does the Podsqueeze API have?

The Podsqueeze API exposes 1 endpoints covering episodes operations.

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

Yes. The Podsqueeze API exposes a single POST operation that processes an episode, taking the episode details in the request body, so your rules in your self-hosted Jentic One instance can grant the agent only that process-episode operation. Because that one operation is the entire allowed set, the agent can do nothing beyond what you permit. Your Podsqueeze token is stored encrypted by your own Jentic One instance and injected only at execution time, so the agent never sees the raw credential.