Data residency & privacy statement

How the Mekong x402 API fleet (api.mekongtradeintel.com) handles your data — stated plainly, because agent operators deserve to know before they route traffic through anyone's API. Last updated 2026-10-25.

Where the service runs

Layer	Location
API servers	Singapore (Contabo) and Hanoi, Vietnam (InferenceHub). Request processing and operational logs live on these servers.
Payments	Settle on the Base blockchain (Coinbase's public L2). Payment authorisations are verified via the CDP facilitator.
Upstream data sources	Endpoints fetch from public sources (e.g. SEC EDGAR, DexScreener, Open-Meteo, public RSS). Your inputs are passed to an upstream only where the endpoint's function requires it (e.g. a URL you ask us to convert, a ticker you ask us to price).

What you send us

Request inputs — the JSON body or upload for the endpoint you call (a ticker, a domain, a PDF URL, an audio file). Inputs are processed to produce your response.
Payment authorisation — when you pay, your signed x402 authorisation contains your wallet address, the amount and the recipient. That is how the protocol works; there are no accounts, passwords or API keys to leak.
Ordinary HTTP metadata — IP address, user-agent, timestamps, as with any web service.

What is logged, and why

Log	Contents	Purpose
Paid-call log	Endpoint, timestamp, payer wallet address, amount, settlement transaction	Accounting, settlement reconciliation, dispute evidence
Free-trial log	Endpoint, timestamp, IP address	Trial quota enforcement and abuse prevention (trial access is keyed by IP)
Operational logs	Errors, response codes, service health events	Keeping the fleet up

Logs are kept on the API servers named above for as long as they are needed for accounting, abuse prevention and operating the service. We do not publish them; aggregate, de-identified counters (e.g. trial-call counts per endpoint) appear on the proof-of-demand page.

Permalinks (opt-in by design of the response)

Paid calls on permalink-enabled endpoints (currently brief and tokenprice) include a permanent _permalink: the paid result is stored under an unguessable link (/tools/result.html?id=…) so the buyer can re-open or share exactly what they paid for. Anyone holding the link can view that result — treat it like a receipt link. To have a stored result removed, contact us with the link or the settlement transaction and we will delete the stored copy; the on-chain payment record itself is public and cannot be deleted by anyone.

What we never do

We do not sell request data, inputs or logs to anyone.
We do not use your inputs to train models.
We do not require accounts, emails or API keys, and we do not set advertising or cross-site tracking cookies on API responses.
We do not see or store your private key — payments are signed in your own client; we only receive the signed authorisation.

On-chain caveat: x402 payments settle on a public blockchain. The payer address, recipient, amount and transaction hash of every settlement are visible to anyone on a block explorer. That is a property of the payment rail, not a disclosure by us — and it is also what makes your payment independently verifiable (see tx-verified ratings).

Contact

Questions, removal requests for stored permalink results, or anything unclear in this statement: [email protected].

Built by Mekong Trade Intelligence — pay-per-call APIs for AI agents, settled in USDC on Base. See also: migration kit · open revenue · /.well-known/x402