This is the entry point for all Ollang API operations. Based on the user's intent, delegate to the appropriate sub-skill below.
Sub-SkillWhen to Useollang-healthUser wants to check if the API is upollang-uploadUser wants to upload a video, audio, document, or VTT fileollang-order-createUser wants to create a translation, CC, subtitle, or dubbing orderollang-order-getUser wants to check the status or details of a specific orderollang-orders-listUser wants to list, search, or filter their ordersollang-order-cancelUser wants to cancel an orderollang-order-rerunUser wants to rerun or regenerate an orderollang-revisionUser wants to report an issue or manage revisions on an orderollang-human-reviewUser wants to request or cancel human (linguist) reviewollang-qc-evalUser wants to run a quality control evaluation on an orderollang-projectUser wants to list or inspect projectsollang-folderUser wants to list or find folders
A complete end-to-end translation workflow looks like this:
text
1. Upload file → ollang-upload → returns projectId
2. Create order → ollang-order-create → returns orderId(s)
3. Monitor status → ollang-order-get → poll until "completed"
4. Quality check → ollang-qc-eval → scores + segment analysis
5. Report issues → ollang-revision → create revisions if needed
6. Upgrade to human → ollang-human-review → optional linguist review
All endpoints (except health check) require the X-Api-Key header.
The API key is read from the OLLANG_API_KEY environment variable.
If the variable is not set, instruct the user to configure it:
bash
export OLLANG_API_KEY=<your-api-key>
Get your API key at https://lab.ollang.com.
text
https://api-integration.ollang.com
OLLANG_API_KEY environment variable. If not set, tell the user to set it with: export OLLANG_API_KEY=<your-api-key>