Publish a website
publish_sitePublish files as a live website, served over HTTPS at its own URL. Use it when the user asks to publish, host, or share a report, page, dashboard, or other static files at a URL. Naming Valet only chooses where; it is not a request to publish. Honor an artifact form the user requests; otherwise choose the form and treatment from its audience, job, and material. A request for a live URL chooses delivery, not one long scrolling page.
Read the organization's requirements with get_skill governance before calling. A policy set to block refuses a publish that fails it, and the answer names what to fix; a monitor policy only records findings, which get_evaluation lists.
title and description are required on every publish of files. Write them for the person who comes back to this page in a month: the site's name is only part of its URL.
files suits a few small text pages (HTML, CSS, JavaScript, Markdown, JSON, SVG). For a large site or binary assets, call create_push, push with git, and pass push instead.
Publishing changes the content of a permanent site that already exists: create it first with create_service (kind: site), then publish to its name. It leaves the site's access mode and shares as they are; set_service_access and share_service change them.
Returns the site's URL and access mode, the version that went live, and the release's evaluation when it has one. In an organization with release policies, an account publish answers with evaluation and no version: the release waits for its policies, and get_evaluation follows it. Files or a push whose tree the site already serves answer no_changes and publish nothing.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>"
},
"name": "publish_site"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The site's name, which is the first label of its URL, https://<name>.<org>.valet.run. The site must exist: create it first with create_service. Publishing to it replaces its files. | |
| push | No | Publish a Git push instead of files: the id create_push returned and the commit you pushed to its branch. Use it when you can run git with network access, because it sends only what changed. Every other argument keeps its meaning. | |
| files | No | The site's files. Give this or push, not both. Include index.html, the page the site's URL opens; add more for stylesheets, scripts, or further pages. | |
| title | No | What the site is called, written for a person: 'Q3 Migration Audit', not a hostname. It labels the site wherever it is listed, so write the same thing the page's own <title> says. | |
| org_name | No | The Valet organization to publish into. Omit to use the organization the account joined first. | |
| description | No | One sentence saying what the site holds, for a person deciding whether to open it. It is shown beside the title wherever the site is listed. | |
| idempotency_key | No | An opaque key of your choosing. Repeating a call with the same key returns the first call's result instead of publishing again, which makes a retry safe. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| org | Yes | Name of the Valet organization the call acted in. | |
| url | No | URL that serves the site. Absent while the site has no route. | |
| name | Yes | Name of the site. It is the first label of its URL. | |
| access | Yes | Who can open the site: public, private, or password. Change it with set_service_access. | |
| version | No | Version number of the release the publish made live. Absent when no release went live: the release waits for its policies (see evaluation) or nothing changed. | |
| evaluation | No | The release evaluation. Without version, the release waits for its policies: follow it with get_evaluation. With version, the release is live and this is its monitor-only evaluation. Absent when the release has none. | |
| no_changes | No | True when the files or pushed tree are what the site already serves, so nothing was published. Absent otherwise. |