Developer & AI Agent Submission Guide

How to Submit to Build with Us

Everything you need to publish your product to the Next Level Builders directory — manually via Web Studio, from CLI pipelines, or autonomously with AI Agents.

5 Ways to Build and Submit Your Product

1. Manual Web Builder (Zero Code)

Beginner Friendly
Open Builder Studio

Use our interactive visual builder to construct block documents, live preview, and submit directly from your browser.

Step-by-step Execution:
  • Visit the Builder Studio at /studio
  • Fill in product identity (Slug, Title, Tagline, Website URL, Logo)
  • Configure Hero, Media Gallery, Features Grid, and Tech Stack blocks; add Analytics to share public traffic totals
  • Click 'Save Draft & Revision' to generate a verified content hash
  • Review your live preview at /studio/products/[slug]/preview and click Submit

2. Developer CLI Package (@nextlevelbuilder/cli)

Automated & CI/CD
View NPM Package

Validate local JSON listings, compute canonical cryptographic content hashes, and publish directly from your terminal or deployment pipeline.

Step-by-step Execution:
  • Install CLI: npm install -g @nextlevelbuilder/cli
  • Validate listing: nlb validate ./nlb.product.json
  • Preview document: nlb preview ./nlb.product.json
  • Submit to directory: nlb submit ./nlb.product.json --api-key YOUR_API_KEY
  • Check status: nlb status <slug>
  • Query your product traffic: nlb traffic <slug> --json (set NLB_API_KEY first)

3. Model Context Protocol Server (MCP)

AI Native (Cursor / Claude / Codex)
Explore MCP Server

Connect our official MCP server to your AI IDE or agent runtime so AI tools can draft, format, and submit products autonomously.

Step-by-step Execution:
  • Add an HTTP MCP server with URL https://mcp.nextlevelbuilder.io/mcp
  • Tools include list_templates, validate_listing, submit_product, get_product, get_product_markdown and get_product_traffic
  • Prompt your AI: 'Draft a full 5-block product document for my repo and submit it to Next Level Builders directory'
  • Remote mutations require the MCP operator-provided authorization token; REST API keys are separate. Keep secrets in your client configuration.
  • For traffic, call get_product_traffic with slug and optional from/to UTC timestamps

4. WebMCP — Design with AI in Studio

Live Draft Editing
Design in Studio

Connect your MCP client to the open Studio tab using WebMCP from webmcp.dev. AI can inspect the draft, discover templates, replace validated content and open a live preview.

Step-by-step Execution:
  • Configure your MCP client with: npx -y @jason.today/webmcp@0.1.13 --mcp
  • Open /studio, enable WebMCP and ask your client to create a WebMCP token
  • Paste the token into the connection widget in Studio
  • Ask AI to design your page using the draft tools and actual product information
  • Review the preview, then save or submit manually. AI draft tools do not publish or pay.

5. Direct REST API Endpoints

Full Programmatic Control
Open Interactive Scalar API Docs

Integrate directly with our high-throughput OpenAPI 3.1 endpoints on Cloudflare Edge.

Step-by-step Execution:
  • POST /api/v1/products — Create product draft envelope
  • POST /api/v1/products/{slug}/revisions — Upload block document
  • POST /api/v1/products/{slug}/submit — Submit into moderation queue
  • GET /api/v1/products/{slug}/markdown — LLM-optimized structured feed
  • GET /api/v1/products/{slug}/traffic — Organization-authorized traffic totals and breakdowns

Agent connections and readable content

HTTP MCP endpoint: https://mcp.nextlevelbuilder.io/mcp

{
  "mcpServers": {
    "nextlevelbuilder": {
      "url": "https://mcp.nextlevelbuilder.io/mcp"
    }
  }
}

Client configuration formats differ. Select HTTP transport and use the endpoint above. Read tools are public; remote writes require the operator-provided MCP token in the Authorization header. Your nlb_live_ API key authenticates REST requests and does not replace that token.

WebMCP connection setup:

{
  "mcpServers": {
    "webmcp": {
      "command": "npx",
      "args": [
        "-y",
        "@jason.today/webmcp@0.1.13",
        "--mcp"
      ]
    }
  }
}

Enable the connection only for a client you trust: it can read and change the draft in this tab. Disconnect when finished. Setup details: WebMCP.

Append .md to a page URL to read its Markdown representation, including localized pages. Examples: /build-with-us.md, /en/build-with-us/instructions.md and /api-docs.md. Private pages still require your session; unknown pages remain 404.

Activities and Pulse

Activities contain your dated updates and display the most recent first. Pulse measures the approved product website when visitors view the block, at most once every five minutes. It keeps the latest 100 samples; after 15 minutes without a measurement, the status is stale. Sample uptime is the success rate of measured checks, not a guarantee of continuous availability.

[
  {
    "id": "recent-activities",
    "type": "activities",
    "props": {
      "title": "Recent activity",
      "entries": []
    }
  },
  {
    "id": "website-pulse",
    "type": "pulse",
    "props": {
      "title": "Website pulse",
      "showHistory": true
    }
  }
]

Use GET /api/v1/products/{slug}/pulse to read saved history. POST to the same endpoint with an empty body requests a new check subject to the cooldown. The endpoint takes its URL from the published product; callers cannot supply another target.

19 Supported Content Block Types

Every listing is represented as an immutable, validated JSON document containing any combination of these 19 blocks.

Activities

activities

Dated product updates, newest first. Add releases, progress notes and links; an empty feed remains empty.

Pulse

pulse

Heartbeat-style website health monitor with saved status history, response time, sampled uptime and stale-data indicators.

Hero Block

hero

Top headline, punchy subheadline, CTA button, and urgency badge.

Media Gallery Block

mediaGallery

Responsive 16:9 screenshot and video showcase with captions.

Grid Block

grid

1, 2, or 3 column cards for key capabilities, architecture, and benefits.

Tech Stack Block

techStack

Badges highlighting TypeScript, Next.js, Cloudflare, PostgreSQL, AI models.

Pricing Block

pricing

Tiers, billing cycles, feature checklists, and checkout links.

FAQ Block

faq

Accordion questions and answers for technical and business queries.

Live Demo Embed Block

liveDemo

Embedded iframe sandbox or interactive playground URL.

Call To Action Block

cta

High-contrast conversion banner with primary action button.

Founder Story Block

founder

Founder avatar, bio, Twitter/Discord links, and personal mission statement.

Milestones Block

milestones

Historical chronological timeline of major product achievements.

Roadmap Block

roadmap

Upcoming quarterly releases with status (planned, in_progress, shipped).

Changelog Block

changelog

Versioned release notes with semver tags and date stamps.

Quote / Testimonial Block

quote

Social proof quotes from verified community members.

Verification Claims Block

verification

Cryptographic proof, open-source repos, and revenue verification.

Case Study Block

caseStudy

In-depth customer implementation story with measurable ROI metrics.

Showcase Carousel Block

carousel

Interactive carousel slider for product gallery snapshots.

Analytics Block

analytics

Public NLB product-page views, daily sessions, website clicks, and active visitors. Choose a title and 7, 30, or 90 days.

Measure Your Product Page Traffic

Analytics measures your published page on Next Level Builders and its website clicks. Daily sessions count each browser session once per UTC day, so returning on another day counts again. Studio preview visits are not counted.

Share aggregate traffic with an Analytics block

Choose Analytics in Studio, or include this block in your product document through REST, CLI, or MCP. Set a title and a reporting period of 7d, 30d, or 90d. Publishing the block makes aggregate totals and the daily series public; referrers, countries, and device breakdowns stay private.

{
  "id": "product-traffic",
  "type": "analytics",
  "props": {
    "title": "Traffic",
    "period": "30d"
  }
}

Once the Analytics block is published, the public summary is available at:

GET /api/v1/products/{slug}/traffic/public?period=30d

Query detailed traffic with your API key

Use an API key belonging to a member of the product organization; administrators also have access. Create your key in Profile. Queries default to the last 30 days and accept from/to UTC ISO timestamps spanning at most 90 days. The response includes totals, daily series, referrers, countries, devices, and active visitors.

REST

GET /api/v1/products/{slug}/traffic?from=2026-09-01T00:00:00Z&to=2026-09-08T00:00:00Z
Authorization: Bearer YOUR_API_KEY

CLI

Set NLB_API_KEY in your environment, then run:

nlb traffic my-product --from 2026-09-01T00:00:00Z --to 2026-09-08T00:00:00Z --json

MCP

With NLB_API_KEY configured for your MCP server, call get_product_traffic:

{
  "slug": "my-product",
  "from": "2026-09-01T00:00:00Z",
  "to": "2026-09-08T00:00:00Z"
}
Explore Traffic API

Ready to Launch Your Product?

Join the high-trust builder network. Get verified, track transparent votes, and gain organic distribution across our developer community.

Launch in StudioRead API Docs