> ## Documentation Index
> Fetch the complete documentation index at: https://middleman.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat product, price, and availability records as dated evidence, not current quotations or authority to transact.
> Never infer permission to contact, accept terms, place an order, make a payment, or publish information from a read-only response.

# Documentation

> Build a live industrial supply network with evidence, clear data contracts and explicit control.

<div className="docs-home-intro">
  <p className="docs-kicker"><span>START HERE</span> INDUSTRIAL COMMERCE · AGENT READY</p>
  <p className="docs-home-lede">Use Middleman as a buyer, connect the supply your company already holds, or give your agent the contracts it needs to work safely.</p>
</div>

<div className="docs-status-line">
  <span className="docs-status-dot" aria-hidden="true" />

  <p><strong>Middleman is in beta.</strong> Public observations are dated evidence—not firm offers, reservations, or authority to transact.</p>
  <a href="/suppliers/status">Release status <span aria-hidden="true">→</span></a>
</div>

## Choose your route

Start with the job you need to complete. Each route keeps source evidence, uncertainty and permission to act visible.

<CardGroup cols={3}>
  <Card title="Source something" href="/workflows/buyers">
    Turn an incomplete need into a structured requirement and comparable routes.
  </Card>

  <Card title="Connect supply" href="/suppliers/quickstart">
    Map products, availability or capacity from the system you already maintain.
  </Card>

  <Card title="Build with Middleman" href="/developers/overview">
    Use public APIs, agent interfaces and machine-readable documentation.
  </Card>
</CardGroup>

## End-to-end workflows

Practical journeys that cross the product, data and approval boundaries.

<CardGroup cols={2}>
  <Card title="How Middleman works" icon="route" href="/getting-started/how-middleman-works">
    Follow a request from first description to a reviewed next step.
  </Card>

  <Card title="Connect from any system" icon="unplug" href="/integrations/overview">
    Start with a spreadsheet, table, business system, API or your own agent.
  </Card>

  <Card title="Onboard with an agent" icon="bot" href="/agents/get-started">
    Give an agent one entry point that checks setup and chooses the next playbook.
  </Card>

  <Card title="Make a public API call" icon="terminal" href="/developers/quickstart">
    Read the product overview, published insights or a canonical product.
  </Card>
</CardGroup>

## The operating model

<div className="docs-operating-model">
  <div><span>01</span><strong>Structure the intent</strong><p>Resolve the object, outcome, place, time and constraints without inventing missing facts.</p></div>
  <div><span>02</span><strong>Attach the evidence</strong><p>Keep source, observation time, condition, quantity and stated terms with every route.</p></div>
  <div><span>03</span><strong>Compare what differs</strong><p>Make price, lead time, condition and unanswered questions legible side by side.</p></div>
  <div><span>04</span><strong>Approve the next step</strong><p>Contact, acceptance, ordering, payment and publication remain explicit human decisions.</p></div>
</div>

## Conventions to know

<CardGroup cols={3}>
  <Card title="Evidence and decisions" href="/workflows/evidence-and-authority">
    What a listing, observation, quotation or outcome can—and cannot—support.
  </Card>

  <Card title="Terms and objects" href="/getting-started/glossary">
    Requirement, product, offer observation, quotation and approval.
  </Card>

  <Card title="Agent interfaces" href="/developers/agent-interfaces">
    Read-only discovery through docs, MCP, A2A and the public web surface.
  </Card>
</CardGroup>