> For the complete documentation index, see [llms.txt](https://docs.useicaria.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useicaria.xyz/architecture/platform.md). # Platform The reference front-end at useicaria.xyz/platform, and the standards it is held to. A Next.js application at [useicaria.xyz/platform](https://useicaria.xyz/platform) is the reference client, running on the same public [API](/architecture/api.md) and the same contracts that any integrator can reach. Keys never touch it, funds never pass through it, and no privileged route exists behind it. Making the honest mechanics readable is the whole point of it. ## The ticket At the centre of the product sits the swap ticket, which renders the [pricing formula](/protocol/pricing-and-spreads.md) rather than concealing it: * Mid, spread and fee as three labelled numbers, given in bps and USDG, with the oracle round available as a link. * A regime badge on the face of the ticket: "US markets closed. Weekend spread ×3 applies." Learning about the session after the fill is not something that happens here. * An all-in rate guarded by the slippage bound, with a countdown against RFQ quote validity. * Two-leg swaps showing both legs, each itemised. Fills come back as receipts carrying the on-chain breakdown and a Blockscout link. Since the event holds that same decomposition, what got quoted is demonstrably what got charged, every time. ## Onboarding Connect Robinhood Wallet, MetaMask or any standard wallet, or spin up an embedded smart account through Alchemy Account Kit with a passkey. Eligibility onboarding walks the attestation flow with the KYC provider, and the platform shows eligibility state before anything gets signed, so an ineligible user reads which rule applies instead of seeing a revert. A first swap folds the Permit2 approval and the swap into one sponsored user operation. ## Portfolio Listed holdings in a wallet-centred view: balances in both token and share terms via `uiMultiplier()`, valuations from the same guarded oracles the vaults quote against, cost basis and realised PnL rebuilt out of on-chain history, and LP positions showing value per share, accrued spread income and each vault's current inventory mix. ## Explorer surfaces The [trade explorer](/using-icaria/trade-explorer.md) and [execution quality](/transparency/execution-quality.md) pages are part of the platform and load without a wallet connected. Transparency surfaces are public by definition, so no part of the venue's record hides behind a login. ## Experience standards [Design principles](/introduction/design-principles.md) sets the bar: calm, technical, precise. Concretely: * Figures set in tabular numerals and aligned, bps and USDG kept out of the same column, timestamps in the reader's zone with UTC on hover. * Empty, loading and error states written as complete sentences that say what happened and what to try next. * Degradation stated openly: with the quote service down, the platform quotes vault-only off the RPC and says as much; with the RPC down, it says that rather than spinning indefinitely. * Dark patterns of every kind absent: no slippage preselected above the default, no invented urgency, no concealed fees. This venue's economics hold up fine once understood. ## Self-hosting Source for the platform is public. Point `pnpm dev` at any RPC and the public API and you reproduce the entire experience except the hosted KYC flow, which any issuer the registry accepts can stand in for. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.useicaria.xyz/architecture/platform.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.