Communication ↗
Summarize
A meeting transcript, thread, or report → a tight summary, key points, and extracted action items.
POST /v1/summarize$0.03/call · 3 credits, charged only on success
Send this
{
"text": "<meeting transcript…>",
"length": "standard"
}Every response carries usage — the credits burned and your remaining balance. A failed call never burns credits.
Try it live against your own key in the interactive reference; every account gets 500 free credits a month, no card.
Get this back
{
"summary": "The team agreed to ship the billing fix Friday…",
"keyPoints": [
"Billing bug root-caused",
"Launch moved to Fri"
],
"actionItems": [
{
"task": "Deploy the fix",
"owner": "Priya"
}
],
"usage": {
"credits": 3,
"balanceRemaining": 481
}
}Four ways in. Same $0.03/call.
curl
curl https://api.kynth.studio/v1/summarize \
-H "Authorization: Bearer ksk_live_…" \
-H "Content-Type: application/json" \
-d '{"text":"<meeting transcript…>","length":"standard"}'TypeScript
import { KynthCore } from "@kynth/api";
const kynth = new KynthCore({ apiKey: process.env.KYNTH_API_KEY! });
const result = await kynth.summarize({
"text": "<meeting transcript…>",
"length": "standard"
});Python
from kynth import Kynth
client = Kynth(api_key=os.environ["KYNTH_API_KEY"])
result = client.summarize(
text="<meeting transcript…>",
length="standard",
)MCP
// One-time setup in your MCP client (Claude, Cursor, …):
{ "mcpServers": { "kynth-core": {
"command": "npx", "args": ["@kynth/api-mcp"],
"env": { "KYNTH_API_KEY": "ksk_live_…" } } } }
// Then the agent just calls the kynth_summarize tool.More from communication
Sentiment
$0.02/call
Turn a review or support message into a sentiment score, per-aspect breakdown, and the themes driving it.
Reply drafting
$0.05/reply
A customer thread plus your context → a ready-to-send reply in the right tone, with an internal note for the agent.
Ticket triage
$0.03/ticket
A support ticket → priority, category, the team it belongs to, sentiment, SLA risk, and a suggested first response.