Solana Foundation Open-Sources tokens.xyz: Asset Registry and ~20-Endpoint API Now on GitHub

The Solana Foundation published the full codebase behind tokens.xyz on GitHub on August 10, making its verified asset registry and Assets API available for public inspection, forking, and community contributions. The repository, at github.com/solana-foundation/tokens, is an MIT-licensed monorepo covering the platform's Next.js frontends, backend services, Postgres schema, and Terraform infrastructure definitions.

Vibhu Norby, Foundation head of marketing, announced the release: "We open sourced @tokens. Fork and build something better." Developer relations engineer Steven Sarmiento followed with a technical thread walking through the repo's three main components.

Inside the tokens.xyz Monorepo: Apps, API, and Infrastructure Code

The repository groups the entire tokens.xyz stack in a single codebase. Web-facing surfaces are deployed on Vercel and include the public product site (apps/web), the API documentation site (apps/docs), the platform API at /v1/... (apps/api), and a dashboard for API key management (apps/app). Backend services run on Google Cloud Platform's Cloud Run and handle assets, pricing, usage, and admin operations. The Postgres database schema lives in db/ as ordered migrations applied via Cloud SQL.

The tech stack: Next.js 16 App Router, Bun workspaces managed with Turborepo, TypeScript, Tailwind CSS 4, Clerk for authentication, ClickHouse for analytics, and Upstash Redis for caching. The Assets API backend is built using the Effect TypeScript library.

The initial repo push landed on August 7. The formal announcement followed on August 10, after documentation and contributing files were updated to position it as a live, contribution-open project rather than a read-only snapshot.

The Canonical Asset Model and the Assets API

The design at the core of tokens.xyz is what the team calls the "canonical asset" model. Assets such as Bitcoin and Ethereum are canonical; every Solana mint that represents them (wrapped, bridged, natively issued, liquid staking token, or tokenized equity) is a variant. The asset registry groups and ranks those variants, and any mint can be resolved back to its canonical asset. A query for "Tesla" returns both the xStock (TSLAx) and Ondo-issued (TSLAon) variants on the same page, with liquidity, trust tier, and mechanism tags side by side.

The Assets API documentation lists approximately 20 endpoints drawn from that registry layer: asset search, market snapshots, OHLCV price history, price charts, DEX market listings, ticker data, risk summaries, curated lists, trending assets, and a news feed. According to Sarmiento, the web interface is the team's own live test of the API: "we are our own customer."

The Assets API was in beta and available on request as of April 2026. Open-sourcing the full codebase makes the implementation public, though end-to-end self-hosting documentation is still under development. The code, database schema, and Terraform definitions are all present, but the Foundation notes the end-to-end self-hosting path is not yet fully documented.

tokens.xyz Integrators and API Use Cases: Wallets, Trading Apps, AI Agents

The registry covers nearly 300 assets spanning crypto, stocks, ETFs, treasuries, currencies, and metals, according to the Solana Foundation's April 2026 product overview. Phantom, Titan, and DFlow are named integrators, and the platform lists more than 90 total integrators.

The intended audience for the API extends across four product types: wallets resolving asset identities before displaying balances; trading apps routing users to the deepest market per variant; analytics products unifying names, tickers, and mints under a single data layer; and AI agents verifying the correct mint before execution. That last use case has grown in relevance as Solana's tokenized asset inventory has expanded. Tokenized equities on Solana reached $1.45 billion in July 2026 trading volume, across multiple issuers and mint variants, the precise fragmentation problem a canonical registry resolves at the API layer.

MIT License, No Token, No Fees: What Open-Sourcing tokens.xyz Means

Tokens.xyz carries no token, charges no fees, and does not execute trades. The Foundation has described it as a public good, and the MIT license is consistent with that framing: any developer can fork the repository and run a derivative under their own terms.

The repository had accumulated 19 forks and 57 GitHub stars within hours of the August 10 announcement, per the project's GitHub page. At least one developer in replies indicated they had already forked it; another noted the Vercel-plus-Cloud-Run architecture as a reference for their own builds.

Sarmiento indicated the open-source transition is complete from the team's perspective, and new features and API endpoints are next: "Now that all this janitorial work is done, we can get back to shipping."