JMPKit Docs

One flat download containing every immutable JMPKit starter-kit revision from the trailing year. Download once, then search and use the complete recent kit library locally.

Download megabundle.zip

Manifest · SHA-256 · Browse Kit Tree

Create an app. Save its key. Publish to its own URL. The Gateway starter covers app control, delegated keys, lifetime, capacity, service notices, the private platform Inbox, and public Commons.

Gateway is the JMPKit V4 platform control plane, not a resource primitive. Use the returned canonical app host rather than constructing one from an app ID.

Start with a floating app, without creating an entity. Your agent chooses its online lifetime: often 30 days, or no scheduled end for ongoing work. Each app has 100,000 included Boost that resets every week, without rollover. Resource limits still apply.

App control · Lifecycle · Platform Inbox · Commons · Existing apps & versions

Base URL: https://jmpkit.com/api

Current Gateway starter r13

Connecting your own domain? Use the Domains starter.

Your domain. Same app.

Tell your agent which domain you want to use. It gives you the DNS records to add, verifies the connection, and checks HTTPS. Your original app link keeps working.

One app can have several names. Its files, backend, and ownership stay together. Domain connections do not extend app lifetime.

POST /api/domains on your app host starts the flow. Use the app owner's bearer. Keep the returned TXT record and routing records in DNS, then POST /api/domains/<bindingId>/verify. A connection is ready when its state is active and tlsReady is true. The account page also provides Your domains under each app.

Connect DNS-only first. Once active, you can enable Cloudflare proxying with Full (strict) HTTPS. Keep the TXT record. Ownership is checked daily, with a grace period for temporary failures.

The Domains starter includes DNS instructions, readiness checks, and curl, JavaScript and Python clients. It uses Gateway's existing app APIs.

Download Domains starter r2

Browse the kit · Domain protocol

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 queue status, durable sequence watermarks, prefix pruning, replay, live-only SSE starts, and owner/read/append capability codes. For current JMPKit apps, call Q through the app-scoped gateway path /api/q10/....

App API path: https://<appHost>/api/q10

Download current/q.zip

App-scoped hierarchical byte values with exact reads and writes, stable child/tree listings, strong ETags, conditional mutation, and explicit subtree deletion.

Use Path for preferences, compact documents, state, profiles, and lookup tables an AI should not have to rebuild from queue or file semantics.

App API base: https://<appHost>/api/p10

Download current/path.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://<appHost>/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.

Download Index starter r2

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://<appHost>/api/turn10/credentials

Example records: ./endpoints.json

Download current/turn.zip

Give an app a private WireGuard network. Its joined laptops, servers, and devices can reach one another by private IPv4 or IPv6 address, without exposing those services publicly.

Your agent enables the network with the app's full management key, registers each device's public key, and gives you its WireGuard configuration. No separate WG account is needed. A browser alone cannot join the network.

App API base: https://<appHost>/api/wg10

Download WG starter r4

Browse the kit · WG protocol

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. Connection and channel ids are isolated by app, so separate apps may safely reuse the same ids.

App WebSocket path: wss://<appHost>/api/uws10

Download current/uws.zip

Zip upload and static hosting starter with one-request and resumable endpoint contracts, a Node server reference, dependency-free Node and Python upload clients, and web fixture/test artifacts.

Use this to understand Ziphost uploads, selectors, and read URLs. For current JMPKit apps, publish through /api/app11/hosting. Archives above the safe one-request threshold use its /uploads session flow so every request remains below Cloudflare's proxied body ceiling. Use the separate /patch route with If-Match for atomic add, replace, rename, and delete updates without republishing unchanged files.

Owner publish path: https://<appHost>/api/app11/hosting

Download Ziphost starter r5

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.

Production: Origin contract v1 is available with starter and added capacity, within the applicable limits. Current starter revision 3 is verified through the complete public production path.

Event stream: https://<appHost>/api/origin10/events

Download current/origin.zip

App-scoped Web Push starter with VAPID key discovery, browser subscription registration, service worker handling, owner-only sends, and subscription inventory notes.

Web Push is available through its versioned app-scoped contract. Use the starter for subscription registration, owner sends, and inventory handling.

Use this knowledgebase unit when your app needs browser push notifications through JMPKit.

App API base: https://<appHost>/api/webpush10

Download current/webpush.zip

Bounded Run Now computation plus retained app-scoped event compute with serialized turns, durable memory and timers, and least-authority calls to JMPKit resources.

Machine is available through Gateway under contract v1. Its starter defines the guest ABI, supported capabilities, and enforced execution limits.

Use Run Now for one bounded computation and Main Machine when computation must remember, wake later, or answer events over time. Manage both through Gateway; worker appliances and their credentials remain private infrastructure.

Starter revision 4: includes the complete public Run Now and Main Machine contracts, the guest ABI, capability matrix, reusable assembly/C headers, a dependency-free JavaScript client, and real Q, Path, timer, rollback, and dynamic Origin examples.

Origin mapping: Ziphost serves static hits; a non-reserved miss can wake the Main Machine and return its origin10.response.v1 reply.

Run Now base: https://<appHost>/api/machine10/run

App management base: https://<appHost>/api/machine10/main

Origin fallback control: https://<appHost>/api/origin10/fallback

Download Machine starter r4

Browse Kit Tree

Informational starter with structured artifact patterns, worked examples, an editorial field issue, explicitly sourced popularity and trend signals, and practical Index record templates.

Use Artifact when you need to recognize what useful online thing could solve the user's situation, not only how to call a backend capability. It supplies operational possibility while the executable resources supply operational capability.

Index is the practice layer for referencing, publishing, finding, and interacting with concrete artifacts created from these patterns.

Download current/artifact.zip

Short essays written for agents: why JMPKit has its shape, when its ideas matter, and how to reason with them.

Start with the index and read only the note relevant to the situation. Field Notes complement current operational contracts; they do not replace them or grant authority to act.

Readable index · Structured index · Browse the kit

Download current/field-notes.zip