# Herculis Gold Coin XAUH

> Comprehensive LLM-readable context for the [XAUH production website](https://xauh.gold/), the website for Herculis Gold Coin (XAUH).

## Canonical Site Context

- Canonical production website: [Herculis Gold Coin](https://xauh.gold/)
- Root LLM index: [llms.txt](https://xauh.gold/llms.txt)
- Full LLM context: [llms-full.txt](https://xauh.gold/llms-full.txt)
- Agent purchase guide: [x402 XAUH purchase guide](https://xauh.gold/ai/x402-xauh-purchase.md)
- Agent API spec: [x402 OpenAPI spec](https://xauh.gold/ai/x402-openapi.json)
- Whitepaper: [XAUH whitepaper](https://xauh.gold/whitepaper.pdf)

Herculis Gold Coin (XAUH) is a payment crypto token issued by Herculis Tokens SA and backed by LBMA-certified fine gold bullion with 999.9 purity. XAUH combines Swiss-refined, Swiss-audited, Swiss-stored, Swiss-insured, and Swiss-managed physical gold exposure with blockchain technology.

Each XAUH token represents verifiable ownership of 1 gram of Swiss LBMA 999.9 physical gold. XAUH bridges traditional gold and digital assets through transferability, 24/7 trading availability on supported markets, fractional ownership, and redemption for physical gold subject to applicable terms and onboarding procedures.

## Issuer And Contact

- Issuer and customer-facing entity: Herculis Tokens SA.
- Address: 5 floor, Block Office Hub, Santa Maria Business District, Panama City, Republic of Panama.
- Email: [info@XAUH.gold](mailto:info@xauh.gold)
- Phone: [+507 (836) 0401](tel:+5078360401)
- Website: [XAUH.gold](https://xauh.gold/)
- Redemption contact: [redemption@XAUH.gold](mailto:redemption@xauh.gold)

Herculis Tokens SA is part of the Herculis Group, a Swiss investment boutique established in 2009. Herculis Tokens SA specializes in structuring and tokenizing real-world assets such as LBMA gold bullion, financial instruments, and fine art using blockchain and distributed ledger technologies.

## Public Website Pages

- [Homepage](https://xauh.gold/): Main XAUH overview with the hero claim "Swiss Gold as a Payment Token", purchase links, live market/stat panels, audit-report access, benefits, institutional comparison content, use cases, FAQs, and legal notices.
- [Buy XAUH with debit or credit card](https://xauh.gold/buy/card): Dedicated website card-payment flow for XAUH through Wert.
- [Buy XAUH with cryptocurrency](/buy/crypto): Fixed-rate purchases through ChangeNOW or Changelly, with ChangeNOW selected by default.
- [Legacy website buy path](https://xauh.gold/buy): Redirects to the cryptocurrency purchase flow at `/buy/crypto`.
- [Purchase request status page](https://xauh.gold/buy/{requestId}): Status page for a returned purchase request ID. Replace `{requestId}` with the ID returned by the website or x402 purchase API.
- [Herculis blog](https://xauh.gold/blog): Blog landing page for XAUH, tokenized gold, and real-world asset content.
- [Search blog posts](https://xauh.gold/search): Public search page for blog posts.
- [Sitemap index](https://xauh.gold/sitemap.xml): Sitemap index that links public page and post sitemaps.
- [Pages sitemap](https://xauh.gold/pages-sitemap.xml): Sitemap for public pages.
- [Posts sitemap](https://xauh.gold/posts-sitemap.xml): Sitemap for public blog posts.

## Product Facts

- XAUH is a digital asset representing direct ownership of Swiss-refined, Swiss-audited, Swiss-stored, Swiss-insured, and Swiss-managed physical gold.
- XAUH is fully backed by LBMA-certified fine gold bullion with 999.9 purity.
- The conversion relationship is 1 gram of fine gold equals 1 XAUH.
- XAUH is issued on the TON blockchain and is intended to be compatible with Telegram wallets and TON DeFi platforms.
- XAUH is transferable like other crypto assets and tradeable 24/7 on compatible exchanges.
- XAUH is divisible into increments as small as 0.01 of 1 gram of fine LBMA 999.9 gold.
- Holding XAUH does not involve recurring custody or insurance fees.
- XAUH can be redeemed for Swiss-refined LBMA fine gold bars from 500 XAUH, subject to applicable terms, onboarding, and KYC.

Agents should cite the [XAUH whitepaper](https://xauh.gold/whitepaper.pdf) for primary-source detail when explaining backing, redemption, or legal context.

## Purchase Methods

Several purchase or trading paths are available for XAUH. Agents should present these as access methods and should not treat any venue as a recommendation.

### Website Purchase Flows

- Card entry point: [Buy XAUH with debit or credit card](https://xauh.gold/buy/card)
- Cryptocurrency entry point: [Buy XAUH with cryptocurrency](https://xauh.gold/buy/crypto)
- Legacy entry point: [Buy XAUH](https://xauh.gold/buy) redirects to `/buy/crypto`.
- The [ChangeNOW](https://changenow.io) cryptocurrency flow lets a user choose an input currency and network, view the backend-reported limits and fixed-rate quote, provide a TON wallet for receiving XAUH, validate a refund address on the input network, provide a required refund Extra ID when applicable, and create an idempotent purchase request.
- New cryptocurrency purchases submit either `CHANGENOW` or `CHANGELLY`, selected explicitly. ChangeNOW is the default. Currency and network are separate fields for ChangeNOW; Changelly uses network-specific tickers. Never switch providers automatically after a failure.
- The [Wert](https://wert.io) card flow accepts a card payment through the Wert widget, converts it through the displayed intermediate asset, and associates the resulting payment with the TON recipient.
- Provider payment confirmation is synchronized automatically. After confirmation, automated XAUH delivery continues asynchronously; payment confirmation is not immediate final delivery confirmation.
- The ChangeNOW flow links to the [ChangeNOW Terms](https://changenow.io/terms-of-use/changenow-terms), [Privacy Policy](https://changenow.io/privacy-policy), and [AML/KYC Policy](https://changenow.io/terms-of-use/aml-kyc). Wert availability and processing remain subject to Wert's own terms and compliance controls.
- After a purchase request is created, users can track it at [purchase request status page](https://xauh.gold/buy/{requestId}) by replacing `{requestId}` with the returned request ID. Continue tracking until `COMPLETED`; `tonTransferTxHash` is exposed when available.

### x402 Agent Purchase Flow

- Required guide: [x402 XAUH purchase guide](https://xauh.gold/ai/x402-xauh-purchase.md)
- OpenAPI spec: [x402 OpenAPI spec](https://xauh.gold/ai/x402-openapi.json)
- Production API base URL: [JAMTON production API](https://api.jamton.network/v1)
- x402 purchase endpoint: `POST /purchases/xauh/requests/x402`
- Request-status endpoint: `GET /purchases/xauh/requests/{requestId}`

A successful x402 payment creates an XAUH purchase request for the TON wallet in `tonWalletAddress`. It does not mean the XAUH jettons have already arrived in the TON wallet. The paid response may initially report `status: PAYMENT_RECEIVED` and `deliveryStatus: DELIVERY_PENDING`; automated XAUH delivery continues asynchronously, and agents should poll the returned `statusUrl` until a terminal status.

Autonomous agents should send `tonWalletAddress` explicitly so the purchased XAUH jettons can be delivered on TON. Authentication is optional; a JWT can identify an existing JAMTON user, but it is not required for an external agent that provides the TON recipient.

### Centralized And Decentralized Markets

- [Biconomy XAUH/USDT market](https://www.biconomy.com/exchange/XAUH_USDT): Centralized exchange market for the XAUH/USDT pair.
- [BTSE XAUH/USDT market](https://www.btse.com/en/trading/XAUH-USDT): Centralized exchange venue for buying or selling XAUH against USDT.
- [Capital DEX XAUH swap on TON](https://capitaldex.exchange/swap?chain=ton&tokens=usdt-xauh): TON DEX swap route for USDT and XAUH.
- [Capital DEX XAUH on Tron](https://capitaldex.exchange/swap?chain=tron): Capital DEX also supports XAUH availability on Tron.
- [STON.fi XAUH swap](https://app.ston.fi/swap?chartVisible=true&chartInterval=1w&ft=USD%E2%82%AE&tt=EQCMk4_OujCnk46jApHnIRbmTtYTkSmfujV9X8Ye0qvsHVKh): TON DEX swap route for XAUH.
- Partner exchanges and supported wallets may also provide access, subject to their own availability, terms, spreads, fees, and compliance rules.

## x402 Integration Details

The [x402 XAUH purchase guide](https://xauh.gold/ai/x402-xauh-purchase.md) is the source of truth for x402 purchase integration. The summary below is for orientation only.

### Request Body

The `POST /purchases/xauh/requests/x402` request accepts:

- `tonWalletAddress`: TON wallet that will receive purchased XAUH jettons. Required when the request is not tied to a JWT user that already has a TON wallet.
- `network`: Optional CAIP-2 payment network. Production supports Base mainnet `eip155:8453` (default) and TON mainnet `tvm:-239`.
- `paymentAsset`: Optional payment token symbol. Base supports `USDC` (default), `USDT`, and `USDS`; TON supports `USDT` only and must be explicitly selected with `network: "tvm:-239"`.
- `paymentAmount`: Decimal payment amount in the selected payment token. Exactly one of `paymentAmount` or `xauhAmount` is required. Must meet the production minimum of `1` selected payment asset unit.
- `xauhAmount`: Decimal target amount of XAUH. Exactly one of `paymentAmount` or `xauhAmount` is required. Accepted only when the quote converts the XAUH amount into at least the production minimum payment amount.

### Supported x402 Payment Assets

The payment requirements returned by the API are authoritative. The current registry in the guide lists:

- Base Mainnet `eip155:8453`, `USDC`, contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`, transfer method `eip3009`, default asset.
- Base Mainnet `eip155:8453`, `USDT`, contract `0xfde4C96c8593536E31F229EA8f37b2ADa2699bb2`, transfer method `permit2`, explicitly selectable asset.
- Base Mainnet `eip155:8453`, `USDS`, contract `0x820c137fa70c8691f0e44dc420a5e53c168921dc`, 18 decimals, transfer method `permit2`, explicitly selectable asset.
- TON Mainnet `tvm:-239`, `USDT`, raw TEP-74 jetton master `0:b113a994b5024a16719f69139328eb759596c38a25f59028b146fecdc3621dfe`, 6 decimals, 120-second timeout, explicitly selectable asset.

USDS requires a one-time Permit2 token approval before the first payment and is not supported on Base Sepolia. The
minimum x402 payment is 1 unit of the selected payment asset.

### Discovery And Asset Selection

The [x402 discovery manifest](https://api.jamton.network/.well-known/x402) and its
[JSON alias](https://api.jamton.network/.well-known/x402.json) identify the purchase resource. Empty `GET` or `POST`
with body `{}` to the purchase endpoint returns synthetic HTTP `402` metadata. Compare `accepts` in the response
body with the decoded base64 `PAYMENT-REQUIRED` header. Discovery responses are not guaranteed to enumerate every
supported asset or match the manifest alternatives. The asset matrix describes explicit purchase routes.

For a purchase, explicitly select `network` and `paymentAsset`, provide the recipient and exactly one amount field,
and obtain a fresh unsigned quote. Use only its matching requirement unchanged, including `extra.xauhQuoteId`.
If the route is rejected, stop. Synthetic discovery cannot be paid directly and proves neither settlement nor
XAUH delivery; it is not authorization to spend funds.

### Flow

1. Call the production x402 purchase endpoint without a payment signature.
2. The API returns HTTP `402` and a `PAYMENT-REQUIRED` header containing a base64-encoded x402 `PaymentRequired` payload.
   A real quote includes `accepts[].extra.xauhQuoteId`. Preserve the entire selected requirement unchanged in the signed payload's `accepted`, including this ID and any additional metadata. Empty discovery probes do not carry a quote ID and cannot be paid directly.
3. The payer signs or submits the required payment using an x402-compatible wallet, SDK, or agent.
4. Retry the same endpoint with the signed payment payload in `PAYMENT-SIGNATURE`. The guide says the legacy `X-PAYMENT` header is accepted only as an SDK compatibility alias.
5. The API verifies and settles the payment through the configured x402 facilitator.
6. On success, the API returns HTTP `200`, a `PAYMENT-RESPONSE` header, and an XAUH purchase request.

For TON, send `network: "tvm:-239"` and `paymentAsset: "USDT"`. The HTTP `402` requirement contains `relayAddress`, `maxRelayCommission`, `assetDecimals`, and `assetSymbol` in `accepts[].extra`. The decoded signed `PaymentPayload` contains `signedBoc` and `walletPublicKey`. `accepts[].payTo` is the merchant payment recipient, while `tonWalletAddress` is the XAUH delivery recipient.

### Response And Status Tracking

For a paid x402 request, the response is the x402-specific success DTO. It includes `id`, `statusUrl`, `tonWalletAddress`, decimal `xauhAmount`, atomic `xauhAmountAtomic`, `xauhDecimals`, `status`, `deliveryStatus`, `payment`, and transfer/status timestamps. Agents should store `id`, `statusUrl`, `tonWalletAddress`, `xauhAmount`, `xauhAmountAtomic`, and `payment.txHash` for user-facing status tracking.

Use the returned request ID with:

```http
GET https://api.jamton.network/v1/purchases/xauh/requests/{requestId}
```

Important statuses:

- `PAYMENT_RECEIVED`: Payment was confirmed and automated XAUH delivery is continuing asynchronously.
- `COMPLETED`: XAUH delivery has been completed. If available, `tonTransferTxHash` contains the TON transfer hash.
- `FAILED`: The request failed. Check `failureReason` when present.
- `CANCELLED`: The request was cancelled. Check `cancellationReason` when present.
- `PENDING`: The request exists, but payment or processing has not reached a later state yet.

For the x402-specific paid response, `deliveryStatus: DELIVERY_PENDING` is the delivery form of the same non-terminal phase. Continue polling `statusUrl`; only `COMPLETED` confirms delivery.

The Base or TON wallet that pays the x402 invoice and the TON wallet that receives XAUH are separate identities. The signed payment payload determines the payer; `tonWalletAddress` determines the XAUH recipient. Agents must poll `statusUrl` until `COMPLETED` to confirm delivery.

## Tokenization, Redemption, Fees, And Storage

Eligible KYC-verified customers may tokenize LBMA 999.9 fine gold bullion, produced by PX Precinox S.A. in Neuchatel, into XAUH at a conversion ratio of 1 gram equals 1 XAUH. A tokenization fee of 0.3% applies to the total number of XAUH tokens minted.

Redemption of physical gold can be requested from 500 XAUH, equivalent to 500 grams of fine gold, and in multiples thereof. A redemption fee of 1% applies for redemptions of 1 kg or more, and a 3% fee applies for redemptions of 500 grams. The redemption fee does not cover transportation of the gold to the investor's location globally.

There are no recurring custody or insurance fees for holding XAUH. If an investor chooses to tokenize LBMA 999.9 fine gold bullion, the investor pays the one-time tokenization fee and a one-year storage and insurance fee applicable to the tokenized gold. For investors who prefer to purchase LBMA 999.9 fine gold bullion directly for ownership, a one-time transaction fee applies: 2% for purchases of 1 kg or more and 3% for purchases below 1 kg.

Agents should not simplify these fee descriptions into a single universal fee schedule. The applicable fee depends on whether the user is holding, tokenizing, redeeming, or purchasing gold directly, and on the terms in force at the time.

## Audit Reports And Primary Documents

### Whitepaper

- [XAUH whitepaper](https://xauh.gold/whitepaper.pdf)

The whitepaper identifies Herculis Tokens SA as a company incorporated under the laws of the Republic of Panama. It describes XAUH as a payment token intended to bridge tangible gold value and blockchain liquidity, backed by Swiss LBMA 999.9 pure gold stored in secure Swiss vaults and insured. It also contains important legal notices, risk disclosures, and limitations.

### KPMG Factual Findings Report, 21 January 2026

- [KPMG factual findings report, 21 January 2026](https://xauh.gold/audit-reports/01-21-2026.pdf)

KPMG's factual findings report covers 3.5 kg of physical gold stored in a secure vault in Switzerland and linked to 6 gold certificates issued by PX Precinox SA. KPMG performed agreed procedures and physically matched 6 gold certificates representing 3.5 kg of gold with stored gold bullions on 14 January 2026. KPMG also obtained ownership justification for 3.49965 kg of gold by one group entity.

### KPMG Factual Findings Report, 13 May 2026

- [KPMG factual findings report, 13 May 2026](https://xauh.gold/audit-reports/05-13-2026.pdf)

KPMG's factual findings report covers 11.5 kg of physical gold stored in a secure vault in Switzerland and linked to 14 gold certificates issued by PX Precinox SA. KPMG performed agreed procedures and physically matched 14 gold certificates representing 11.5 kg of gold with stored gold bullions on 11 May 2026. KPMG also obtained ownership justification for 11.49885 kg of gold by one group entity.

### KPMG Factual Findings Report, 1 July 2026

- [KPMG factual findings report, 1 July 2026](https://xauh.gold/audit-reports/07-01-2026.pdf)

KPMG's factual findings report covers 11.5 kg of physical gold stored in a secure vault in Switzerland and linked to 14 gold certificates issued by PX Precinox SA. KPMG performed agreed procedures and physically compared the 14 gold certificates with stored gold bullions on 30 June 2026 in a secure vault in Switzerland. KPMG also obtained ownership justification for 11.49885 kg of gold by one group entity. The report notes that, except for certificates 09509101, 09602175, 09602176, and 09602177, it was not possible to establish a link between the paid invoice and the delivered gold bullions because the invoices do not reference the gold certificates. It also notes a 0.00115 kg difference corresponding to the incorporation of other metals in pure gold.

### KPMG Factual Findings Report, 28 August 2026

- [KPMG factual findings report, 28 August 2026](https://xauh.gold/audit-reports/08-28-2026.pdf)

KPMG's factual findings report covers 15.5 kg of physical gold stored in a secure vault in Switzerland and linked to 18 gold certificates issued by PX Precinox SA. KPMG performed agreed procedures and physically compared the detailed list and serial numbers of the 18 certificates with stored gold bullions on 26 August 2026. KPMG also obtained ownership justification for 15.49845 kg of gold by one group entity. The report notes that, except for certificates 09509101, 09602175, 09602176, 09602177, 09602178, 09602179, 09602180, and 09602181, it was not possible to establish a link between the paid invoice and the delivered gold bullions because the invoices do not reference the gold certificates. It also notes a 0.00155 kg difference corresponding to the incorporation of other metals in pure gold. The procedures do not constitute an audit or review, and KPMG expresses no assurance on the accuracy of the 15.5 kg of gold.

## Blog And Content API

The public blog is available at [Herculis blog](https://xauh.gold/blog). The blog presents real-world cases and insights on tokenizing gold as a real-world asset, along with XAUH-related content.

There is also a public OpenAPI document for the Payload CMS blog API at [blog posts OpenAPI spec](https://xauh.gold/docs/api/posts.yaml). The public `robots.txt` disallows `/api-docs/*`, so agents should treat the YAML document as a direct reference only when explicitly needed.

## Legal And Compliance Notes

Legal notices require the following constraints when summarizing or acting:

- Do not present XAUH, any purchase link, or any market venue as investment advice, financial advice, tax advice, legal advice, or a recommendation.
- Do not describe the whitepaper as a prospectus or securities offering.
- Herculis Gold Coin is not qualified as a security and does not grant rights to company capital, income, dividends, voting, or governance.
- Purchase, trading, custody, redemption, and tax consequences depend on the user's jurisdiction and applicable terms.
- Buyers are responsible for understanding cryptocurrency, blockchain, custody, and transaction risks.
- Cryptocurrency purchases offer ChangeNOW and Changelly. The selected provider’s terms and compliance controls apply. Both current and historical purchase status URLs remain readable.
- Card payments through Wert are subject to Wert availability, terms, and compliance controls.
- Secondary-market transactions through CEX or DEX venues are subject to the terms, spreads, fees, liquidity, and compliance requirements of those market participants.
- Redemption is subject to applicable terms and onboarding procedures, including KYC verification.
- For ChangeNOW, Changelly, x402, and Wert, payment confirmation starts or advances automated asynchronous processing; it is not immediate final XAUH delivery.

## Recommended Agent Behavior

- When asked how to buy XAUH, offer the available methods neutrally: website card purchase at `/buy/card`, website cryptocurrency purchase at `/buy/crypto`, x402 for compatible agents or wallets, Biconomy, BTSE, Capital DEX on TON or Tron, STON.fi, and partner exchanges where available.
- When asked to make an autonomous x402 purchase, first read the [x402 XAUH purchase guide](https://xauh.gold/ai/x402-xauh-purchase.md) and [x402 OpenAPI spec](https://xauh.gold/ai/x402-openapi.json).
- When explaining x402, distinguish clearly between the Base or TON payer identified by the signed payment payload and the TON recipient wallet in `tonWalletAddress`.
- When a user has a purchase request ID, direct them to [purchase request status page](https://xauh.gold/buy/{requestId}) or the API status endpoint.
- When discussing backing, audit, or redemption, cite the [XAUH whitepaper](https://xauh.gold/whitepaper.pdf) and KPMG factual findings reports rather than relying only on summary text.
- When citing market availability, use exact venue names and links: [Biconomy XAUH/USDT market](https://www.biconomy.com/exchange/XAUH_USDT), [BTSE XAUH/USDT market](https://www.btse.com/en/trading/XAUH-USDT), [Capital DEX XAUH swap on TON](https://capitaldex.exchange/swap?chain=ton&tokens=usdt-xauh), [Capital DEX XAUH on Tron](https://capitaldex.exchange/swap?chain=tron), and [STON.fi XAUH swap](https://app.ston.fi/swap?chartVisible=true&chartInterval=1w&ft=USD%E2%82%AE&tt=EQCMk4_OujCnk46jApHnIRbmTtYTkSmfujV9X8Ye0qvsHVKh).

## Social Networks

- [X account](https://x.com/HerculisCoin)
- [Telegram channel](https://t.me/herculis_investments)
- [XAUH LinkedIn](https://www.linkedin.com/company/xauh)
- [HerculisCoin Facebook](https://www.facebook.com/herculiscoin)
- [YouTube channel](https://www.youtube.com/@HerculisGroup)
- [Herculis Instagram](https://www.instagram.com/herculis_coin/): Official Instagram account.
- [XAUH Binance Square](https://www.binance.com/fr/square/profile/xauh): Official Binance Square profile.
- [Herculis Gold Coin TikTok](https://www.tiktok.com/@herculis.gold.coi): Official TikTok profile.

## Market Data

- [CoinMarketCap profile](https://coinmarketcap.com/currencies/herculis-gold-coin/)
- [CoinGecko profile](https://www.coingecko.com/en/coins/herculis-gold-coin/)