Neynar Host
host.neynar.app- Category
- Developer Tools
- Rank
- No. 1750Tools index
Previous survey · No. 1653 ·
- Pricing
- Freemium
- Platform
- web · cli
- Type
- TOOL
- Builder
- @neynarxyz
- GitHub
- 10 stars
- Date
About
A deployment platform that lets you deploy websites with a single API call by uploading a tar file. Built for AI agents to deploy sites without human intervention, but works for developers too.
What it does
Neynar Host manages the deployment lifecycle for static, Vite, Hono, and Next.js projects. Each release receives a version, stable public address, build status, history entry, and optional description. Agents can inspect project context, follow builds, view traffic analytics, download the latest source archive, and restore earlier successful releases.
Why it's ranked here
This is a focused option for automated website publishing because deployment, status checks, history, rollback, and analytics share one HTTP interface. Stable project addresses simplify repeat releases, while structured project context helps agents resume work across sessions. The narrow framework list and operational constraints keep it from being a general hosting replacement.
What's good
Every deployment automatically increments its version and retains structured history. Rollback can restore an earlier successful release when its source archive exists. Build responses distinguish ready, building, and error states, with summaries and recent log lines for failures. The first unauthenticated deployment creates credentials, reducing setup for a new project.
Tradeoffs
The initial API key appears only once, so losing it creates an immediate credential-management problem. Next.js projects must use npm. Rollback depends on the target version having a stored source archive. The documented free tier limits uploads to 50 MB and allows 10 deployments per hour. Builds may require polling before the public site is ready.
How to use it well
Use it for agents or scripts that repeatedly publish small supported web projects and need stable URLs, deploy notes, status checks, analytics, and quick recovery. Save the first credential immediately, describe each release, poll non-ready builds, and verify the canonical public address before reporting success. Keep source control separately because this version history centers on deployments and stored archives.
Technical notes+
README.md documents the hosted REST API at https://api.host.neynar.app and the npx-installed MCP package @neynar/service.agent-deploy. SKILL.md and skill.md describe multipart deployment through POST /v1/deploy, Bearer authentication after initial credential creation, status polling, project context, source download, analytics, and rollback endpoints. They distinguish the canonical url or currentUrl from the immutable internalUrl. index.html is a small static landing page, CNAME maps the site hostname, and LICENSE contains the MIT terms.
Observed
- License
- MIT
- Interfaces
- Hosted REST API, MCP server, and agent skill file
- MCP packaging
- Available through npx as @neynar/service.agent-deploy
- Supported project types
- Static sites, Vite apps, Hono apps, and Next.js apps
- Authentication
- The first deployment can create an API key; later authenticated requests use a Bearer token
- Repository structure
- Documentation and skill definitions accompany a static HTML landing page and CNAME file
Read from README.md, CNAME, LICENSE, SKILL.md, skill.md, index.html.
What it can do
Deploy website from archive
Tar file containing website files → Deployed website with URL
Deploy website via API call
Single API request with deployment parameters → Website deployment confirmation and endpoint
Process automated deployments for AI agents
Deployment requests from AI agents → Live websites without human intervention
Upload and extract website files
Compressed tar archive → Extracted and hosted website files
Generate deployment endpoint
Website deployment request → Accessible web URL for deployed site
Tags
Media
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.