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

# Developer Center

> How the Vantr API-host developer experience is organized across docs, portal, OpenAPI, sandbox, and AI discovery surfaces.

# Developer Center

The Vantr Developer Center lives on `api.vantr.ai`. It is the first-class home for external builders who only need the public API, while `app.vantr.ai` remains the business web application and `vantr.ai` remains the marketing site.

<Info>
  Treat the Developer Center as product UI. A developer should be able to sign in, create credentials, read docs, test safely, generate clients, and inspect usage without needing the business app navigation.
</Info>

## Host model

| Surface          | Host                   | Purpose                                                                                             |
| ---------------- | ---------------------- | --------------------------------------------------------------------------------------------------- |
| Marketing        | `https://vantr.ai`     | Product positioning, pricing, sales, and public marketing pages.                                    |
| Web app          | `https://app.vantr.ai` | Business operations for stores, finance teams, inventory, purchasing, and operators.                |
| Developer Center | `https://api.vantr.ai` | Public API docs, OAuth apps, OpenAPI, SDK starters, usage, webhooks, sandbox, and agent-ready docs. |

## Developer Center map

<Columns cols={2}>
  <Card title="Portal" icon="layout-dashboard" href="https://api.vantr.ai/developer">
    Authenticated workspace for OAuth applications, client secrets, redirect URIs, scopes, request activity, and webhooks.
  </Card>

  <Card title="Docs" icon="book-open" href="/quickstart">
    Human-readable guides for quickstart, authentication, conventions, errors, scopes, catalog workflows, and operations.
  </Card>

  <Card title="Reference" icon="braces" href="/api-reference">
    Generated endpoint reference from the public v2 OpenAPI source of truth.
  </Card>

  <Card title="OpenAPI" icon="file-json" href="/openapi/v2.json">
    Machine-readable contract for typed clients, API explorers, MCP tools, and integration tests.
  </Card>

  <Card title="AI tools" icon="bot" href="/guides/ai-tools">
    `llms.txt`, `skill.md`, MCP search, and agent instructions that point tools at the same supported contract.
  </Card>

  <Card title="Sandbox" icon="flask-conical">
    Dedicated safe account path for testing lifecycle-sensitive writes before production access.
  </Card>
</Columns>

## Public API lanes

Organize the API around jobs developers perform:

* Products and variations: create, update, archive, and organize sellable catalog records.
* Categories and tags: manage category trees, subcategories, and tenant-defined tags such as Organic or SNAP/EBT.
* Bills: ingest and retrieve bill data with constrained CRUD rules that protect accounting state.
* Draft orders: create and modify draft-state orders; paid orders cannot be deleted through the API.
* Payments: append-only payment creation tied to an order; created payments are one-and-done.
* Webhooks and usage: inspect request history, usage, and event delivery without leaving the API host.

## Experience principles

<Steps>
  <Step title="Start with a working path">
    The first viewport should route developers to quickstart, reference, OAuth applications, sandbox, and OpenAPI without marketing detours.
  </Step>

  <Step title="Keep docs and console connected">
    Endpoint pages should link back to the portal for the matching scopes, credentials, request history, and sandbox state.
  </Step>

  <Step title="Use OpenAPI as the source of truth">
    Reference pages, SDK starters, MCP tooling, Postman collections, and contract tests should all flow from the public v2 spec.
  </Step>

  <Step title="Document lifecycle rules directly">
    Bills, orders, and payments need explicit write limits, immutable states, idempotency guidance, and examples for failed state transitions.
  </Step>

  <Step title="Make AI support first class">
    Keep `/openapi/v2.json`, `/llms.txt`, `/llms-full.txt`, `/skill.md`, and `/mcp` easy to discover so agents use supported public surfaces.
  </Step>
</Steps>

## Provider stance

Mintlify can continue to serve as the bridge for current docs and generated reference pages. The long-term product decision is different: Vantr owns the Developer Center experience, and docs tooling supports that experience rather than defining it.