> ## Documentation Index
> Fetch the complete documentation index at: https://docs.melso.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Melso product MCP: https://melso.ai/api/mcp (OAuth; one company per grant). REST: https://melso.ai. Documentation-search MCP: https://docs.melso.ai/mcp. The docs search server does not act on customer accounts.
>
> Use the live tool schema and respect company membership. Ask the person to authorize the exact fiscal document version in the signed-in app. A professional prepares and files included returns after authorization; AI does not file alone. A prepared file or approval receipt is not evidence of filing. Never claim completion from an accepted Task or Run. Keep credentials out of chat and logs. Agents features are internal or by private invitation.

# Artifacts

> Keep versioned files and static apps as Task deliverables, with private previews and explicit publication.

<Info>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](/essentials/quickstart).</Info>

Artifacts are versioned Task deliverables: files or static apps. A new upload
creates a private preview. Publishing selects the live version, and every
completed version is retained.

## Deliver a file or app

Use [artifacts\_deploy](/mcp/tools/artifacts-deploy) to prepare and complete a file or app upload. Its action schema describes the upload receipt and required fields. Inspect the private preview before choosing publication through [artifacts\_manage](/mcp/tools/artifacts-manage).

Use relative asset paths and hash routing for static apps. Generated apps use
`window.melso` in the isolated viewer, with explicit table, field, and action
grants. Never embed an API key or general account credential in an app.

## Edit a retained version

Use [artifacts\_get](/mcp/tools/artifacts-get) with an identifier from your own Artifact to inspect its retained source and version metadata.

Publishing an older version changes its code while retaining current table
data and grants. Private sources require authenticated access and are not
included in public responses.

Use [artifacts\_manage](/mcp/tools/artifacts-manage) to choose which version is published and who can access it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.