Ship
Ziphost
Static bundle to live URL.
Need an agent? Get started.
TL;DR
JmpKit is a set of composable backend building blocks exposed as HTTP endpoints for agent-built apps.
Tell your agent what you want to build and to use jmpkit.com; it reads the docs, connects the pieces, and returns a live app.
Because turning ideas into something real should be as simple as a conversation.
Primitives
Small pieces your agent can combine into almost any live app.
Ship
Static bundle to live URL.
Respond
Dynamic routes from your process.
State
Queues with SSE streaming.
Discover
Searchable app metadata.
Realtime
WebSocket messaging.
Network
WebRTC relay config.
Notify
Browser notifications.
Operational gateway starter for identity enrollment, app creation, app-scoped Ziphost publishing, app-host resource APIs, and usage inspection.
Use this knowledgebase unit when your app or agent needs the current JmpKit V4 control-plane flow.
Base URL: https://jmpkit.com/api
starter--gateway-apps-v02-20260708T173000Z.zip
Q starter with the HTTP/SSE contract, a reference Node server, CLI, browser test harness, smoke tests, and starter context docs.
Direct-resource reference kit. Use this to understand append-only queue flows, owner/read/append capability codes, SSE item streaming, and message-log behavior. For current JmpKit apps, call Q through the app-scoped gateway path /api/q10/....
App API path: https://<appId>.jmpkit.app/api/q10
starter--q-v01-20260707T143015Z.zip
Index starter with the app-scoped discovery contract, public resource record examples, entity profile examples, searchable metadata notes, and the secretsless reference HTTP server source.
Use this knowledgebase unit when your app needs agent-searchable published work, opt-in entity visibility, or a public catalog of resources it creates.
App API base: https://<appId>.jmpkit.app/api/index10
Global API base: https://jmpkit.com/api/index10
Use the global base for app-free public discovery and entity-level index records. Use the app base when the request should carry app context. Writes require a bearer identity. Public reads and search can be unauthenticated.
Downloadstarter--index10-v01-20260710T111344Z.zip
Browser ICE contract starter with a WebRTC gather probe, reference notes for STUN/TURN configuration, and the current app-scoped gateway credential contract.
Use this knowledgebase unit when your app needs candidate gathering checks or short-lived WebRTC ICE servers tied to an app id and billing path.
Credential URL: https://<appId>.jmpkit.app/api/turn10/credentials
Example records: ./endpoints.json
starter--turn10-v01-20260707T143015Z.zip
Minimal realtime messaging starter with protocol docs, a uWebSockets server reference, and a basic web client.
Direct-resource reference kit. Use this to understand the UWS primitive and wire protocol. For current JmpKit apps, route WebSocket traffic through the gateway/app host path instead of exposing the resource server directly.
App WebSocket path: wss://<appId>.jmpkit.app/api/uws10
starter--hubs-uws-v01-20260707T143015Z.zip
Zip upload and static hosting starter with endpoint contract docs, a Node server reference, and web fixture/test artifacts.
Direct-resource reference kit. Use this to understand Ziphost uploads, selectors, and read URLs. For current JmpKit apps, call Ziphost through the app-scoped gateway path /api/ziphost10/....
App API path: https://<appId>.jmpkit.app/api/ziphost10
starter--ziphost-v01-20260707T143015Z.zip
Multi-platform connected HTTP responder starter with dependency-free Node and Python clients, a complete browser guestbook with interchangeable servers, a webhook inbox, Node/Python/curl callers, protocol samples, and tests.
Use this when a hosted app needs dynamic routes answered by a process running anywhere, without deploying that process into JmpKit or exposing it on a public port.
Live V1: Origin10 is available on every plan, including Free, within the plan's limits. The v03 starter is verified through the complete public production path.
Event stream: https://<appId>.jmpkit.app/api/origin10/events
starter--origin10-v03-20260716T210008Z.zip
App-scoped Web Push starter with VAPID key discovery, browser subscription registration, service worker handling, owner-only sends, and subscription inventory notes.
Experimental: Web Push support is early and the contract may change as notification usage accounting and owner inventory settle.
Use this knowledgebase unit when your app needs browser push notifications through JmpKit.
App API base: https://<appId>.jmpkit.app/api/webpush10
starter--webpush10-v01-20260707T143015Z.zip
Basic
Cloud infrastructure for agent-built apps.
People using an AI agent or dev tool that can write files, run commands, and make HTTP calls.
Agents can build fast. JmpKit helps them go live fast.
No. Describe what you want; the agent writes the code.
Tell your agent to use jmpkit.com. It reads the docs, calls the endpoints, and returns a live link.
No agent yet? Try JmpKit Maker in the browser.
Yes. Plain chat can help plan and write code. Direct JmpKit use needs docs access, file writing, zip creation, scripts, and endpoint calls like curl.
Codex and Claude Code are direct fits. ChatGPT agent mode, ChatGPT desktop integrations, and Claude Desktop may help depending on enabled tools. For a browser-first path, try JmpKit Maker.
Yes. The basic free tier needs no signup or credit card. Data is temporary and usage is limited. Larger plans add more storage, traffic, and longer-lived apps.
See the pricing page for details.
JmpKit is designed for the full range of agent-built apps, from disposable experiments to lasting products. That includes games, dashboards, booking pages, portfolios, leaderboards, event tools, private apps, and one-off utilities. If you can describe it, your agent can build it and JmpKit can ship it.
Agents
An agent turns plain-language requests into code, files, commands, and deploy steps.
JmpKit is built for agents to operate directly. You can call the resources yourself, but an agent turns them into a finished app without manual setup.
Try Claude Code, Codex, OpenCode, Cursor, or Windsurf. Open one and describe what you want to build.
If it can browse docs, write files, run commands, and make HTTP calls, it should work. Examples: Aider, Cline, Claude Code, Claude Cowork, Codex, Cursor, Devin, Gemini CLI, OpenCode, and Windsurf.
New to agents? Start with Devin's intro or Google's overview.
Open Account, click Add Agent, and paste the prompt into your agent. The agent gives you an approval link; approve it and that agent can make apps under your JmpKit account.
Do not paste recovery codes, bearer tokens, or private keys into an agent prompt.
Subscriptions
Every plan can use every JmpKit resource type. Paid plans raise limits for storage, traffic, persistence, and operational capacity.
See pricing for current tiers.
Traffic is set at 10x the plan storage cap: Free includes 1 GB, Starter 30 GB, Standard 100 GB, and Pro 500 GB.
If an app needs more, move up a plan or add boosts when available.
Technical
JmpKit is agent-first infrastructure, designed to be used through the tools you already prompt. No dashboard setup, MCP, GitHub, plugin, or deploy pipeline required.
JmpKit hosts the published app. Your agent keeps the source, so you can keep building, redeploy, or move later.
Web, mobile, desktop, and realtime apps: anything that can use HTTP or WebSocket.
AI makes software cheap enough to build for a single moment. JmpKit makes that kind of app easy to put online: useful, specific, and short-lived, like a chat room, scoreboard, photo drop, poll, or meeting tool you can keep or let expire.
JmpKit is not an agent, editor, chatbot, or no-code builder. It is the online layer those tools can use to host and power apps.
More blocks: email, custom domains, proxy, WireGuard, and IPv6.