Repository navigation
[docs-agent] Add Preconfirmations gRPC Subscribe page - #1734
Merged
Merged
Conversation
Documents the alchemy.preconf.v1.Preconf/Subscribe server-streaming gRPC method that streams Solana transactions from Jito BAM nodes before they land on-chain. New page lives under a standalone "Preconfirmations gRPC" nav section (sibling to Yellowstone gRPC) with slug reference/preconf-grpc-subscribe. Also adds a discovery card to the API Overview and Chain APIs overview. Requested-by: @andreidg31
🔗 Preview Mode
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
…nces Per Andrei's follow-up in the Slack thread, remove the explicit :443 TLS port from the endpoint / grpcurl example and drop the <Info> + inline cross-link that compared the Preconf service to Yellowstone gRPC. The page now stands on its own without framing Preconfirmations as a sibling-of-Yellowstone service. Requested-by: @andreidg31
dslovinsky
approved these changes
Oct 29, 2026
vahnag
approved these changes
Oct 30, 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
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
Documents the new
alchemy.preconf.v1.Preconf/Subscribeserver-streaming gRPC method that streams Solana transactions from Jito BAM nodes as they are sequenced into a block, before the block lands on-chain.The new page is a standalone section in the chains tab, sibling to Yellowstone gRPC (per follow-up guidance in the Slack thread: "let's put it separated from Yellowstone gRPC since it is a different method"):
/docs/reference/preconf-grpc-subscribecontent/api-reference/preconf/subscribe.mdxContent follows the structure of the source documentation: endpoint + auth,
grpcurlexample, filter structure proto, per-field reference, response structure, delivery semantics, pricing, errors, and the full.protoat the bottom. The page notes thatalchemy.preconf.v1.Preconfis a separate service from Yellowstone'sgeyser.Geyserbut shares thestreaming.alchemy.com:443host andx-tokenauth, and cross-links to the Yellowstone overview.Also adds a
Preconfirmations gRPCdiscovery card to the two "Standard APIs" overview pages that already surface Yellowstone gRPC:content/api-reference/introduction/api-overview.mdxcontent/api-reference/node-api/chain-apis-overview.mdxValidation
pnpm run validate:docs-yml→ ✅npx prettier --checkon all four touched files → ✅Not included (open questions)
content/api-reference/pricing-resources/pricing/compute-unit-costs.mdx. Preconf pricing (max(100 × n, 3,000)CU per slot) is documented on the new page itself but doesn't fit the existing bandwidth or per-method CU tables cleanly. Happy to add a dedicated section there as a follow-up if desired.Requested by
@andreidg31 (via Slack thread)