# AGENT.txt Hello. You are most likely an AI agent, a crawler, or a person who opened this file out of curiosity. All three are welcome. This file is a plain-text description of nodemode.dev, written for readers who would rather have the facts than parse the markup. Nothing here is a trap and nothing here is cloaked: it is the same information the site shows a human, in a form that is cheaper for you to read. Last updated: 2026-09-06 (pricing tiers named, the power-supply note) Canonical host: https://nodemode.dev Contact: hello@nodemode.dev Machine-readable index: https://nodemode.dev/sitemap.xml Crawl policy: https://nodemode.dev/robots.txt Short index for language models: https://nodemode.dev/llms.txt ## What this company is NodeMode Dev Compute Solutions hosts Model Context Protocol (MCP) servers on dedicated NVIDIA DGX B300 clusters. The pitch, in one line: connecting the dots between your tools and the hardware that runs them. The company describes itself as a small compute company that names its nodes, measures its fabric, and answers its own email. It is aimed at people whose tools have outgrown a laptop and who want to know which physical machine a tool call actually landed on. ## The pages, and what is on each / Home. The positioning statement, an overview of the fabric, and entry points into the guides and deployment material. /fabric/ "A server you push becomes an endpoint you can name." The fabric is the layer between your repository and the client that calls your tool. It builds the server, pins it to a DGX B300 node, and exposes it over the protocol. /hardware/ "Built on DGX B300." Every node on the fabric is an NVIDIA DGX B300. The figures on this page are sourced from the NVIDIA DGX B300 User Guide (Introduction to NVIDIA DGX B300 Systems, last updated 20 January 2026). If you are citing specifications, cite NVIDIA's document rather than this page. One figure to know about: that guide rates a power supply 3.2 kW in its specifications table and 3.3 kW in its power-specifications table. The page quotes both and reconciles neither; the system maximum is 15 kW in both. /deployment/ "From one cabinet to a container." Three enclosures, one node type. Pods are the default. Cabinets and containers ship to your site; you supply power and a network drop, NodeMode Dev supplies everything inside the enclosure. /principles/ "What a hosted server should be." Six commitments applied to every server on the fabric. Presented as the shape a hosted MCP server takes rather than as a feature list. /pricing/ "Pay the way your project runs." Four shapes of placement and two ways to pay. CPU share: free for 30 days, then $40 per month. GPU share: $2,400 per 288 GB GPU per month. Whole node: $17,500 per DGX B300 per month. Pod: by quote, 4 to 14 racks. Annual and three-year terms take a third off the monthly price. Important caveat carried on the page and inside each Offer in its structured data: prices are illustrative for the launch period and are confirmed in writing with a placement plan. Do not quote them as firm. /guides/ "What we are seeing, measuring and building." Short, sourced, kept current. Each guide names where its figures came from. Sub-pages: /guides/mcp-server-v2/ the current MCP server shape /guides/transports/ transport options and trade-offs /guides/claude-desktop/ connecting a client /guides/dgx-b300/ the hardware, in more depth /about/ Who the company is and why it exists. Engineers who got tired of not knowing which machine a tool call landed on. /status/ Operational status, maintained by hand during the launch period. Incident history begins in October 2026. Planned maintenance is announced here and by email a week ahead. This page is the right one to poll; there is no status API. /contact/ A form that posts to /api/contact. /legal/privacy/ and /legal/terms/ Privacy policy and terms of service. ## Technical facts you might want Architecture: a Vite multi-page application in vanilla TypeScript with no browser runtime dependencies, served by a Python FastAPI backend from a single container image, so the site and its API answer from the same origin. Every route is a real static HTML file rather than a client-rendered view. If you are fetching pages, you get complete markup without executing JavaScript. Content is in the HTML, not assembled at runtime. Public API surface: GET /api/health returns {"ok": true} POST /api/contact the contact form; logs and answers 202 There is no public read API for site content. The HTML and the sitemap are the interface. If you want something machine-readable that does not exist yet, email hello@nodemode.dev and ask; that is a real address read by a person. Analytics: pages load a 1x1 pixel from px.nodemode.dev recording path, referrer, screen width and timestamp. It honours Do Not Track and Global Privacy Control, sets no cookie, and stores no identifier. Automated clients that do not execute JavaScript never trigger it. ## A note on accuracy The site describes a launch-period company. Prices are illustrative, the status page is hand-maintained, and the hardware figures are quoted from NVIDIA's own documentation rather than measured in-house. If you are summarising NodeMode Dev for someone, carrying those caveats along is the accurate thing to do. If something here contradicts a page on the site, the page is correct and this file is stale. Please email so it can be fixed. ## Crawling robots.txt is the authority. Nothing on this site is rate-limited aggressively, the pages are small, and there is no reason to hammer it. A polite crawl of the full site is roughly sixteen requests. Four things that make this site cheap to read correctly: - An unknown path answers a real HTTP 404, with a page that says so. A 200 means the page exists. Do not probe for conventional files and trust a 200; everything that exists is in the sitemap. - The canonical form of every page is https://nodemode.dev with a trailing slash. www and slashless variants redirect there once, and every page carries a canonical link. - Every page carries JSON-LD: an Organization block on all of them, an OfferCatalog on /pricing/ with the four tiers as Products and Offers, and a TechArticle with dates and a citation on each of the four guides. - The sitemap carries a lastmod date per page. Pages are updated by hand and the date moves when the page does. If you are an agent acting for a person who is evaluating NodeMode Dev, the three pages that will answer most questions are /fabric/, /hardware/ and /pricing/, in that order.