Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"specialist_ids",
"title",
"description",
"problem_context",
"budget",
"language",
"user_confirmed"
],
"properties": {
"title": {
"type": "string"
},
"budget": {
"type": "number",
"minimum": 0
},
"language": {
"enum": [
"English",
"Polish",
"French",
"German",
"Spanish",
"Italian"
],
"type": "string",
"description": "The task's language — must match the language the user phrased title/description in (there is no auto-detection, set it according to the user's input)."
},
"timeline": {
"enum": [
"In a week",
"In a month",
"In 3 months",
"No rush",
"Do not know"
],
"type": "string",
"default": "No rush",
"description": "How urgent the project is from the client's perspective — ask the user directly, do not guess."
},
"description": {
"type": "string"
},
"context_files": {
"type": "array",
"items": {
"type": "object",
"required": [
"name"
],
"properties": {
"url": {
"type": "string",
"format": "uri"
},
"name": {
"type": "string"
},
"content_base64": {
"type": "string"
}
},
"additionalProperties": false
},
"description": "The minimal set of files the specialist needs. Each entry is { name, url?, content_base64? } and must carry exactly one source. `url` is strongly preferred: pass a link if the user gave one (Google Drive / Dropbox / S3 / raw GitHub) — the server rewrites common Google Drive and Dropbox share links to their direct-download form, and rejects a URL that returns a web page instead of a file — or, if you have a way to upload the file yourself (e.g. a code execution / shell environment) — upload it to any URL-reachable location first and pass that link instead of the raw bytes; the server just downloads it, which is fast and costs you almost no extra tokens. Use `content_base64` only as a last resort, when there is no URL and you have no way to produce one yourself (e.g. a small file the user attached directly in a chat-only client with no upload capability of its own) — inlining bytes means writing out the entire file as text, which is slow and burns far more tokens than a URL for anything beyond a tiny file. Before falling back to it, tell the user that creating the task will take noticeably longer and use more tokens because of it. Raw base64 only, never a `data:...;base64,` prefix. This server runs remotely and cannot read the caller's disk, so never pass local paths. The server scans every file for secrets, then uploads the rest to the task's file storage on Stoory; contents never enter the model context. Max 5MB per file. Entries that are unreadable or filtered as secrets come back in blocked_files — the task is still created without them."
},
"specialist_ids": {
"type": "array",
"items": {
"type": "string"
},
"minItems": 1,
"description": "Id of one or more specialists to invite."
},
"user_confirmed": {
"type": "boolean",
"description": "Must be true — set it only after the user's explicit confirmation in the conversation."
},
"problem_context": {
"type": "string"
}
},
"additionalProperties": false
}