> For the complete documentation index, see [llms.txt](https://docs.taptap3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taptap3d.com/get-started/readme.md).

# Introduction

Taptap3D developer documentation for inventory records, catalogue production and planned ecommerce embeds.

Taptap3D turns inventory records and photographs into catalogues. Its next publication surface is an online listing that a business can embed in an existing website.

The product starts with auction houses, where one record describes a physical object, its images and the information needed to publish it. The catalogue workflow is implemented. Public listing APIs, iframe embeds and ecommerce integrations are not available yet.

These docs explain the current record model and the proposed publication boundary. They are for developers planning an integration, not a reference for a released SDK.

## The data flow

```
Spreadsheet + photographs
         |
         v
Inventory record -- editorial corrections
         |
         +--> Catalogue layout --> PDF
         |
         +--> Approved public listing --> Website embed   [planned]
```

A correction belongs to the record or its presentation settings. Changing a catalogue layout should not discard it. An online listing should reuse that work rather than require a second product description.

## Start here

* [Capabilities](/get-started/capabilities.md): what exists and what is planned.
* [Records and outputs](/concepts/records-and-outputs.md): the domain model.
* [Choose an integration](/get-started/embedding.md): hosted iframe or custom data rendering.
* [Local quickstart](/get-started/local-quickstart.md): run a synthetic listing and check the expected result.
* [Connection playbook](/get-started/connection-playbook.md): the client onboarding sequence.
* [Search visibility](/integration-guides/search-visibility.md): how host pages should expose listing content to search engines and answer systems.

## Reading paths

For a storefront developer: choose a surface, run the local quickstart, then follow the matching integration guide. Keep the [listing contract](/proposed-reference/listing-contract.md) available as a reference.

For an integration lead: review [publication boundaries](/concepts/publication-boundaries.md), [access and environments](/proposed-reference/access-and-environments.md) and the [release acceptance checks](/testing-and-support/acceptance.md) before agreeing a live connection.

Taptap3D is developed by Binox Limited. Product status reviewed on 8 October 2026.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.taptap3d.com/get-started/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.