Skip to main content
Melso Agents is available only internally or by private invitation. Agents-specific features require existing access. For the autónomo fiscal service, see Get started.
Create and organize durable conversations. Execution happens in Runs. Read the workflow guide before making changes. The endpoint pages below contain the request and response schemas. Company membership and credential scope apply to every operation. Agents-only capabilities require existing private access. A company API key does not grant every route merely because it belongs to the company.

​
Creation constraints

These field descriptions come from the POST /api/tasks request schema in the OpenAPI contract. Use the endpoint pages for the full request and response shapes.

​
metadata

metadata: A flat map of strings, numbers and booleans with at most 50 keys. Keys match ^[a-zA-Z_][a-zA-Z0-9_.-]$. The encoded create value and stored JSONB each have an 8 KiB limit; storage size is checked by the server, not by a JSON Schema character limit. Null values, arrays and nested objects are rejected.

​
instructions

instructions: Immutable guidance for every Run on the Task. At most 32768 UTF-8 bytes and no NUL characters. The server checks bytes, not Unicode character count. Run credentials cannot configure this field.

​
MCP servers

mcp_servers: At most 10 servers with unique, non-reserved names. Each server uses exactly one of a remote HTTPS url or a stdio command. headers belong to remote servers; args and env belong to stdio servers. The encrypted set is limited to 64 KiB; the server rejects a larger sealed set with HTTP 413. This encrypted-size limit cannot be measured as JSON character count. Header and environment values are write-only; GET returns McpServerSummary objects.

​
repositories

repositories: At most 20 repository grants, fixed at Task creation. Requires an admin company key and an enabled integration broker. Each grant names a canonical GitHub HTTPS URL, read or write permission and a credential_reference identifying an authorization grant, never a token. The broker response must contain token, expires_at and permission matching the request. expires_at must be more than 30 seconds and at most 70 minutes after the exchange validation time. This expiry rule applies to the broker response, not to a Task creation field.