[docs-agent] Add Solana Account Archive guide, OpenRPC entry, CU pricing row - #1492
[docs-agent] Add Solana Account Archive guide, OpenRPC entry, CU pricing row#1492alchemy-bot wants to merge 2 commits into
Conversation
…ing row
Adds the initial docs for Solana Account Archive: an extension of `getAccountInfo` with three new mutually-exclusive parameters (`slot`, `lastUpdateBeforeSlot`, `firstUpdateAfterSlot`) for point-in-time and cursor-based historical reads. Coverage extends back to July 2025 with no pruning.
Changes:
* New guide + FAQ page at content/api-reference/solana/account-archive.mdx sourced from the internal Notion doc.
* New OpenRPC spec at src/openrpc/alchemy/solana-account-archive/solana-account-archive.yaml with three worked examples (point-in-time, walk-backward, walk-forward) and error -32020 documented for cursor-past-coverage.
* docs.yml: new 'Solana Account Archive' section under Solana with the guide page + flattened endpoints entry.
* compute-unit-costs.mdx: new 'Solana: Account Archive' block with TBD rows and a note that final per-method pricing is pending.
Assumptions flagged for reviewer confirmation:
* Endpoint host uses the standard `solana-mainnet.g.alchemy.com/v2/{apiKey}` (drop-in with normal Solana calls). Easy to switch to a distinct archive host if that's the actual routing.
* Chain scope: mainnet only for v1 (no devnet/testnet server entries). Add a devnet server if the archive is available there.
* No preview / private-beta callout on the guide. Add one if this ships behind an allowlist.
* CU pricing left as TBD per the original ask ("temporary for now if you dont have per method CU pricing").
Refs DOCS-168
Requested-by: @clinder777
🔗 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: bf6f434e94
ℹ️ 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".
|
|
||
| `jsonParsed` encoding works on historical state: the same decoders a | ||
| standard RPC node uses are applied to the historical bytes. | ||
| x-compute-units: 10 |
There was a problem hiding this comment.
When this OpenRPC spec is published, x-compute-units: 10 makes the Account Archive endpoint advertise a definitive 10-CU cost for getAccountInfo, but the pricing page added in the same commit says archive lookups with slot, lastUpdateBeforeSlot, or firstUpdateAfterSlot are still TBD. For users reading the generated endpoint reference instead of the pricing page, historical archive calls will appear priced as standard getAccountInfo; drop this field or make both places agree until pricing is finalized.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fair catch. Dropped the hardcoded x-compute-units: 10 from the archive getAccountInfo in commit a6d6405 so the spec no longer advertises a definitive CU cost while the pricing page still shows TBD. Once real per-method CU values land in topconfig.yml, we can add the field back with the correct value (and refresh the pricing table in the same PR).
Codex flagged the inconsistency between the OpenRPC spec advertising x-compute-units: 10 and the pricing page showing TBD for the three archive params. Since Canaan's original ask was to leave pricing as TBD until topconfig.yml values land, remove the hardcoded CU value from the spec so both surfaces agree. Refs DOCS-168 Requested-by: @clinder777
1 participant
Summary
Adds the initial docs for Solana Account Archive, Alchemy's historical account state service. Answers
getAccountInfofor any Solana account at any historical slot from July 2025 onward, using the same request and response shapes as standard Solana RPC.The archive extends
getAccountInfowith three mutually-exclusive parameters, also mutually exclusive withminContextSlot:slotlastUpdateBeforeSlotfirstUpdateAfterSlotOmit all three for a normal latest-state read: the archive is a drop-in superset.
Changes
content/api-reference/solana/account-archive.mdx, sourced from the internal Notion doc. Covers the API surface, cursor iteration pattern, backfill-via-replay architecture, trust model, and 8 FAQ entries.src/openrpc/alchemy/solana-account-archive/solana-account-archive.yamlwith three worked Try It examples (point-in-time, walk-backward, walk-forward) and error-32020documented for cursor-past-coverage.docs.yml: newSolana Account Archivesection under Solana with the guide page + a flattened endpoints entry.compute-unit-costs.mdx: newSolana: Account Archiveblock with TBD rows and a note that final per-method pricing is pending.Assumptions to confirm
Filed as a fast turnaround on Canaan's ask — flagged here for reviewer input before merge:
solana-mainnet.g.alchemy.com/v2/{apiKey}(matches the doc's "drop-in superset" framing). Easy to swap to a distinct archive host if that's the actual routing.solana-devnetserver entry). Add if the archive is available on devnet/testnet.TBDper Canaan's original message ("temporary for now if you dont have per method CU pricing"). Will fill in oncetopconfig.ymlvalues land.Validation
pnpm run generate:rpc→ ✅pnpm run validate:rpc→ ✅Successfully validated json-rpc OpenRPC specspnpm run lint→ 0 errors (6 pre-existing baseline warnings unrelated to this diff)Linear
DOCS-168
Requested by
@clinder777 (via Slack thread)