# Documentation

- Getting started
  - [What is DALP?](/docs/getting-started.md): DALP is a platform for issuing, managing, and servicing regulated digital assets across their lifecycle.
  - [Create your account and organisation](/docs/getting-started/onboarding.md): Create your Console account and deploy the organisation that owns your first DALP configuration.
  - [Issue your first asset](/docs/getting-started/your-first-asset.md): Define an asset class, issue an instrument, mint its tokens, and transfer them to a recipient in the Console.
  - [Where to go next](/docs/getting-started/where-next.md): Choose the DALP documentation path that matches the work you need to do next.
- The platform
  - [Platform Architecture](/docs/platform.md): Platform Architecture is how DALP divides one platform into named systems: what each owns, what crosses its boundary, and where reversibility ends.
  - [DALP Instance](/docs/platform/dalp-instance.md): A DALP Instance is one self-contained copy of the platform, deployed inside a boundary you choose and connected to ledger networks you approve.
  - [EVM Contract Set](/docs/platform/evm-contract-set.md): The EVM Contract Set is the identity, compliance, custody, and settlement contracts DALP deploys around one composable security token, checked in one call.
  - [System Version](/docs/platform/system-version.md): A System Version is how far an organization's on-chain components have advanced against the current module set; migrating repoints those that fell behind.
- Console
  - [Console overview](/docs/console.md): Hold, issue, operate, and report on digital assets, scoped to your account, the participant you act as, your organisation, or the platform as a whole.
  - Essentials
    - [Essentials](/docs/console/essentials.md): Choose a Console screen for pending work, indexed history, participant context, or search.
    - [Dashboard](/docs/console/essentials/dashboard.md): Use Dashboard to land on the right Console view for your role and reach every other screen from one place.
    - [Actions](/docs/console/essentials/actions.md): Use Actions to review scheduled, pending, and completed work for the active participant, and to run the one control each row actually offers.
    - [Activity](/docs/console/essentials/activity.md): Use Activity to inspect indexed events for your account and trace each one to its blockchain transaction.
    - [Acting as](/docs/console/essentials/acting-as.md): Use Acting as to select the participant whose data and authority the Console uses for your next operation.
    - [Search](/docs/console/essentials/search.md): Use Console search to find assets, users, organisations, contacts, and system contracts you already have access to, without leaving your current screen.
  - My assets
    - [My assets](/docs/console/my-assets.md): What the active participant owns and could acquire: holdings, valuation, and income on Portfolio, open Primary Offerings on Invest, scoped to who you act as.
    - [Portfolio](/docs/console/my-assets/portfolio.md): Use Portfolio to review the active participant's positions, value history, income, and the holder operations each row actually offers.
    - [Invest](/docs/console/my-assets/invest.md): Use Invest to find Primary Offerings open to the active participant, then subscribe within the limits each offering actually enforces.
  - Asset management
    - [Asset management](/docs/console/asset-management.md): Deploy a new asset from a template, find tokens issued by your organisation, and operate each one from its own workspace.
    - [Issue new asset](/docs/console/asset-management/issue-new-asset.md): Configure and deploy a new asset from an approved instrument template in the Console.
    - [All assets](/docs/console/asset-management/all-assets.md): Find tokens issued by your organisation and open their management workspaces from one table.
    - [External tokens](/docs/console/asset-management/external-tokens.md): Register and inspect tokens that were deployed outside the active DALP instance.
    - [Asset management insights](/docs/console/asset-management/insights.md): Read a one-page briefing on the organisation's assets: total value, launches, token activity, what needs attention, and how value is spread.
    - Manage
      - [Transfers](/docs/console/asset-management/manage/transfers.md): Move tokens, force a transfer as custodian, and manage transfer pre-approvals for a compliance-restricted asset.
      - [Mint and burn](/docs/console/asset-management/manage/mint-burn.md): Increase or reduce an asset's token supply from its management workspace.
      - [Pause and freeze](/docs/console/asset-management/manage/pause-freeze.md): Stop asset-wide transfers or hold a specified amount at one address so it cannot move.
      - [Fee administration](/docs/console/asset-management/manage/fee-administration.md): Set transaction and AUM fee rates and recipients, freeze either rate permanently, and collect accrued AUM fees for an asset.
      - [Yield and maturity](/docs/console/asset-management/manage/yield-maturity.md): Operate the yield schedule and maturity redemption already configured on an issued asset, and fund the treasury that pays them.
      - [Corporate actions](/docs/console/asset-management/manage/corporate-actions.md): Record approved corporate event terms on an issued asset, preview the holder allocations, and confirm execution.
  - Asset lifecycle
    - [Asset lifecycle](/docs/console/asset-lifecycle.md): How an asset changes hands after issuance: a first sale at a fixed price, order book trading, multi-party settlement at agreed amounts, and governance votes.
    - [Primary Offerings](/docs/console/asset-lifecycle/primary-offerings.md): A Primary Offering is the contract-governed first sale of new assets to investors, from funding through delivery, refunding only if the minimum is missed.
    - [Trading](/docs/console/asset-lifecycle/trading.md): Place orders on a permissioned venue, track reserved or escrowed balances, and follow fills through delivery or undo.
    - [Venue operations](/docs/console/asset-lifecycle/venue-operations.md): Operate the trading venue from the Console: list and halt markets, delist them, tune fees and bands, grant desk limits, and undo pending deliveries.
    - [Venue journey](/docs/console/asset-lifecycle/venue-journey.md): Follow one security from listing on the trading venue through investor onboarding, funding, trading, settlement, positions, reports, and the session close.
    - [XvP settlement](/docs/console/asset-lifecycle/settlement.md): XvP settlement is the Console workspace for a multi-party exchange in which every party's asset moves in one transaction or none move, so no party sends first.
    - [Governance votes](/docs/console/asset-lifecycle/governance.md): Governance votes are the Console workflow for creating an on-chain vote, casting ballots on it, and carrying out whatever a token's holders approved.
  - Organisation participants
    - [Organisation participants](/docs/console/participants.md): Manage everyone the organisation tracks an identity for: users with a login, entities without one, saved contacts, and the verification records a token checks.
    - [Users](/docs/console/participants/users.md): Manage organisation participants with login credentials, wallets, on-chain identities, roles, and invitations, and review a user's holdings and eligibility.
    - [Contacts](/docs/console/participants/contacts.md): Save counterparty names and wallet addresses for reuse during issuance and settlement, and learn what editing or deleting a saved contact does not affect.
    - [Entities](/docs/console/participants/entities.md): Review and register organisation participants without login credentials, act on incoming registration requests, and see which data feeds each one publishes.
    - [Insights](/docs/console/participants/insights.md): Read identity and verification counts for the selected organisation and network, and know when to stop trusting the aggregate and open the participant record.
    - [Verify a participant](/docs/console/participants/verify-a-participant.md): Confirm a participant has a registered identity, add the issuer-signed verification, and check the target token's eligibility requirements.
  - Asset design
    - [Asset design](/docs/console/asset-design.md): Build the reusable product shapes and compliance rules an issuer selects when creating an asset, plus the identity-evidence chain every compliance check reads.
    - [Asset classes](/docs/console/asset-design/asset-classes.md): Manage the business categories that organise instrument templates and decide where issued assets appear.
    - [Instrument templates](/docs/console/asset-design/instrument-templates.md): Define the reusable product shapes issuers select during asset issuance.
    - [Token features](/docs/console/asset-design/token-features.md): Reference for what each token feature does, its parameters and units, and how it is operated after issuance.
    - [Policy templates](/docs/console/asset-design/policy-templates.md): Assemble reusable compliance rules for instrument templates and asset issuance.
    - [Global controls](/docs/console/asset-design/global-controls.md): Configure compliance controls that apply across every bound token.
    - [Verification topics](/docs/console/asset-design/verification-topics.md): Define the claim topics used to classify identity evidence.
    - [Trusted issuers](/docs/console/asset-design/trusted-issuers.md): Authorise identity issuers for specific verification topics.
    - [Compliance providers](/docs/console/asset-design/compliance-providers.md): Connect an external verification service to claim topics and control what pausing, revoking, and reactivating each connection changes.
    - [Compliance modules](/docs/console/asset-design/compliance-modules.md): Reference for what each compliance module permits or refuses, its parameters and units, and where you configure it.
  - Reporting
    - [Reporting](/docs/console/reporting.md): See which reporting duty needs attention next, review filing attempts, check the published version each duty files under, and see who performed an operation.
    - [Filing calendar](/docs/console/reporting/filing-calendar.md): Review the organisation's filing periods and each one's urgency.
    - [Filings](/docs/console/reporting/filings.md): Review filing attempts, their anchor state, and the restricted actions available for one attempt.
    - [Obligations](/docs/console/reporting/obligations.md): Review reporting duties, publish a version, and manage optional on-chain evidence for future filings.
    - [Audit trail](/docs/console/reporting/audit-trail.md): Review who acted, under what role, on which operation, and with what outcome.
  - Organisation settings
    - [Organisation settings](/docs/console/organisation-settings.md): Configure the active organisation's identity, networks, on-chain roles, wallets, custody credentials, integrations, pricing inputs, and platform health signals.
    - [Organisation profile](/docs/console/organisation-settings/profile.md): Change the active organisation's name and logo, and choose whether holders see redemption funding.
    - [Organisation theme](/docs/console/organisation-settings/theme.md): Configure the active organisation's Console theme and branding assets.
    - [Organisation data feeds](/docs/console/organisation-settings/data-feeds.md): Register and maintain trusted on-chain data feeds for subjects and topics.
    - [System updates](/docs/console/organisation-settings/system-updates.md): Reference for the withdrawn Console screen that compared deployed system components with the reference directory.
    - [Wallet type](/docs/console/organisation-settings/wallet-type.md): Compare EOA wallets with smart wallets, check which networks are ready for smart wallets, and move the organisation to smart wallets once.
    - [Transaction funding](/docs/console/organisation-settings/transaction-funding.md): See who pays gas on the sidebar network, top up the shared gas wallets that pay it, withdraw from idle ones, and change the gas payer for that network.
    - [Platform status](/docs/console/organisation-settings/platform-status.md): Review live platform health across four service areas, plus the operational metrics and history behind them.
    - [Organisation networks](/docs/console/organisation-settings/networks.md): Select which platform catalogue networks the active organisation can use, and whether it can use more than one at a time.
    - [Admins and roles](/docs/console/organisation-settings/admins-and-roles.md): Assign administrative roles for the organisation's system on the selected network.
    - [Roles and segregation of duties reference](/docs/console/organisation-settings/roles-and-segregation-of-duties.md): Every role a DALP deployment checks, what each one permits, and which pairs of roles or people the platform keeps apart today.
    - [Webhook endpoints](/docs/console/organisation-settings/webhooks.md): Create webhook endpoints and inspect their lifecycle delivery health.
    - [Exchange rates](/docs/console/organisation-settings/exchange-rates.md): Enable tracked currencies and inspect the latest recorded exchange rates.
    - [Token pricing](/docs/console/organisation-settings/token-pricing.md): Review and edit token prices supplied by the feed system.
    - [Organisation custody](/docs/console/organisation-settings/custody.md): Manage the organisation's custody provider catalog, credentials, and execution health.
    - [Holiday calendars](/docs/console/organisation-settings/holiday-calendars.md): Create the calendars your organisation owns and close the days on which its filing deadlines and trading venues do not count.
  - Platform settings
    - [Platform admin](/docs/console/platform-admin.md): Manage organisations, the network catalogue and RPC endpoints, indexing scope, and base holiday calendars. Platform administrators only.
    - [Platform organisations](/docs/console/platform-admin/organisations.md): Create an organisation as a platform administrator, and review every organisation on the platform from one list.
    - [Platform networks](/docs/console/platform-admin/networks.md): Manage the platform network catalogue and its RPC endpoints.
    - [Indexing scope](/docs/console/platform-admin/indexing-scope.md): Choose which announced systems the Ledger Data reads on each network.
    - [Base calendars](/docs/console/platform-admin/base-calendars.md): Publish the platform-wide holiday calendars that every organisation can extend, and close days on them for every organisation at once.
  - My account
    - [Profile](/docs/console/my-account/profile.md): Update your Console account details and submit the personal information a regulated token checks before your wallet can receive it.
    - [Security](/docs/console/my-account/security.md): Set up the PIN, recovery codes, two-factor authentication, passkeys, and sessions that protect your Console account and your wallet's signing authority.
    - [API keys](/docs/console/my-account/api-keys.md): Create and manage the API credentials that authenticate Platform API requests on your behalf, without a signed-in Console session.
    - [On-chain identity](/docs/console/my-account/onchain-identity.md): View your own On-Chain Identity: its record, its status, and the verifications an issuer has attached to it.
    - [Acting as participants](/docs/console/my-account/acting-as-participants.md): View every participant you can act for, switch which one your actions apply to, and create a new participant when your organisation needs one.
- Concepts
  - [DALP concepts](/docs/concepts.md): Build a shared mental model for digital asset lifecycle, settlement, compliance, custody, and platform data.
  - Modeling assets
    - [Composable Token](/docs/concepts/modeling-assets/composable-token.md): A Composable Token lets an issuer bring a new regulated instrument to market by configuring facts, features, and rules, not new contract code.
    - [Instrument Templates](/docs/concepts/modeling-assets/instrument-templates.md): An Instrument Template lets an issuer configure a new instrument from an approved shape, instead of re-deciding what it records, does, and permits each time.
    - [Asset Class](/docs/concepts/modeling-assets/asset-class.md): An Asset Class groups instrument templates by economic category for catalog navigation and exposure reporting.
    - [Denomination Asset](/docs/concepts/modeling-assets/denomination-asset.md): A Denomination Asset lets a payout-bearing Token Feature, such as Maturity Redemption or a yield schedule, pay holders in a real asset it never custodies.
    - [Stablecoin](/docs/concepts/modeling-assets/stablecoin.md): A Stablecoin lets an issuer declare a currency peg and enforce a collateral check against a signed claim, on the same record as the rest of the token's life.
  - Issuing & markets
    - [Asset Lifecycle](/docs/concepts/issuing-and-markets/asset-lifecycle.md): Asset Lifecycle is the whole working life of a regulated tokenized instrument, from issuance through servicing to redemption, governed on one platform.
    - [Primary Offering](/docs/concepts/issuing-and-markets/primary-offering.md): A Primary Offering lets an issuer sell newly issued units once and resolve payment, allocation, and delivery or refunds as one on-chain outcome.
    - [Corporate Action](/docs/concepts/issuing-and-markets/corporate-action.md): A Corporate Action pays a coupon, a dividend, or a matured redemption straight to token holders, turning an issuer's announced terms into an on-chain payout.
    - [Token Distribution](/docs/concepts/issuing-and-markets/token-distribution.md): Token Distribution lets an issuer put an allocation into every wallet an eligibility list names, at one fixed cost, without a payout system per campaign.
    - [Trading Venue](/docs/concepts/issuing-and-markets/trading-venue.md): A Trading Venue lets a tenant run its own market for a tokenized asset after issuance. The venue contract never gains custodian power over what trades on it.
  - Settlement
    - [Transaction Lifecycle](/docs/concepts/settlement/transaction-lifecycle.md): The Transaction Lifecycle gives every write one auditable path to its outcome, so a same-key retry never leaves it unrecorded or runs it twice.
    - [Transaction Queue](/docs/concepts/settlement/transaction-queue.md): The transaction queue lets an integrator submit a blockchain write once and retry it safely, without ever risking a duplicate broadcast to the chain.
    - [Settlement Verdict](/docs/concepts/settlement/settlement-verdict.md): A Settlement Verdict lets you report success only when an operation actually happened, not from acceptance alone, across four recorded end states.
    - [XvP Settlement](/docs/concepts/settlement/xvp-settlement.md): XvP Settlement lets two or more parties exchange tokenized assets without either side delivering first: local legs settle atomically, external legs by hashlock.
    - [Workflow Engine](/docs/concepts/settlement/workflow-engine.md): The Workflow Engine lets a multi-step operation survive a process restart without repeating a finished step or losing track of one still in progress.
  - Compliance & identity
    - [Participant](/docs/concepts/compliance-and-identity/participant.md): A participant lets every role grant, claim, audit row, and delegated action point at one stable subject, so a person's history never splits.
    - [On-Chain Identity](/docs/concepts/compliance-and-identity/onchain-identity.md): An On-Chain Identity lets a subject's verification serve every asset that accepts it, so a screened wallet skips re-onboarding for the next regulated asset.
    - [Compliance Policy](/docs/concepts/compliance-and-identity/compliance-policy.md): A Compliance Policy lets a compliance team write eligibility and holding rules once, while a platform floor reaches every current-factory token.
    - [Transfer-Path Compliance](/docs/concepts/compliance-and-identity/transfer-path-compliance.md): Transfer-Path Compliance enforces a regulated token's rules inside the on-chain transfer itself, so a movement that fails any rule reverts and never settles.
    - [Role Grant](/docs/concepts/compliance-and-identity/role-grant.md): A role grant turns an institution's segregation-of-duties policy into a check the ledger itself runs before every privileged call.
    - [Delegated Authority](/docs/concepts/compliance-and-identity/delegated-authority.md): Delegated Authority lets a signed-in operator work inside another party's account. One check decides who may enter; the party's own roles decide the rest.
  - Custody & signing
    - [Smart Wallet](/docs/concepts/custody-and-signing/smart-wallet.md): A Smart Wallet lets a tenant require several signers to agree before an instruction moves assets, with the rule enforced on chain, not by one private key.
    - [Multisig](/docs/concepts/custody-and-signing/multisig.md): Multisig lets a tenant put a wallet under several signers, weighted so authority follows who must actually agree, before any of them can act alone.
    - [Custody Provider](/docs/concepts/custody-and-signing/custody-provider.md): A Custody Provider decides who signs for an organization's accounts, a managed custodian or the holder's own wallet, without changing accounts or approvals.
    - [Custody Approval](/docs/concepts/custody-and-signing/custody-approval.md): Custody Approval lets you require a decision from your own approvers before a key signs, enforced by the party holding the key, not the platform.
    - [Maker-checker](/docs/concepts/custody-and-signing/maker-checker.md): Maker-checker keeps a single mistaken instruction or a single compromised account from moving money, filing a report, or approving a corporate action alone.
    - [Operator Wallet](/docs/concepts/custody-and-signing/operator-wallet.md): An operator wallet lets your users transact without holding native gas: the platform pays the network fee, and you fund and monitor the wallet that covers it.
  - Records & evidence
    - [Ledger Data](/docs/concepts/records-and-evidence/ledger-data.md): Ledger Data lets an integration answer a holder list, a transfer history, or a compliance check with one query, instead of decoding chain events itself.
    - [Market Data](/docs/concepts/records-and-evidence/market-data.md): Market Data gives valuation, compliance, and reporting one governed price for an asset or currency pair, so they stop reconciling separate copies of the market.
    - [Audit Trail](/docs/concepts/records-and-evidence/audit-trail.md): An audit trail lets you show a regulator or an auditor who did what, under which role, without relying on the requester's own account of the request.
    - [Reconciliation](/docs/concepts/records-and-evidence/reconciliation.md): Reconciliation lets your register stay the book of record while you prove it agrees with the platform's ledger, and know exactly when a gap needs a person.
    - [Reporting Obligation](/docs/concepts/records-and-evidence/reporting-obligation.md): A reporting obligation lets your organisation prove to a regulator which rules governed a filing, and keeps that proof fixed even after the duty changes.
  - Events out
    - [Platform Event](/docs/concepts/events-out/platform-event.md): A Platform Event tells an integration what happened through a named, versioned message, so it need not interpret raw chain logs.
    - [Webhook Delivery](/docs/concepts/events-out/webhook-delivery.md): Webhook Delivery retries a signed notification for three days and records whether a counterparty was told, so an integrator skips its own retry logic.
  - Operating
    - [Platform Health](/docs/concepts/operating/platform-health.md): Platform Health lets a platform admin see in one glance whether the platform is healthy right now, instead of checking a dozen dashboards.
- Deployment
  - [Deploy and operate DALP](/docs/deployment.md): Plan a topology and posture, prepare prerequisites, install the charts, integrate SSO and observability, and run the instance with upgrades and runbooks.

  - **Plan**
  - [Deployment topologies](/docs/deployment/topologies.md): See what the DALP Helm charts deploy and how each backend role scales: three Platform API roles, PgBouncer in front of PostgreSQL, and the environment bundles.
  - [Hosting and access](/docs/deployment/hosting-and-access.md): Where a DALP Instance runs and how involved the vendor stays once it is running are separate decisions, chosen at install and revisited independently after.
  - [Security and compliance posture](/docs/deployment/security-compliance-posture.md): The layered control model an operator reviews before accepting a DALP instance, from authentication and authorization through custody, compliance, and networks.

  - **Prepare**
  - [Networks](/docs/deployment/networks.md): How a DALP instance's served-network list is configured, validated, and extended, for EVM networks.
  - [Gas settings per network](/docs/deployment/gas-settings.md): The per-network gas keys a DALP instance reads before it asks for funds, the layer order that decides each one, and the chains that ship calibrated.
  - [Prerequisites](/docs/deployment/prerequisites.md): The external endpoints, credentials, and cluster capacity a DALP installation needs ready before you run the Helm charts.

  - **Install**
  - Install
    - [Install DALP](/docs/deployment/install.md): The three Helm charts a DALP deployment composes, the Gateway API CRD bundle that precedes them, and the order to install them in.
    - [Helm charts](/docs/deployment/install/helm-charts.md): The dalp umbrella chart: what its subcharts default to, what a release gates on, and where the Gateway API CRDs come from.
    - [Configure values and secrets](/docs/deployment/install/values-secrets.md): Set the dalp chart's datastore, TLS, and secret-manager values, and choose how secrets reach each pod.
    - [Install the observability stack](/docs/deployment/install/observability-stack.md): Install the observability Helm chart a DALP instance exports to: an Alloy collector, VictoriaLogs, Tempo, VictoriaMetrics, and Grafana, then verify telemetry.
    - [Deploy DALP to OpenShift](/docs/deployment/install/openshift.md): Apply the OpenShift values overlay to run the dalp chart under a restricted security context and Routes instead of ingress.

  - **Integrate**
  - [Single sign-on](/docs/deployment/sso.md): Configure an external OIDC identity provider for the DALP Console, and understand that a complete entry replaces local sign-in for the whole deployment.
  - [Fireblocks policy for DALP vaults](/docs/deployment/fireblocks-policy.md): The Fireblocks policy rules each DALP vault needs with account abstraction off and on, and the limits DALP enforces where a Fireblocks rule cannot see them.
  - [Deposit funding instructions](/docs/deployment/deposit-funding-instructions.md): How an operator chooses which tokens investors can deposit and how the instructions API tells an investor where to send them.
  - [Observability](/docs/deployment/observability.md): The OpenTelemetry pipeline a DALP instance exports by default: traces, metrics, and logs, and how the admin debug bundle auto-wires to an in-cluster stack.

  - **Upgrade**
  - [Upgrades and migrations](/docs/deployment/upgrades-migrations.md): How the database migration Job runs inside a Helm upgrade, which hook type to choose, and what a failed migration leaves behind for you to inspect.

  - **Recover**
  - [Backup and disaster recovery](/docs/deployment/backup-recovery.md): What a DALP instance backs up inside the cluster, what your managed dependencies must back up themselves, and how to restore or plan a failover.
  - Runbooks
    - [Runbooks](/docs/deployment/runbooks.md): Diagnose and fix the readiness, indexing, and delivery problems platform operators run into most on a DALP instance.
    - [Platform API not ready](/docs/deployment/runbooks/platform-api-not-ready.md): A Platform API, indexer, or Workflow Engine pod runs but is not Ready: how to read the pod's own diagnosis, which waits are normal, and when a restart helps.
    - [Ledger indexing stalled](/docs/deployment/runbooks/ledger-indexing-stalled.md): The Ledger Data stops advancing on a chain: how to tell catch-up from a stalled chain, and which of three signatures decides the fix.
    - [Webhook deliveries failing](/docs/deployment/runbooks/webhook-deliveries-failing.md): A webhook endpoint stops receiving events: the retry schedule, the automatic circuit breaker that pauses a failing consumer, and how deliveries recover.
- API reference
  - [DALP API reference](/docs/api-reference.md): Authenticate, generate a client, and integrate the DALP Platform API through guides, the CLI, the OpenAPI explorer, and the error catalog.
  - Guides
    - [Authenticate with API keys](/docs/api-reference/guides/authentication-api-keys.md): Authenticate Platform API requests with an X-Api-Key header, or a Console session on session-or-api-key routes, and store the secret when you create it.
    - [Paginate list endpoints](/docs/api-reference/guides/pagination.md): Page DALP list endpoints with JSON:API sort, page, and filter query parameters, read the response links object, and stay inside the 200-item page-size cap.
    - [Read and handle DALP errors](/docs/api-reference/guides/errors.md): Read the DALP-#### id, category, and retryable flag on every error response, branch your integration on those fields, and never parse the message text.
    - [API versioning and deprecation policy](/docs/api-reference/guides/versioning-and-deprecation.md): Breaking API changes ship only on a new /api version, and a deprecated operation answers with Deprecation and Sunset headers for at least 90 days.
    - [Idempotency and async settlement](/docs/api-reference/guides/idempotency-async-settlement.md): Learn where Idempotency-Key deduplicates queued transactions and use Prefer to wait for on-chain settlement or return immediately.
    - [Onboard an investor through the API](/docs/api-reference/guides/onboard-an-investor.md): Create a user through the API, resolve the participant's identity wallet, register the identity under a country, and verify the investor with Sumsub.
    - [Sale terms and acknowledgement](/docs/api-reference/guides/sale-terms-and-acknowledgement.md): Upload a Primary Offering's terms documents, record their hash once during setup, then list, download, acknowledge and buy as an investor.
    - [Corporate actions](/docs/api-reference/guides/corporate-actions.md): Declare a corporate action, preview its effect on holders, then confirm or abort. Covers chunked mint or burn, the in-flight limit, and redemption approval.
    - [Corporate actions catalog reference](/docs/api-reference/guides/corporate-actions-catalog.md): The thirteen corporate action types grouped by mechanism, with the status lifecycle, the in-flight limit, and the allocation records used by each mechanism.
    - [Generate and download investor statements](/docs/api-reference/guides/investor-statements.md): Configure investor statement policy, generate a statement for a final date range, and download statements for the caller's own wallets.
    - [Send an issuer its shareholder list after an auction or at month end](/docs/api-reference/guides/issuer-shareholder-list.md): Produce one security's shareholder list at a record block, check that it adds up to total supply, and send the CSV, XLSX or PDF file to the issuer.
    - [Receive DALP webhooks](/docs/api-reference/guides/webhooks.md): Register an HTTPS endpoint, verify signed DALP webhook deliveries, rotate signing secrets, and update endpoint settings.
    - [Post DALP webhook events to a ledger](/docs/api-reference/guides/accounting-feed.md): The signed webhook feed that carries DALP activity, and the journal, account-key, reversal and idempotency rules an external ledger follows to post it.
    - [Read files and object storage](/docs/api-reference/guides/files.md): Read public branding assets from /dalp/* with no authentication, and private KYC, organization, and platform files from /dalp/private/* with a session.
    - [Read and submit price feeds](/docs/api-reference/guides/feeds.md): Read the on-chain price-feed directory, latest values, rounds, and staleness windows, and submit a signed observation as a trusted issuer on V1 or V2.
  - Webhooks
    - [Webhooks](/docs/api-reference/webhooks.md): How a DALP webhook reaches your endpoint, what your receiver checks on each request, and which page documents each part of the contract.
    - [Webhook event catalogue](/docs/api-reference/webhooks/events.md): Every webhook event the platform sends today, grouped by domain, with its lifecycle state, its trigger and the action your endpoint takes.
    - [Webhook subscription patterns](/docs/api-reference/webhooks/subscriptions.md): Lists the subscription pattern grammar, its validation rules, the default subscriptions, and the live events the defaults skip.
    - [Webhook lifecycle states and event sequences](/docs/api-reference/webhooks/lifecycle.md): The lifecycle states that DALP webhook events send today, the sequences an endpoint receives, and the states the platform reserves.
    - [Consuming webhook events](/docs/api-reference/webhooks/consuming.md): How a receiver reads DALP webhook deliveries: outcomes, identifiers, ordering, retries, Resend and Replay, receipts, payload shape and retractions.
  - TypeScript SDK
    - [TypeScript SDK](/docs/api-reference/sdk.md): A typed, namespaced client for every v2 route, generated from the platform's own declaration, with TanStack Query factories and a matching Effect surface.
    - [Install and construct a client](/docs/api-reference/sdk/install.md): Install the SDK from npm, construct a client against your instance, and choose the credential for where the code runs: a session cookie or an API key.
    - [Calling routes](/docs/api-reference/sdk/calling-routes.md): Every route is a node on one namespaced tree, called with one flat object the SDK splits into path, query, and body, returning the response envelope unchanged.
    - [Mutations and settlement](/docs/api-reference/sdk/mutations.md): A write that touches the chain returns the settled resource or the platform's 202 handle; retry safety, the acting context, and errors are yours to handle.
    - [Streaming routes](/docs/api-reference/sdk/streaming.md): Read streaming routes as async iterables through the DALP TypeScript SDK, with decoded events, cancellation, and error handling.
    - [TanStack Query](/docs/api-reference/sdk/react-query.md): Every route carries its own query and mutation factories, so a cache key derives from route identity and canonicalized input instead of hand-written keys.
    - [Server-side rendering](/docs/api-reference/sdk/server-rendering.md): On a server render the browser holds the session and the server does not, so the SDK forwards the request's headers under an origin allowlist.
    - [React Native](/docs/api-reference/sdk/react-native.md): Use the DALP TypeScript SDK from an Expo app: supported versions, the transport to pass, where the session lives, and how passkeys reach the device.
    - [The Effect surface](/docs/api-reference/sdk/effect.md): The same namespaced route tree returning Effect values instead of promises, with a tagged failure channel and interruption wired to the request.
  - Errors
    - [Errors overview](/docs/api-reference/errors/overview.md): Index of DALP's error catalogs and handling guidance. Map an error to the right reference page, find its domain, and choose the next action.
    - [DALP error index](/docs/api-reference/errors.md): Look up any error your integration can receive and jump to the reference page that explains its cause and its fix.
    - [Error handling](/docs/api-reference/errors/error-handling.md): Handle DALP API failures with stable error identifiers, retry decisions, and support-ready diagnostics.
    - [Platform API error reference](/docs/api-reference/errors/platform-api-error-reference.md): Complete reference of all Platform API error codes returned by the DALP API, with HTTP status, retryability, and remediation guidance.
    - [Error code reference](/docs/api-reference/errors/error-code-reference.md): Find the cause and the fix for every on-chain revert your contracts can return, with retryability for each.
  - CLI
    - [Install and configure the DALP CLI](/docs/api-reference/cli/install.md): Install the DALP CLI from npm, authenticate with a browser device code flow, and configure the API URL, active organization, and output format.
    - [CLI commands](/docs/api-reference/cli/commands.md): The DALP CLI generates a verb-first command tree from the Platform API. Learn the pattern, discover commands, and follow a write that has not settled.
    - [Using the DALP CLI with AI agents](/docs/api-reference/cli/ai-agents.md): Register the DALP CLI as an MCP server or an agent skill, run it safely from a coding agent's shell, and scope the session an operator hands an assistant.
- Changelog
  - [Changelog](/docs/changelog.md): Find every user-visible capability, API change, and operator workflow update shipped in the 3.x line, with context for what to act on.
  - DALP 3.2
    - [DALP 3.2: trading, income, and reporting](/docs/changelog/dalp-3-2.md): Assets issued on the platform can now trade on its own permissioned order book, pay income to holders, and produce regulatory filings and audit records.
    - [Trade it where you issued it](/docs/changelog/dalp-3-2/trading-venue.md): A tenant can run several permissioned venues with their own members, calendar, and rules, where investors and desks trade listed token pairs.
    - [Run the raise, not just the contract](/docs/changelog/dalp-3-2/primary-offerings.md): A primary offering, the first sale of a new asset, now has both sides in the Console: a desk that runs the raise and a portal where investors subscribe.
    - [Instruments that pay their holders](/docs/changelog/dalp-3-2/dividend-interest-yield.md): Two token features let an instrument pay income: dividend yield pays a declared amount per unit on a chosen date, and interest yield accrues continuously.
    - [A corporate action is now a record, not a batch you assemble](/docs/changelog/dalp-3-2/corporate-actions.md): Thirteen corporate-action types such as cash dividends and stock splits are recorded objects: enter the terms, read the effect on every holder, then confirm.
    - [A holder vote that carries out what it decided](/docs/changelog/dalp-3-2/governance-votes.md): A governance vote asks a token's holders to approve a decision, weighted by holdings on a record date, and a passing vote can execute the change after a delay.
    - [Nine product shapes the catalog could not express before](/docs/changelog/dalp-3-2/instrument-catalog.md): The catalog of instrument shapes grew from twenty-four to thirty-three, adding two sukuk structures, a digital asset class, a spot commodity, and more.
    - [Each organisation chooses which instrument templates it offers](/docs/changelog/dalp-3-2/template-publication.md): Instrument templates, the reusable product shapes an asset is issued from, are offered for issuance only when an organisation publishes them.
    - [Controls that hold when tested](/docs/changelog/dalp-3-2/compliance-controls.md): Six controls close gaps found in a two-class share structure: expiring claims, a sanctions rule the subject cannot undo, a minimum holding, and a supermajority.
    - [The filing your regulator asked for](/docs/changelog/dalp-3-2/regulatory-reporting.md): Report families now generate from platform data on your filing schedule, and every state-changing request is recorded with the person, role, and outcome.
    - [Wallets that need more than one person](/docs/changelog/dalp-3-2/weighted-multisig.md): A participant account can now be a multisig wallet where each seat carries its own weight and the bar to clear is a total of weights rather than a signer count.
    - [Find out before you sign](/docs/changelog/dalp-3-2/transfer-precheck.md): A read-only check answers whether a transfer would clear an asset's compliance rules before anyone signs, naming every blocking rule and who can resolve it.
    - [See what your submission is doing](/docs/changelog/dalp-3-2/live-operation-activity.md): Every Console operation now reports its progress through named phases in a tray that follows you across pages, survives a refresh, and offers an undo.
    - [An embedded wallet, and signing requests your policy can read, Ripple included](/docs/changelog/dalp-3-2/custody.md): A built-in self-custody wallet, signatures a custody provider can inspect, DFNS custody wallets on your network, and properties a Ripple policy can match.
    - [Own the road to the chain](/docs/changelog/dalp-3-2/network-control-plane.md): The platform runs its own connection layer: admins define networks and endpoint pools, traffic leaves a lagging node, and an organisation can use many chains.
    - [Refuse the wrong number](/docs/changelog/dalp-3-2/index-correctness.md): The Ledger Index now follows blocks by identity rather than height so a reorganization cannot mix data, and an inexact price is refused instead of rounded.
    - [The SDK types itself from the platform](/docs/changelog/dalp-3-2/typescript-sdk.md): The client keeps its namespaced shape with types from the platform's own routes, one flat argument per call, a bounded wait on writes, and query factories.
    - [TypeScript SDK 3.1 to 3.2 mapping](/docs/changelog/dalp-3-2/typescript-sdk-migration.md): A call-by-call map from the 3.1 TypeScript SDK to the 3.2 namespaced routes, flat arguments, narrowed responses, and retained client interpreters.
    - [Stop re-downloading what has not changed](/docs/changelog/dalp-3-2/response-caching.md): Read responses carry a version tag, so a client can ask whether anything changed instead of fetching the payload, and read-your-write moved into the platform.
    - [Legacy asset families are no longer created by default](/docs/changelog/dalp-3-2/legacy-asset-creation.md): The seven original asset families can no longer be created on a new deployment because they carry an older identity model; issued tokens keep working.
    - [The explanation, on the screen that needs it](/docs/changelog/dalp-3-2/contextual-documentation.md): Console screens that use a term of art now link to the page that defines it, so a reader meeting collateral or a record date can read what it means in place.
  - DALP 3.1
    - [DALP 3.1: run the platform as your own](/docs/changelog/dalp-3-1.md): Each organization brings its own custody provider, contracts deploy inside air-gapped clusters with operator-held keys, and admins get audited tools.
    - [Bring your own custody, per organization](/docs/changelog/dalp-3-1/org-custody.md): Each organization now configures its own custody provider, tests the credentials before adopting them, and rotates them from the Console with secrets masked.
    - [Deploy where no one else can reach](/docs/changelog/dalp-3-1/air-gapped-deployment.md): DALP deploys its contracts inside an air-gapped cluster, signing with a operator-held key, pulling mirrored images, and trusting storage behind a private CA.
    - [Run and support the platform](/docs/changelog/dalp-3-1/platform-operations.md): Archive and restore organizations with an audit trail, reset a user's onboarding, invite people with on-chain roles pre-assigned, and tighten KYC search.
  - DALP 3.0
    - [DALP 3.0: design your own digital asset](/docs/changelog/dalp-3-0.md): Reusable instrument and compliance templates let regulated teams move from policy definition to live instrument without rebuilding from scratch on every launch.
    - [Design your own assets from templates](/docs/changelog/dalp-3-0/asset-templates.md): Turn a proven asset setup into a reusable template, so the next instrument starts from a standard instead of a blank form.
    - [Write your compliance policy once](/docs/changelog/dalp-3-0/compliance-templates.md): Package a compliance policy (identity, jurisdictions, supply caps, approvals) once and apply it to every asset in a program, enforced at every transfer.
    - [Keep signing inside your own custody](/docs/changelog/dalp-3-0/custody.md): Sign through your own custody provider while DALP prepares, broadcasts, and tracks every transaction to confirmation, with keys that never leave the vault.
    - [Operators act, the platform sponsors gas](/docs/changelog/dalp-3-0/advanced-accounts.md): ERC-4337 smart wallets and a system paymaster remove the native-token balance requirement, so on-chain work runs under enforced role boundaries.
    - [Transactions that recover themselves](/docs/changelog/dalp-3-0/durable-transactions.md): Every transaction carries explicit state across preparation, approval, broadcast, and confirmation, so a stuck step recovers and a retry never resends.
    - [A blockchain index, built into the platform](/docs/changelog/dalp-3-0/ledger-index.md): A live, multi-chain index that decodes every on-chain event the moment a block is final, reorg-safe and queryable as business data, with balances at any block.
    - [Signed prices, on-chain](/docs/changelog/dalp-3-0/data-feeds.md): Push off-chain prices and values into assets through issuer-signed, per-token feeds. An asset only acts on a figure a named party has vouched for.
    - [One identity surface per participant](/docs/changelog/dalp-3-0/identity.md): Verified KYC claims live on-chain; the asset checks the claim at transfer time and never sees the documents. In 3.0 the full lifecycle lives on one surface.
    - [Token features that behave like instruments](/docs/changelog/dalp-3-0/token-features.md): Fees, yield, redemption, and conversion now carry the controls a real financial instrument needs.
    - [Lower gas on every on-chain operation](/docs/changelog/dalp-3-0/gas-optimization.md): DALP 3.0 optimizes the hot path: identity verification up to 40% cheaper, a supply-cap mint saves about 146,000 gas, and compliance checks run in constant time.
    - [Push signed events, stop polling](/docs/changelog/dalp-3-0/webhooks.md): HMAC-signed delivery with exponential retries and optional counter-signed receipts means every settlement, approval, and deployment reaches your systems.
    - [Platform health in one view](/docs/changelog/dalp-3-0/monitoring.md): One verdict tells you whether the platform can proceed, without leaving the product to stitch together three separate infrastructure views.
    - [Upgrade your platform from the on-chain directory](/docs/changelog/dalp-3-0/self-managed-upgrade.md): System updates compares your deployed components against the on-chain directory and upgrades every out-of-date implementation in one guided run.
    - [Drive all of it from the SDK, CLI, and MCP](/docs/changelog/dalp-3-0/cli-api.md): Every console action is available through the SDK, an AI-native CLI, and an MCP server that agents drive, under the same permissions and controls as a human.
    - [A typed v2 API built for real integrations](/docs/changelog/dalp-3-0/v2-api.md): The v2 REST API at /api/v2 adds JSON:API filtering and sorting, offset pagination, idempotency keys, and headers for identity, wallet routing, and timing.
    - [Hardened for enterprise security review](/docs/changelog/dalp-3-0/security.md): Authentication, key material, roles, and deployment, hardened and documented for an enterprise security review in DALP 3.0.
    - [Documentation rebuilt around the reader](/docs/changelog/dalp-3-0/documentation.md): DALP 3.0 splits docs into six audience tracks so each role reads pages written for their job, not a shared feature dump.

## Agent endpoints

- [Full corpus](/docs/llms-full.txt): every documentation page concatenated as markdown
- Page markdown: every page URL returns the page as markdown when the request sends Accept: text/markdown, or when .md is appended to the path, as in /docs/api-reference.md.
- [API v2 reference contract](/docs/api-reference/openapi-v2.json): the OpenAPI document as JSON
- [API v1 reference contract](/docs/api-reference/openapi-v1.json): the OpenAPI document as JSON
- Search: GET /docs/api/search?query=<terms> matches page titles, descriptions, headings, and body text, returned as JSON. 3 page groups are not in this index: /docs/api-reference/errors, /docs/api-reference/errors/error-code-reference, /docs/api-reference/errors/platform-api-error-reference. Find them through /docs/llms.txt, which lists every page including them. Add &tag= to hold the search to one section. It takes one value, never a list: getting-started, platform, console, concepts, deployment, api-reference, changelog, overview. Every page carries exactly one section, so &tag=a,b matches no page at all and returns an empty array. Add &limit= to change the result cap. The cap counts records, not pages: each matched page contributes one record for the page itself plus up to 8 text fragments from that same page, so the default of 60 records can be as few as 7 pages. An empty, fractional, zero, or negative value falls back to 60, and anything above 200 is capped at 200. Every response reports the cap it applied in the X-Docs-Search-Limit header, and says in X-Docs-Search-Truncated whether more records were available: true means raise &limit= or narrow the query, false means the array is the complete result set.
- MCP: /docs/api/mcp is a Model Context Protocol server over streamable HTTP with list_pages, get_page, and search tools.