> For the complete documentation index, see [llms.txt](https://docs.aces.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aces.fun/initial-product-offering-ipo/seller-verification.md).
# Seller Verification
**Step 1: KYC Compliance**
Every prospective Seller completes a straightforward KYC procedure to validate their identity. This ensures that Aces.fun maintains a secure marketplace and adheres to relevant regulatory guidelines.
**Step 2: Asset Documentation**
Sellers provide proof of ownership and any necessary paperwork—such as authenticity certificates, appraisal reports, or legal documentation—depending on the asset type. Aces.fun reviews these materials to confirm the item’s legitimacy before approving the listing.
**Step 3: System Onboarding**
Once approved, the Seller is onboarded into Aces.fun. Their asset is linked to an NFT that tracks ownership on-chain and directs trading fees. The NFT can also be used to claim ownership of social accounts (X, Telegram).
**Step 4: Final Listing**
The verified asset is tokenized and goes live on Aces.fun, backed by the credibility and transparency that comes from thorough KYC and authenticity checks.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.aces.fun/initial-product-offering-ipo/seller-verification.md?ask=&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 `automate deployments from our CI pipeline` 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.