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

# Questions

Answers to developer questions about Taptap3D APIs, ecommerce embeds, catalogue data and access.

## What is Taptap3D?

Taptap3D is inventory-to-catalogue software developed by Binox Limited. It starts with auction houses and is being extended toward public listings that reuse the same approved records and images.

## Can I embed a Taptap3D item on my website today?

No production embed is available. The [connection playbook](/get-started/connection-playbook.md) gives proposed syntax, code examples and a local mock for planning. These are not a released integration contract.

## Is there a public REST API or JavaScript SDK?

No public API or SDK has been released. The application's internal routes are not a supported integration contract.

## Does Taptap3D process ecommerce payments?

No. Bidding, checkout, payments and settlement are outside the current scope. Planned integrations will connect approved listing content to existing websites or commerce systems.

## Can a private catalogue field appear in an embed?

The planned embed must use a reviewed public listing, not the raw record. The current engine has audience-based field policies, but a publication service and approval flow still need implementing. See [Publication boundaries](/concepts/publication-boundaries.md).

## Are Shopline, Boutir or SleekFlow supported?

No released adapters exist. Adapters are planned after the listing projection and a partner integration are established.

## Which languages are in scope?

The product is built for English and Traditional Chinese records. The embed's language negotiation and localisation contract have not been released.

## How do I discuss an integration?

Email <enquiry@binox.com.hk> with your website platform, the content you need to display and whether a hosted iframe or data integration suits your application.


---

# 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/project/questions.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.
