> 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/capabilities.md).

# Capabilities

Current Taptap3D functionality and the status of public APIs, embeds and ecommerce integrations.

This table distinguishes implemented application features from proposed integration features. An implemented feature is not necessarily a public developer API.

| Capability                                  | Status       | Developer implication                                                   |
| ------------------------------------------- | ------------ | ----------------------------------------------------------------------- |
| CSV, TSV and XLSX ingestion                 | Implemented  | Users review field mappings before records are committed.               |
| Inventory records and photographs           | Implemented  | Records and image assets have stable identities.                        |
| Catalogue layouts and editorial corrections | Implemented  | Corrections survive layout regeneration.                                |
| Catalogue PDF output                        | Implemented  | The catalogue workflow produces a print document.                       |
| Organisation membership and selection       | Implemented  | Application requests are scoped to the acting organisation.             |
| Field visibility policies                   | Implemented  | Output audiences govern which fields may appear.                        |
| Public listing projection                   | Planned      | A proposed contract is documented; no production endpoint is available. |
| Per-item iframe embed                       | Planned      | No production embed URL is available.                                   |
| Online catalogue publication                | Planned      | Requires collection-level navigation and publication controls.          |
| Ecommerce channel adapters                  | Planned      | No Shopline, Boutir or SleekFlow connector is released.                 |
| Public SDK, API keys or webhooks            | Not released | Do not integrate against internal application routes.                   |

GCP deployment preparation is underway. It is not a claim that a production GCP service or a developer sandbox is available.

Bidding, checkout, payments and settlement are outside the current product scope. A future integration may hand a visitor to an existing commerce system; Taptap3D does not currently process the transaction.

Status reviewed on 8 October 2026. See the [roadmap](/project/roadmap.md) for sequencing.


---

# 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/capabilities.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.