[docs-agent] Add Solana DAS API v2 spec + landing page (12 methods, Helius upstream naming)#1460
Merged
Conversation
…elius upstream naming) Adds a sibling Solana DAS API v2 page under NFT API with a new OpenRPC spec (`solana-das-v2`) covering the 12 canonical DAS methods. Three method names differ from v1 to match the Helius upstream: `getAssets` → `getAssetBatch`, `getAssetProofs` → `getAssetProofBatch`, `getAssetSignatures` → `getSignaturesForAsset`. Response shapes add `last_indexed_slot`, the MPL Core fields (`is_agent`, `agent_token`, `asset_signer`, `plugins`), and the `MplCoreAsset` / `MplBubblegumV2` / `MplCoreCollection` / `MplCoreGroup` interface values. Params consolidate on `options` (dropping the v1 `displayOptions` alias). The v2 backend is not yet in production; the landing page carries a Beta banner noting the endpoint host is subject to change and Try It may fail until backend rolls out. v1 stays live in parallel; no deprecation notice is added. Refs DOCS-145 Requested-by: @victorbware
🔗 Preview Mode
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9e3be6f190
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
…, not just renames Per @victorbware's Slack feedback, reframes the first bullet in the "Compared with v1" section from a rename-focused description to one that emphasizes v2 adds `getAssetBatch`, `getAssetProofBatch`, and `getSignaturesForAsset` to support paginated responses. Refs DOCS-145 Requested-by: @victorbware
Populates `examples[0].result.value` on every method in the DAS v2 spec so Fern's Response panel renders realistic 200 bodies instead of the empty `{"jsonrpc":"2.0","id":1}` placeholder. Values are sourced from the canonical Helius DAS docs (Mad Lads collection for getAsset/getAssetBatch/getAssetsByAuthority/getAssetsByGroup, the Helius compressed-NFT sample for getAssetProof/getAssetProofBatch/getAssetsByOwner, and the same canonical addresses used in the params example for the remaining methods).
Refs DOCS-145
Requested-by: @victorbware
…on both v1 and v2 Per @victorbware's Slack feedback: 1. All 12 DAS v2 JSON-RPC method names now carry a `_v2` suffix (`getAsset_v2`, `getAssetBatch_v2`, ..., `searchAssets_v2`) so v1 and v2 can coexist on the same endpoint. Landing MDX table + migration section reflect the new naming; URL slugs updated to Fern's `get-<method>-v-2` kebab-case pattern (matching the observed `getMultipleNewAddressProofsV2` → `get-multiple-new-address-proofs-v-2` mapping). Preview build will confirm the URL slugs; if Fern generates a different form we'll follow up. 2. `getAsset` CU cost bumped from 80 to 160 on BOTH v1 and v2. Updated in: `src/openrpc/alchemy/solana-das/solana-das.yaml` (v1 spec), `src/openrpc/alchemy/solana-das-v2/solana-das-v2.yaml` (v2 spec), the v1 landing MDX table, and `content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx` (Solana DAS APIs table). The compute-unit-costs.mdx Solana DAS table sits inside a `{/* cu:auto product="solana-das" */}` marker; the corresponding chain-config `topconfig.yml` may need a follow-up update so the value stays consistent on the next auto-sync. Refs DOCS-145 Requested-by: @victorbware
The v2 landing MDX hard-codes 12 method links under `solana-das-api-v2-endpoints/` (matching the desired product URL). Without an explicit `slug:` on the api entry, docs-site's `visitApiReference` derives the child path via lodash `kebabCase`, which splits `v2` into `v-2` and produces `solana-das-api-v-2-endpoints`. This mismatch would 404 every method link on the new landing page. Pin the slug to `solana-das-api-v2-endpoints` (same fix as the existing Polygon zkEVM api block a few sections above). Addresses codex P2 review comment on PR #1460. Refs DOCS-145 Requested-by: @victorbware
…page Removes the Beta/'not yet in production' panel, (Beta) suffixes in the v2 landing page frontmatter, and the beta caveats from the OpenRPC info.description and server names. Adds a 'Solana DAS APIs v2' link entry in content/docs.yml under the Solana chain section (mirrors the existing 'Solana DAS APIs' entry for v1). Refs DOCS-145 Requested-by: @victorbware
…or's searchAssets example
Adds sortBy: {sortBy: created} to the examples[0].params of getAssetsByAuthority_v2, getAssetsByCreator_v2, getAssetsByGroup_v2, and getAssetsByOwner_v2 so Fern's Try It form pre-populates the sortBy field. Without it, the form leaves sortBy blank and calls hit an empty-sort default that Victor reported as not working.
Replaces the searchAssets_v2 example with Victor's exact payload: ownerAddress + tokenType + limit + page + options (all 5 show flags set false).
Refs DOCS-145
Requested-by: @victorbware
dslovinsky
approved these changes
Jul 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new Solana DAS API v2 section as a sibling to the existing Solana DAS API under NFT API, with a new OpenRPC spec (
solana-das-v2) covering the 12 DAS methods and a landing page describing what's new.Three method names differ from v1, matching the canonical DAS upstream:
getAssetBatchgetAssetsgetAssetProofBatchgetAssetProofsgetSignaturesForAssetgetAssetSignaturesThe other 9 methods keep their existing names.
Schema differences from v1:
last_indexed_slot.is_agent,agent_token,asset_signer,plugins(with MIP-11groupsmembership).V2_NFT,MplCoreAsset,MplBubblegumV2,MplCoreCollection,MplCoreGroup.options(v1 accepteddisplayOptionsandoptionsas aliases; v2 keeps onlyoptions).getAssetProofBatchreturns an object keyed by asset ID, not an ordered array.getTokenAccountsusesmint/owner(v1 usedmintAddress/ownerAddress).searchAssetsrequires bothownerAddressandtokenType; addsisAgent,agentToken,assetSigner,tree.Beta caveat
The v2 backend is not yet in production and the endpoint host is subject to change before launch. The landing page carries a prominent Beta banner. Try It requests will fail with
Unsupported method: X on SOLANA_MAINNETon the three renamed methods (getAssetBatch,getAssetProofBatch,getSignaturesForAsset) until the backend rolls out. The existing v1 Solana DAS API stays live in parallel; no deprecation notice is added.Files
src/openrpc/alchemy/solana-das-v2/solana-das-v2.yaml— 12-method OpenRPC spec (allparamStructure: by-name)src/openrpc/chains/_components/solana/asset-v2.yaml— v2 shared schemas (self-contained; does not touch v1'sasset.yaml)content/api-reference/data/nft-api/alchemy-das-apis-for-solana-v2.mdx— new landing page with 12-method table, Beta banner, and a migration-from-v1 sectioncontent/docs.yml— sibling nav entry after v1 (api-name: solana-das-v2)Validation
pnpm run generate:rpc✅pnpm run validate:rpc✅ (both json-rpc and chains specs)pnpm exec prettier --check✅ on all changed filesOpen questions for reviewers
x-compute-unitson the affected methods.serversblock currently points tosolana-mainnet.g.alchemy.com/v2so the pages render cleanly in Fern, but the actual v2 backend URL is TBD. Once the backend team picks the URL, either drop a follow-up PR here or open a Linear ticket and we'll rev the spec'sservers.Linear
DOCS-145 — https://linear.app/alchemyapi/issue/DOCS-145/add-solana-das-api-v2-sub-page-openrpc-spec-12-methods-helius-upstream
Requested by
@victorbware (via Slack thread)