hanzo.ai/app/(marketing)/crawl/crawl-client.tsx

'use client'

import { Braces, Database, FileText, Globe, Monitor, Search, Shield, Zap } from 'lucide-react'
import { OSSRevenueBanner } from '@/components/oss/OSSRevenueBanner'
import { ProductFooter } from '@/components/products/ProductFooter'
import { ProductLanding } from '@/components/product/ProductLanding'
import type { ProductLandingProps } from '@/components/product/ProductLanding'

const docs = 'https://docs.hanzo.ai/docs/openapi/crawl/'

const crawl: ProductLandingProps = {
  badge: 'AI-Ready Web Crawler',
  badgeIcon: Globe,
  title: 'Hanzo Crawl',
  tagline: 'Give it a URL, get back Markdown',
  lede: 'It fetches the page, finds the part a person would actually read, and renders that as Markdown. Navigation, cookie banners and footers do not come with it. A page that needs JavaScript gets a real browser; everything else is a fetch and a parse, which is most of the web and far faster.',
  stats: {
    hero: true,
    items: [
      { value: 'JS', label: 'Full rendering' },
      { value: 'Parallel', label: 'High throughput' },
      { value: 'LLM', label: 'Structured extraction' },
      { value: 'MD', label: 'Clean Markdown' },
    ],
  },
  ctas: [
    { label: 'Read the docs', href: docs },
    { label: 'GitHub', href: 'https://github.com/hanzoai' },
  ],
  features: {
    title: 'Three steps, and a boundary',
    sub: 'Fetch, extract, render. Then the part that matters when the URL comes from a stranger.',
    items: [
      {
        icon: FileText,
        title: 'The readable part, not the page',
        body: 'Deciding which subtree is the article is the hard problem, and it is the one this solves. You get the content and what the page says about itself, without the chrome around it.',
      },
      {
        icon: Monitor,
        title: 'A browser only when needed',
        body: 'Most pages are a fetch and a parse. Headless Chromium is a separate service it escalates to for the ones that genuinely need rendering, so you do not pay browser cost for a documentation page.',
      },
      {
        icon: Braces,
        title: 'Markdown, and the metadata',
        body: 'Headings stay headings and links keep their targets, resolved against the page they came from. Title, description and canonical URL come back alongside — including the URL after redirects, which is the one worth citing.',
      },
      {
        icon: Zap,
        title: 'It cannot be pointed at your cluster',
        body: 'The caller supplies the URL, which makes any crawler a request-forgery primitive. Loopback, link-local and multicast are refused — including the cloud metadata endpoint on 169.254.169.254 that hands out credentials.',
      },
      {
        icon: Search,
        title: 'Every redirect is checked too',
        body: 'Blocking the first address is not enough, because a public URL can redirect to a private one. The guard sits on the dialer, so a 302 toward metadata is refused at the hop that matters.',
      },
      {
        icon: Shield,
        title: 'A tool an agent can call',
        body: 'It answers on MCP as well as over HTTP, so a model can read a page mid-conversation without you building the plumbing for it.',
      },
    ],
  },
  steps: {
    title: 'How it works',
    sub: 'Each step is its own file and can be tested without the other two.',
    items: [
      {
        n: 'Step 01',
        icon: Globe,
        title: 'Fetch',
        body: 'One guarded HTTP request. The dialer refuses private and link-local addresses on every hop, so a URL that redirects somewhere it should not reach is stopped there rather than after the fact.',
      },
      {
        n: 'Step 02',
        icon: FileText,
        title: 'Extract',
        body: 'The document is reduced to the subtree a reader would call the content, plus the title, description and canonical URL the page claims for itself. If the HTML alone is not enough, this is where a headless browser gets involved.',
      },
      {
        n: 'Step 03',
        icon: Database,
        title: 'Render',
        body: 'That subtree becomes Markdown with its structure intact — headings, lists, code and links, with relative URLs resolved against the page. It is the format a model reads best and a person can still diff.',
      },
    ],
  },
  chips: {
    title: 'Two ways to call it',
    sub: 'Over HTTP at /v1/crawl when your code is doing the asking, or over MCP when a model is.',
    items: ['Static Sites', 'SPAs', 'Documentation', 'E-Commerce', 'Forums', 'REST API'],
  },
  plans: {
    title: 'Pricing',
    sub: 'You are paying for the hosted API and the browsers behind it, not for the code.',
    footnote:
      'The crawler is open source, and so is the headless-browser image it escalates to. Run both yourself for nothing. The plans buy you somebody else operating them.',
    items: [
      {
        name: 'Build',
        price: '$49',
        period: 'mo',
        points: [
          '50,000 pages/month',
          '5 concurrent crawlers',
          'JavaScript rendering',
          'Markdown + structured output',
          'REST API access',
        ],
        cta: { label: 'Read the docs', href: docs },
      },
      {
        name: 'Scale',
        price: '$499',
        period: 'mo',
        pick: true,
        points: [
          '500,000 pages/month',
          '25 concurrent crawlers',
          'Priority JS rendering',
          'LLM-based extraction',
          'Direct Search + Vector integration',
        ],
        cta: { label: 'Read the docs', href: docs },
      },
      {
        name: 'Enterprise',
        price: 'Custom',
        points: [
          'Unlimited pages',
          'Unlimited concurrent crawlers',
          'Dedicated rendering pool',
          'Custom extraction schemas',
          'Dedicated support + SLA',
        ],
        cta: { label: 'Contact Sales', href: '/contact-sales' },
      },
    ],
  },
  finalCta: {
    eyebrow: 'Hanzo Crawl',
    title: 'Send it a URL',
    sub: (
      <>
        One call, and the page comes back as Markdown.
        <br />
        From your code over HTTP, or from a model over MCP.
      </>
    ),
    buttons: [
      { label: 'Read the docs', href: docs },
      { label: 'View on GitHub', href: 'https://github.com/hanzoai' },
    ],
  },
}

export default function CrawlClient() {
  return (
    <>
      <ProductLanding {...crawl}>
        <OSSRevenueBanner />
      </ProductLanding>
      <ProductFooter slug="crawl" name="Crawl" />
    </>
  )
}