If you happen to publish a podcast usually, you already know the routine: report, add, look forward to enhancing, obtain, publish. Multiply that by 4 episodes a month and also you’re spending hours on repetitive file administration. What in case your recording software program may hand off the uncooked audio to an enhancing service routinely?
That’s precisely what the Barevalue API does. It enables you to submit uncooked podcast recordings programmatically and get again absolutely edited episodes — with filler phrases eliminated, noise decreased, quantity normalized, and present notes generated — with out ever opening a browser.
On this information, we’ll stroll by means of methods to automate your total podcast post-production pipeline utilizing the Barevalue REST API, webhooks, and our MCP server for AI assistant integration.
What You Get From the API
The Barevalue API provides you programmatic entry to the identical AI enhancing pipeline that powers the net interface. Each API order consists of:
- Full audio processing — noise discount, quantity normalization, filler phrase removing (ums, ahs), silence trimming
- Multi-track mixing — add separate host and visitor tracks, we combine them
- Transcription — full episode transcript
- AI present notes — abstract, highlights, and key takeaways
- Social media clips — AI-selected spotlight clips for promotion
- Webhook notifications — get notified the second your episode is prepared
Getting Began: Authentication
First, you’ll want an API key. Create a free Barevalue account (each account consists of bonus minutes to check with — no bank card required), navigate to Settings → API Keys, and generate a key.
All API requests use Bearer token authentication:
curl -H "Authorization: Bearer bv_sk_your_api_key_here"
https://barevalue.com/api/v1/accountThis returns your account information, subscription minutes remaining, and pricing — all the pieces you must know earlier than submitting an order.
The Three-Step Workflow
Submitting a podcast for enhancing takes three API calls:
Step 1: Get a Presigned Add URL
curl -X POST https://barevalue.com/api/v1/orders/upload-url
-H "Authorization: Bearer bv_sk_your_key"
-H "Content material-Sort: utility/json"
-d '{"filename": "episode-42.mp3", "content_type": "audio/mpeg"}'This returns a presigned S3 URL that’s legitimate for one hour. No must handle AWS credentials — the API handles it.
Step 2: Add Your Audio
curl -X PUT
-H "Content material-Sort: audio/mpeg"
--data-binary @episode-42.mp3
"https://barevalue-files.s3.amazonaws.com/..."Add on to S3 utilizing the presigned URL. This works with information as much as 750MB.
Step 3: Submit the Order
curl -X POST https://barevalue.com/api/v1/orders/submit
-H "Authorization: Bearer bv_sk_your_key"
-H "Content material-Sort: utility/json"
-d '{
"s3_key": "413/16000/uncooked/episode-42.mp3",
"podcast_name": "The Dev Present",
"episode_name": "Episode 42: API Automation"
}'That’s it. The AI pipeline picks up your order, processes it, and delivers the outcomes. Typical turnaround is below half-hour for episodes as much as an hour.
Multi-Monitor Assist
Recording with separate microphones for host and visitor? The API handles multi-track uploads natively:
curl -X POST https://barevalue.com/api/v1/orders/upload-urls
-H "Authorization: Bearer bv_sk_your_key"
-H "Content material-Sort: utility/json"
-d '{
"information": [
{"filename": "host.mp3", "content_type": "audio/mpeg", "size_bytes": 45000000, "role": "host"},
{"filename": "guest.mp3", "content_type": "audio/mpeg", "size_bytes": 43000000, "role": "guest"},
{"filename": "intro.mp3", "content_type": "audio/mpeg", "size_bytes": 2000000, "role": "intro"}
]
}'Every monitor will get its personal add URL. After importing all information, submit the order utilizing the returned order_id. The AI handles mixing, stage matching between audio system, and all post-production.
Submit by URL (No Add Wanted)
Have already got your audio hosted someplace? Skip the add completely:
curl -X POST https://barevalue.com/api/v1/orders/submit-url
-H "Authorization: Bearer bv_sk_your_key"
-H "Content material-Sort: utility/json"
-d '{
"url": "https://your-server.com/recordings/episode-42.mp3",
"podcast_name": "The Dev Present",
"episode_name": "Episode 42"
}'The API downloads the file and processes it. That is notably helpful should you report to a cloud service or have a recording bot that saves to a server.
Webhooks: Get Notified When It’s Completed
As a substitute of polling for order standing, register a webhook and we’ll POST to your endpoint when the order completes:
curl -X POST https://barevalue.com/api/v1/webhooks
-H "Authorization: Bearer bv_sk_your_key"
-H "Content material-Sort: utility/json"
-d '{
"url": "https://your-server.com/webhook/barevalue",
"occasions": ["order.completed", "order.failed"],
"secret": "your_webhook_secret"
}'When an order completes, you obtain a signed POST with the order particulars and obtain hyperlinks. Confirm the signature utilizing your webhook secret, obtain the information, and publish — all with out human intervention.
Actual-World Automation: A Full Pipeline
Right here’s what a completely automated podcast pipeline seems to be like in Python:
import requests
import os
API_KEY = os.environ["BAREVALUE_API_KEY"]
BASE = "https://barevalue.com/api/v1"
HEADERS = {"Authorization": f"Bearer {API_KEY}"}
def process_episode(audio_path, podcast_name, episode_name):
# 1. Get add URL
resp = requests.put up(f"{BASE}/orders/upload-url", headers=HEADERS, json={
"filename": os.path.basename(audio_path),
"content_type": "audio/mpeg"
})
upload_info = resp.json()
# 2. Add the file
with open(audio_path, "rb") as f:
requests.put(
upload_info["upload_url"],
headers={"Content material-Sort": "audio/mpeg"},
knowledge=f
)
# 3. Submit the order
resp = requests.put up(f"{BASE}/orders/submit", headers=HEADERS, json={
"s3_key": upload_info["s3_key"],
"podcast_name": podcast_name,
"episode_name": episode_name
})
order = resp.json()
print(f"Order {order['order_id']} submitted. Standing: {order['state']}")
return order
# Course of an episode
process_episode("raw-episode-42.mp3", "The Dev Present", "Episode 42")Pair this with a webhook handler and you’ve got a zero-touch pipeline: report → add → edited episode lands in your publishing queue.
MCP Server: Use Barevalue From Claude Code
If you happen to use Claude Code or one other AI coding assistant that helps the Mannequin Context Protocol (MCP), you possibly can submit and handle podcast orders instantly out of your IDE.
Fast Setup (2 minutes)
Add Barevalue to your Claude Code configuration:
# In your Claude Code settings, add this MCP server:
{
"mcpServers": {
"barevalue": {
"command": "npx",
"args": ["-y", "barevalue-mcp"],
"env": {
"BAREVALUE_API_KEY": "bv_sk_your_api_key_here"
}
}
}
}That’s it. Restart Claude Code and now you can speak to it naturally:
- “Submit episode-42.mp3 for enhancing” — uploads and submits the file
- “Verify the standing of my orders” — lists latest orders with their state
- “What number of minutes do I’ve left?” — reveals your subscription stability
- “Arrange a webhook at https://my-server.com/hook” — registers a completion webhook
The MCP server exposes 12 instruments that map to all API endpoints — account information, file add, order submission, standing checks, webhook administration, and API key rotation. View the total instrument reference on GitHub.
Pricing
API orders use your present subscription minutes — no separate API pricing. Each new account consists of bonus minutes to check the total pipeline. Verify our pricing web page for present plans and charges.
Getting Began
Able to automate your podcast enhancing?
- Create a free account — bonus minutes included, no bank card required
- Generate an API key from Settings → API Keys
- Submit your first order utilizing the curl examples above
- Register a webhook for completion notifications
- Optionally, set up the MCP server for Claude Code integration
Full API documentation is offered in your account dashboard after signup.
Questions? Attain us at assist@barevalue.com.
