Endpoints
Communication
Replies, triage, minutes, and outreach, ready to send.
Summarize
POST /v1/summarize$0.03/call
A meeting transcript, thread, or report → a tight summary, key points, and extracted action items.
curl https://api.kynth.studio/v1/summarize \
-H "Authorization: Bearer $KYNTH_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"<meeting transcript…>","length":"standard"}'Example response
200 OK
{
"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
}
}Sentiment
POST /v1/sentiment$0.02/call
Turn a review or support message into a sentiment score, per-aspect breakdown, and the themes driving it.
curl https://api.kynth.studio/v1/sentiment \
-H "Authorization: Bearer $KYNTH_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"Love the product but support took days to reply.","aspects":["product","support"]}'Example response
200 OK
{
"sentiment": "neutral",
"score": 0.1,
"confidence": 0.88,
"aspects": [
{
"aspect": "product",
"sentiment": "positive",
"score": 0.8
},
{
"aspect": "support",
"sentiment": "negative",
"score": -0.6
}
],
"themes": [
"slow support response"
],
"usage": {
"credits": 2,
"balanceRemaining": 476
}
}Reply drafting
POST /v1/reply$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.
curl https://api.kynth.studio/v1/reply \
-H "Authorization: Bearer $KYNTH_API_KEY" \
-H "Content-Type: application/json" \
-d '{"thread":"Customer: I was charged twice for order 5561 and support hasn't replied in 3 days.","context":"Duplicate charge confirmed in Stripe; refund takes 5-10 days.","tone":"apologetic","goal":"Refund the duplicate, keep the customer","senderName":"Sam"}'Example response
200 OK
{
"reply": "Hi — you're right, and I'm sorry about the silence. I've refunded the duplicate charge just now…",
"subject": "Re: Double charge on order 5561 — refunded",
"internalNote": "Refund issued; check why the retry fired twice on this order.",
"usage": {
"credits": 5,
"balanceRemaining": 318
}
}Ticket triage
POST /v1/triage$0.03/ticket
A support ticket → priority, category, the team it belongs to, sentiment, SLA risk, and a suggested first response.
curl https://api.kynth.studio/v1/triage \
-H "Authorization: Bearer $KYNTH_API_KEY" \
-H "Content-Type: application/json" \
-d '{"ticket":"Subject: URGENT site down\nOur checkout has been erroring for 2 hours, we're losing sales.","categories":["bug","billing","how-to"],"teams":["payments","platform","support"]}'Example response
200 OK
{
"priority": "urgent",
"category": "bug",
"team": "payments",
"sentiment": "frustrated",
"slaRisk": true,
"summary": "Checkout erroring 2h in production — revenue impact.",
"suggestedFirstResponse": "Acknowledge outage, confirm engineers engaged, promise 30-min updates.",
"usage": {
"credits": 3,
"balanceRemaining": 315
}
}Meeting minutes
POST /v1/minutes$0.06/transcript
A meeting transcript → clean minutes: summary, decisions made, action items with owners, and open questions.
curl https://api.kynth.studio/v1/minutes \
-H "Authorization: Bearer $KYNTH_API_KEY" \
-H "Content-Type: application/json" \
-d '{"transcript":"<45-minute product sync transcript…>","attendees":["Priya","Marco","Dana"]}'Example response
200 OK
{
"title": "Product sync — launch readiness",
"summary": "Launch moves to Friday behind the payment fix…",
"decisions": [
"Launch Friday, not Thursday"
],
"actionItems": [
{
"task": "Deploy duplicate-charge fix",
"owner": "Priya",
"due": "2026-07-10"
}
],
"openQuestions": [
"Does the churn dashboard need the new events?"
],
"usage": {
"credits": 6,
"balanceRemaining": 309
}
}Outreach sequence
POST /v1/outreach$0.06/sequence
An enriched lead plus what you sell → a personalized outreach sequence that references what actually makes them a fit.
curl https://api.kynth.studio/v1/outreach \
-H "Authorization: Bearer $KYNTH_API_KEY" \
-H "Content-Type: application/json" \
-d '{"lead":"{…/v1/enrich output for brightco.io…}","product":"Kynth Verbatim — meeting notes that write themselves","sender":{"name":"Isaiah","role":"Founder","company":"Kynth"},"steps":2}'Example response
200 OK
{
"sequence": [
{
"day": 0,
"subject": "Notes for BrightCo's client calls",
"message": "Hi Dana — saw BrightCo runs 20+ client calls a week…"
},
{
"day": 4,
"subject": null,
"message": "Bumping this — one line…"
}
],
"personalizationPoints": [
"Agency model = heavy client-call volume",
"Recent hiring spree in account management"
],
"usage": {
"credits": 6,
"balanceRemaining": 303
}
}Review response
POST /v1/review-reply$0.03/review
A customer review → a brand-safe public response, the issues to log, and whether it needs human escalation.
curl https://api.kynth.studio/v1/review-reply \
-H "Authorization: Bearer $KYNTH_API_KEY" \
-H "Content-Type: application/json" \
-d '{"review":"Two stars. The product is fine but delivery took three weeks and nobody answered my emails.","rating":2,"business":{"name":"Loomworks","voice":"warm, direct, no corporate speak"},"resolution":"free shipping on next order"}'Example response
200 OK
{
"reply": "That's on us — three weeks is far too long, and going quiet made it worse…",
"sentiment": "negative",
"issues": [
"Shipping delay (3 weeks)",
"Support unresponsive via email"
],
"escalate": false,
"usage": {
"credits": 3,
"balanceRemaining": 300
}
}