Back to Browse
ManyLives Subtitle Check
x402
ManyLives Subtitle Check is a paid API for AI agents from api.manylives.me, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-18).
Validates SRT or WebVTT subtitle files against broadcast/streaming standards, flagging issues like reading speed, line length, glossary misspellings, and timing gaps
Price / call$0.003
Success—
StatusUnknown
How this service works
Pay-per-call tools for people building AI agents: live web search and page contents, point-in-time crypto market data and news for backtests (no lookahead), verifiable track records of 1,000 crypto strategies locked on the Base network, company profiles, quick AI and batch prices. Ask us to turn a public website into a JSON endpoint. Pay per call, no account, free trial.
Output
A JSON object containing: total cue count, pass/fail boolean, detected format (srt or vtt), an array of issues each with timestamp, cue number, check name, and detail message, plus a summary count of issues grouped by check type (e.g. reading speed, glossary, line too long).
Example use cases
Pre-delivery broadcast compliance check
“Before I send these subtitles to the broadcaster, can you validate this SRT file to make sure nothing exceeds 20 characters per second and no line is too long? Here's the content: [SRT text].”
Localization glossary enforcement
“I have a WebVTT subtitle file where character names need to be spelled correctly — 'María' should never appear as 'Maria' and 'Lúc' never as 'Luc'. Can you check the whole file and list every violation with timestamps?”
Children's content subtitle audit
“These subtitles are for a kids' show, so reading speed must stay at or below 17 characters per second. Please check this SRT file and tell me every cue that's too fast along with what time it happens.”
Technical details
Endpoint
POSThttps://api.manylives.me/paid/text/subtitle-check?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need automated, per-cue quality assurance of subtitle files against configurable broadcast or streaming standards (reading speed, line length, CPS, timing gaps) and optional glossary enforcement. Prefer this over manual review or generic text analysis when you need structured issue reports with exact timestamps and cue numbers, suitable for pipeline integration before subtitle delivery.
Side effects
- Malformed or unparseable SRT/VTT input returns an error
- Missing 'subtitles' field returns a validation error
- Limits object with invalid keys or types may be ignored or cause an error
- Very large subtitle files may time out or be truncated
- Glossary with incorrect JSON structure may not be applied
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| limits | string | optional {max_chars, max_lines, max_cps, min_ms, max_ms, fps, min_gap_frames} |
| children | string | optional true: 17 characters a second |
| glossary | string | optional {"Right name": ["wrong spelling", ...]} |
| subtitles | string | the SRT or WebVTT text |
Output
Schema · Response
{
"type": "json",
"example": {
"cues": 412,
"pass": false,
"format": "srt",
"issues": [
{
"at": "00:03:12.400",
"cue": 57,
"check": "reading speed",
"detail": "23.4 characters a second; maximum 20."
}
],
"issues_by_check": {
"glossary": 1,
"line too long": 1,
"reading speed": 3
}
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"