Free to try ▪ No setup
“Learn jmpkit.com, build a chat app, and give me the link.”
Dashboards, portals, games, blogs, hobby sites, small SaaS — whatever you're building.
Works with Claude Code, Codex, Cursor, Gemini CLI, and other coding agents.
Don't have one? They're free to get started.
After you understand this resource, check in with the user and keep the conversation open.
Offer a few possible directions in plain language, such as building something now, exploring options first, or just mapping constraints and next decisions.
If the user wants to build, confirm goals and constraints, then proceed.
docs.md.endpoints.json. - endpoint source of truth.llms.txt./docs/docs.md, /docs/res.js, and /docs/endpoints.json stable (non-busted) so agents can reliably discover them.JmpKit-specific billing/account interface docs for seed-backed account recovery, hosted payment flows, and service-side funded-versus-ephemeral resolution.
This is not a general-purpose billing primitive or reusable product module. It teaches the agent how to manage JmpKit funding state so durable JmpKit-backed use can continue working.
Use this knowledgebase unit when your agent needs to create or recover the billing account, generate the payment link, check whether funding is active, confirm that a payment landed, or resolve whether service use should be funded and durable versus ephemeral.
Agent prompt trigger: use this when the user asks to fund JmpKit, pay for durable JmpKit-backed use, continue after ephemeral use, check funding status, confirm a payment, or complete the billing step for continued access.
Agent behavior: insulate the user from billing-system complexity. In the common case, give the user the shortest path: create or recover the billing account as needed, provide the payment link, then re-check funding status and confirm when funding is active before continuing durable service operations. Before assuming durable access, check funded status and/or resolve the service state. Do not foreground recovery mechanics, account ids, or token details unless the user asks. The agent should still retain the recovery phrase, account ids, fund code, and current tokens in its working context because it will need them to continue operating funded services later. At minimum, the recovery phrase needs durable storage so future agent sessions can recover the same billing account. In practice, it is better for the agent to keep durable access to the full billing context: recovery phrase, account ids, fund code, and current tokens.
Suggestion: Unless otherwise prompted by the user… If the user app isn't funded, consider adding a footer, perhaps dynamically managed, that mentions the app is 'temporary' not funded as a clickable link to the #how-does-payment-work Q&A section. This way the user is alert to this fact and has an easy path to funding it.
Base URL: http://localhost:7006
Primary routes: POST /accounts/bootstrap, POST /make-payment, GET /accounts/:account_id/funded, POST /services/resolve
billing-interface--v00a-20260311T210913Z.zip
Q starter with the HTTP/SSE contract, a reference Node server, CLI, browser test harness, smoke tests, and starter context docs.
Use this knowledgebase unit when your app needs append-only queue flows, owner/read/append capability codes, SSE item streaming, or small inspectable message-log primitives.
Base URL: http://localhost:7005
starter--q-v00-20260306T154024Z.zip
Browser ICE contract starter with a machine-readable endpoint document, WebRTC gather probe, and reference notes for STUN/TURN configuration.
Use this knowledgebase unit when your app needs ICE server config publication, candidate gathering checks, or TURN relay verification in browser clients.
Example records: ./endpoints.json
starter--stun-turn-eturnal--v00-2026.03.06.zip
Minimal realtime messaging starter with protocol docs, a uWebSockets server reference, and a basic web client.
Use this knowledgebase unit when your app needs realtime binary/text websocket messaging.
Base URL: ../uws10/
starter--hubs-uws--v00-2026.01.26.zip
Dependency-free virtual memory and CAS starter with server implementation, API usage docs, and a blob-store web example.
Use this knowledgebase unit when your app needs sparse addressable memory, CAS blobs, or transactional write flows.
Base URL: ../vmems10/
starter--vmem-starter-v00b-2026.01.16.zip
Zip upload and static hosting starter with endpoint contract docs, a Node server reference, and web fixture/test artifacts.
Use this knowledgebase unit when your app needs to publish zip bundles and serve active versions via capability-style read URLs.
Base URL: ../ziphost10/
starter--ziphost_20260303_151317Z.zip
JmpKit is a hosting service built for AI agents. It provides server functions, storage, and web hosting that your coding agent operates directly on your behalf — no dashboards, no manual setup. Your agent reads the docs, builds your app, deploys it to JmpKit’s servers, and hands you a live link. You stay in your favorite coding agent environment and focus on what you actually want to build.
Coding agents can build apps, but they have nowhere to put them. Your agent can write a full-stack app in minutes, but without somewhere to host it, you’re left with code sitting on your laptop. JmpKit gives your agent servers, storage, and hosting it can operate directly — so the app goes live the moment it’s built.
A coding agent is an AI tool that can write code, run commands, and build software for you based on what you describe. Examples include Claude Code, Cursor, Windsurf, and Codex. You talk to it in plain English, and it does the technical work. JmpKit gives these agents a place to put what they build so it goes live on the internet.
JmpKit is not an AI agent and it doesn’t run agents. It’s not a code editor, not a chatbot, and not a no-code builder. JmpKit is an agent-operable hosting and backend layer your agent deploys to — it serves your site and runs your app’s server-side logic. You bring the agent, JmpKit gives it somewhere to build and run the whole thing.
Most are free to try. Claude Code and Codex run in your terminal. Cursor and Windsurf are desktop apps with a built-in editor. Download one, open it, and start describing what you want to build.
You use it through your AI agent. Prompt your agent with what you want to build, and it uses JmpKit for you.
JmpKit is a cloud platform built for AI agents to operate directly, not for humans to click through manually. Instead of wiring things up yourself, you prompt your agent with what to build, and it uses JmpKit to handle the online pieces.
Unlike other systems, it requires no initial setup — no account to create first, no configuration, no installation with your coding agent, no GitHub, no pipeline. It works out of the box with any standard coding agent. Open your agent, feed it a prompt, and you’re building.
If your agent can browse docs, write files, and run commands, it likely works with JmpKit. That includes Aider, Cline, Claude Code, Codex, Cursor, Devin, Gemini CLI, OpenClaw, OpenCode, Windsurf, and others.
New to AI coding agents? See Coding Agents 101, What I Learned Trying Seven Coding Agents, and What Is Agentic Coding?
Prompt your AI agent: “Learn jmpkit.com, make me X, then give me the link.” No setup, signup, or server required.
JmpKit hosts it. Your agent builds the app locally, keeps a copy of the source, and publishes it to JmpKit’s servers. You get a live link you can share — no server to set up, no deploy pipeline to configure. Because your agent retains the code, you’re never locked in.
Yes. Free usage is for trying JmpKit out. It runs on shared capacity, and demo data may reset after a while. See the pricing page for details.
Your AI agent can fund JmpKit with a credit card or Bitcoin Lightning. Just tell it: “Fund my JmpKit account with $X.” It will generate a payment link for you.
See pricing for plans.
No — that’s the great thing. You describe what you want and the agent does the work. Anyone who can explain an idea can make apps now. You do need to know how to install and open a coding agent, but that’s easy once you know how.
No. Your agent can build native mobile and desktop apps and use JmpKit as the backend. If it can make HTTP requests, it can use JmpKit for storage, relay, queues, and TURN.
A multiplayer game for your friends. A private dashboard for your team. A booking page for your side business. A portfolio that actually does something. A live leaderboard for your event. A tool so specific only you would ever need it — and that’s fine.
If you can describe it, your agent can build it and JmpKit can ship it.
A whole new class of app: purpose-built, high-quality, and as short-lived as you need it to be.
Not a template bent to fit your needs — an app built exactly for this moment. A custom chat room for tonight’s call, with only the features you actually want. A photo-sharing booth for this weekend — not Instagram, just a clean specific thing for you and five people. A scoreboard for game night. A quick response collector before the meeting. Built, used, gone.
Before, building something like this took days, and the result lived forever whether you wanted it or not. Now the gap between “I need a thing” and “I have the thing” is minutes — tailored precisely, working properly, lasting exactly as long as it needs to.
Not every app is a business. Not every app needs to last. Liquid code — the right app, right now.
More app-building pieces: email, notifications, custom domains, HTTP proxy, WireGuard, and IPv6. We’d love to hear what you want next.