Dinari

• Name: Dinari
• URL: https://dinari.com/
• Category: tokenized public-securities company / brokerage-and-wallet integration control plane / compliance-and-corporate-actions operator
• Tags: ethereum-ecosystem
• Summary: Dinari belongs in companies/, not only projects/, because the durable dependency is a named operator that controls partner onboarding, KYC/KYB, wallet linkage, broker routing into traditional markets, jurisdiction and asset coverage, corporate-actions handling, and production API access for tokenized public securities. The useful question is not just what tokenized stock API exists? but which company controls the brokerage, compliance, lifecycle, and developer-access shell behind dShares?
• What it does:
  • Operates dShares and related tokenized-public-securities products rather than only publishing a token wrapper or marketing page
  • Provides APIs for entity creation, account management, wallet management, KYC workflows, funding flows, and production deployment under one company-managed integration surface
  • Exposes stock metadata, quotes, order placement, and hosted-trading flows that connect tokenized positions back to broker-routed traditional-market activity
  • Handles lifecycle details including dividends, corporate actions, stock splits, restrictions, fees, taxes/reporting, and wallet-linked asset handling
  • Publishes SDKs and developer tooling across multiple languages, plus an MCP-ready path, which makes Dinari a real operating dependency for integrators rather than a one-off issuer site
• Key claims:
  • Dinari’s homepage positions the company as offering API & Tokens for 1:1 Backed US Stocks, ETFs, & More, which is a direct first-party signal that the operator shell and the asset wrapper travel together
  • The homepage says Dinari operates across 85+ jurisdictions, emphasizes institutional-counterparty compliance expectations, and describes compliance controls enforced at the token level including KYC gating, geographic restrictions, accredited-investor verification, and AML monitoring
  • The homepage also says Dinari uses tokenization-on-demand, where customer orders are placed on traditional financial markets before a token is minted, which makes the broker-routing and issuance workflow an operator question rather than a generic onchain primitive
  • Dinari’s quickstart docs require partner-account creation, login at partners.dinari.com, and API-key generation before integrations can proceed, reinforcing that integrators inherit a company-managed access and credential boundary
  • The broader docs cover entities, wallets, KYC, stock data, orders, dividends, corporate actions, restrictions, taxes, and production deployment, which is the clearest sign that Dinari should be read as tokenized-securities operations infrastructure rather than only a token product
• Whitepaper: No standalone company whitepaper is the important artifact here. The strongest current primary materials remain Dinari’s official site, quickstart and broader docs, llms.txt, entity-management and stock-data pages, onboarding/get-started materials, and public SDK repositories; see ../whitepapers/dinari-primary-sources-2026-04-26.md.
• Sources:
  • https://dinari.com/
  • https://docs.dinari.com/docs/quickstart
  • https://docs.dinari.com/llms.txt
  • https://docs.dinari.com/docs/stock-data
  • https://docs.dinari.com/docs/entity-management
  • https://dinari.com/get-started
  • https://github.com/dinaricrypto
  • https://github.com/dinaricrypto/dinari-api-sdk-go
  • https://raw.githubusercontent.com/dinaricrypto/dinari-api-sdk-go/master/README.md

Internal linkages

• Product-layer note: dinari.
• Useful adjacent company reads: archax, securitize, and zerohash.
• Useful product-level contrasts where the asset or reserve architecture matters more than one hosted operator shell: m0 and circle-usdc.

Protocol / company boundary

• dinari is the product-layer note for the tokenized-securities API and dShares surface developers and end products integrate against.
• This company note is the operator boundary: partner onboarding, API-key issuance, entity and wallet admission, KYC/KYB review, jurisdiction and asset coverage, broker routing, corporate-actions handling, restrictions, taxes/reporting workflow, and lifecycle-state publication all sit with Dinari as a named company.
• That split matters because integrators are not inheriting only a tokenized-stock contract or an API schema. They are inheriting Dinari-managed compliance, brokerage, lifecycle servicing, and production-access assumptions.

Control surface

• Practical authority sits in who gets production credentials, which entities and wallets are admitted, how customer orders map into traditional-market purchases before token minting, what restrictions and geography controls apply, how dividends and corporate actions are processed, and how taxes/reporting or redemption-like lifecycle events are surfaced.

• The sticky dependency is operational memory: once a fintech, wallet, broker interface, or treasury stack hardens around Dinari-managed entities, wallets, broker routing, corporate-actions handling, and token lifecycle state, the real lock-in is to the company-run operating shell rather than to a neutral token primitive.

• Read Dinari as tokenized-securities market plumbing first, and as a token wrapper second.

• Last reviewed: 2026-08-07 UTC