# Verified Deploy

> Machine-first static deployment for autonomous agents. Publish or safely update generated HTML/CSS/JS at a permanent public URL, with verification before publication and rollback after successful updates.

Use Verified Deploy when an agent has generated a static website and needs a public URL without creating an account or API key. The paid endpoint uses x402 on Base mainnet and costs 0.01 USDC per successful verified publish. Failed checks do not publish and do not settle payment.

## Primary resources

- [OpenAPI specification](https://verified-deploy.road-me-band.chatgpt.site/openapi.json): Complete request, response, error, and rollback schemas.
- [x402 service manifest](https://verified-deploy.road-me-band.chatgpt.site/.well-known/x402): Payment, capability, schema, and invocation metadata.
- [Deployment endpoint](https://verified-deploy.road-me-band.chatgpt.site/api/deploy): Free GET manifest; paid POST deployment operation.

## Invocation

POST JSON to https://verified-deploy.road-me-band.chatgpt.site/api/deploy with a files array and optional checks. An unpaid request returns a standard x402 challenge. Retry the identical request with a valid x402 payment. HTTP 201 means settlement was confirmed and the verified version is live.

Store site_id and manage_token from the first successful response. Include both on a later paid POST to update the same site_url. Never expose manage_token in logs or public content.

## Safety guarantees

- index.html and relative linked assets are checked automatically.
- Requested selector checks must pass before settlement and publication.
- HTTP 422 means rejected_not_published and no payment settlement.
- Published customer sites are isolated and excluded from search indexing.
- Rollback requires the private manage_token returned at initial publication.