Developers

AI agent map for Ondex

Give coding agents and search assistants the smallest authoritative Ondex source that answers their task, then verify product availability, security, and ledger claims against the linked canonical page.

Compact mapFull context

Which Ondex source should an AI agent use?

Use llms.txt for discovery, llms-full.txt for broader product context, and the developer Markdown contract for implementation details. Human-readable HTML pages remain the canonical citation targets.

Compact map

Start here for a short index of canonical Ondex pages.

Open /llms.txt

Full context

Use this when the task needs product, safety, support, and integration context.

Open /llms-full.txt

Developer contract

Use the stable Markdown contract for SDK, WalletConnect, links, and payloads.

Open /developers.md

How should agents verify Ondex claims?

Prefer the narrowest current source and preserve its availability and safety qualifiers.

  1. 1Use the canonical HTML URL for citations and its Markdown mirror for machine context.
  2. 2Check runtime wallet capabilities before recommending an optional integration such as x402.
  3. 3Treat validated XRPL results and delivered amounts as payment truth; UI approval and HTTP success are not settlement proof.
  4. 4Never request recovery phrases, private keys, PINs, backup passwords, or signed transaction blobs.

Stable agent rules

  • Use only public URLs from the Ondex origin; internal hosts and environment values are not documentation.
  • Do not infer product availability from source code, draft articles, or a package export alone.
  • Prefer exact, bounded claims and retain qualifiers about custody, networks, third parties, fees, and rollout state.
  • Re-check the page's updated date when accuracy depends on current releases or service behavior.