Docs/genesis public api coverage - #547
Open
tonyboylehub wants to merge 9 commits into
Open
Conversation
…1 spec The public API at api.metaplex.com/v1 exposes 13 endpoints but only 7 were documented. This adds the missing coverage: - New Agents > API Reference section: list/get agents, A2A agent-card, mint, fund, and withdraw endpoints (served from the Metaplex app) - New Verify Twitter page under Genesis Integration APIs, plus the previously undocumented twitterVerificationToken field on Register Launch - Creator rewards claim and twitter verify added to the Integration APIs endpoint table - Draft OpenAPI 3.1 spec at public/openapi/metaplex-api-v1.yaml covering all 13 endpoints (redocly-lint clean), linked from the Integration APIs overview
The API at api.metaplex.com serves more than Genesis (agent registry,
verification), so the REST reference now lives at /api as its own product
('Metaplex API', Dev Tools category) instead of being split between
smart-contracts/genesis/integration-apis and agents.
- Move 8 launch endpoint pages (en/ja/ko/zh) and the 6 new agent endpoint
pages to src/pages/{locale}/api/; unified overview page with Launches and
Agents endpoint tables in all four locales
- Keep fetch-bucket-state / fetch-deposit-state under Genesis (SDK chain
methods, not REST); Genesis and Agents navs now point at /api
- Middleware: narrow the /en rewrite skip from /api to /api/og so /api/*
serves docs content while the OG image route keeps its literal path;
locale-aware 308 redirects for all moved integration-apis URLs; legacy
aggregation redirects point straight at /api (no double hop)
- Verified: production build green, old URLs 308 to /api equivalents,
/api/og and chain-method pages unaffected
The spec now lives in the app repo next to the routes it describes and is served at https://api.metaplex.com/v1/openapi.yaml, so the hand-copied public/openapi/ file is removed and the /api overview links to the canonical URL instead. Keeping one copy prevents the two repos drifting.
…DE.md Records for future contributors (human and LLM): the /api pages document the API implemented in genesis-app; the OpenAPI spec's canonical home is that repo (never copy it here); endpoint changes arrive as tickets from genesis-app PRs (route authors may not have this repo cloned); and the /api/og middleware skip-list constraint.
…n, and API category in llms.txt
… curve parameters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Warning Review limit reached
Next review available in: 45 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (42)
Summary by CodeRabbit
WalkthroughThe PR creates a top-level Metaplex REST API documentation product. It adds endpoint references in English, Japanese, Korean, and Chinese, updates navigation and catalogs, redirects legacy Genesis API routes, and adds Genesis bonding-curve parameter documentation. ChangesMetaplex API migration
Estimated code review effort: 4 (Complex) | ~60 minutes Possibly related PRs
Suggested reviewers: Sequence Diagram(s)sequenceDiagram
participant Client
participant Middleware
participant APIReference
Client->>Middleware: Request legacy Genesis integration-apis route
Middleware->>Middleware: Match locale and supported API slug
Middleware-->>Client: Redirect to localized /api route
Client->>APIReference: Open REST endpoint documentation
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 35
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/components/products/index.js`:
- Line 70: Reorder the product registry entries around api so the full registry
remains alphabetically sorted, placing api before das while preserving all
existing entries.
In `@src/pages/en/api/index.md`:
- Around line 66-98: Add the required ## Quick Reference, ## Glossary, and ##
Notes sections to the API overview, placing the endpoint summary under Quick
Reference, API terminology under Glossary, and compatibility or usage caveats
under Notes. Preserve the existing launch, agent, and transaction-building
endpoint content while organizing it beneath the appropriate section headings.
- Around line 140-145: Update the API docs table in the index page so the
canonical OpenAPI specification is labeled on the YAML entry rather than the
JSON entry. Keep the `openapi.json` row as an alternate representation, and use
the existing URL symbols (`/v1/openapi.yaml`, `/v1/openapi.json`) to make the
canonical-vs-alternate distinction explicit without changing the rest of the
table.
In `@src/pages/en/api/list-agents.md`:
- Around line 175-176: Update the agent-list response handling around
response["data"]["agents"] to check the response success status before accessing
nested data, and validate that agents is an array before reading its length.
Replace the unwrap-based access with safe handling that preserves the endpoint’s
error response behavior and avoids panics.
In `@src/pages/en/smart-contracts/genesis/bonding-curve-parameters.md`:
- Around line 2-5: Add the required created frontmatter field alongside updated
in the Bonding Curve Protocol Parameters page, using the page’s creation date
while preserving the existing metadata values.
- Around line 47-58: Update the Genesis product configuration in the Bonding
Curve navigation within src/components/products/genesis/index.js to add a
“Protocol Parameters” child linking to
/smart-contracts/genesis/bonding-curve-parameters. Preserve the existing
navigation structure and labels.
- Around line 47-58: Add a concise declarative summary sentence immediately
after each of the Protocol Parameters, Fee Schedule, Starting Price, and
Constant Product Invariant headings, before their existing tables, nested
headings, or code blocks; ensure each sentence directly states the section’s key
answer and leave the supporting structures unchanged.
- Around line 83-88: Update the post-bond fee values in the bonding-curve
parameters page to match the postBondTrading constants: use 0.21% for LP fees
and 0.04% for the Raydium fee. Apply the same values consistently in the FAQ
answer and Quick Reference table.
- Around line 96-110: Update the startingPrice and graduation fdv formulas in
this document, plus their duplicated definitions in the frontmatter FAQ and page
FAQ, to convert raw token units to tokens and lamports to SOL before labeling
results as tokens per SOL or SOL. Keep the bonding-curve calculations unchanged
otherwise, and ensure all duplicated formulas use the same unit-consistent
definitions.
- Around line 55-57: Replace the [TBD] placeholders for virtualSol,
virtualTokens, and Graduation target in the protocol parameter table and quick
reference with the canonical values from the Genesis source, keeping the
documented units and descriptions accurate.
In `@src/pages/en/smart-contracts/genesis/index.md`:
- Line 92: Update the migrated `/api` links across the Genesis docs to use the
unified API product name instead of the Genesis-specific “Integration APIs”
label: change the link text in src/pages/en/smart-contracts/genesis/index.md at
the anchor site and in the sibling sites in
src/pages/en/smart-contracts/genesis/launch-pool.md and
src/pages/en/smart-contracts/genesis/sdk/javascript.md so they read “REST API”
or “Metaplex API” while keeping the same `/api` targets and preserving the rest
of the surrounding content.
In `@src/pages/ja/api/claim-creator-rewards.md`:
- Around line 33-50: Add a `## Quick Reference` section to the endpoint
documentation between the Summary and `## エンドポイント` sections, using a compact
table that documents the HTTP method, path, authentication requirement, response
format, and transaction-signing behavior described by the existing summary.
In `@src/pages/ja/api/fund-agent.md`:
- Around line 2-3: Translate the localized frontmatter metadata in each affected
page so the user-facing title and metaTitle are no longer left in English:
update src/pages/ja/api/fund-agent.md#L2-L3 and
src/pages/ja/api/get-agent-card.md#L2-L3 for the Japanese pages, and
src/pages/ko/api/mint-agent.md#L2-L3, src/pages/ko/api/verify-twitter.md#L2-L3,
and src/pages/ko/api/withdraw-agent.md#L2-L3 for the Korean pages; keep the
existing page body content unchanged and only replace the title/metaTitle values
in each file.
In `@src/pages/ja/api/withdraw-agent.md`:
- Line 83: Update the Japanese documentation links to use localized API routes:
in src/pages/ja/api/withdraw-agent.md lines 83-83 and 98-98, use
/ja/api/mint-agent#signing-and-submitting and /ja/api/fund-agent; in
src/pages/ja/smart-contracts/genesis/creator-fees.md lines 212-212, use
/ja/api/claim-creator-rewards; and in
src/pages/ja/smart-contracts/genesis/index.md lines 84-84, use /ja/api.
In `@src/pages/ja/smart-contracts/genesis/bonding-curve-parameters.md`:
- Line 5: Add the required created frontmatter field to the
bonding-curve-parameters documentation page, placing the creation date alongside
the existing updated field before release.
- Around line 55-57: Replace the [TBD] entries for virtualSol, virtualTokens,
and 卒業目標 in the documented parameter tables with the canonical protocol values,
including the corresponding entries at the additional graduation-calculation
section. Ensure the published starting-price and graduation formulas use those
same values consistently; if canonical values are unavailable, remove the claims
of concrete calculations instead.
In `@src/pages/ko/api/claim-creator-rewards.md`:
- Around line 39-40: Update the Korean documentation around the “오류” and HTTP
400 descriptions to use one consistent contract: state that the server returns
HTTP 400 with “No rewards available to claim” when no rewards exist, while
clients should treat this specific response as an expected no-rewards outcome
rather than an exceptional failure. Keep the claimCreatorRewards SDK wrapper
description unchanged.
- Around line 42-46: Update the sections `엔드포인트`, `요청 본문`, `요청 예시`, `성공 응답`, and
`알려진 오류 메시지` in the creator rewards claim documentation so each heading is
immediately followed by one short, direct declarative sentence before any code
block, table, or import. Keep the existing content unchanged after adding these
section-introducing sentences.
- Around line 42-50: Add the required Quick Reference table to
src/pages/ko/api/claim-creator-rewards.md at lines 42-50, covering method, path,
authentication, request, and response details. Add the corresponding Quick
Reference table to src/pages/ko/api/index.md at lines 38-42, covering base URL,
authentication, network, and specification details.
- Around line 42-70: In src/pages/ko/api/claim-creator-rewards.md lines 42-70,
add one short declarative sentence immediately under the 엔드포인트, 요청 본문, 요청 예시,
and 성공 응답 headings before their existing blocks. Apply the same heading-first
declarative-answer pattern to src/pages/ko/api/fund-agent.md lines 24-72 for
Summary, Quick Reference, endpoint, parameter, request, example, and response
sections; src/pages/ko/api/get-agent-card.md lines 32-70 for Quick Reference,
endpoint, parameter, example, response, and error sections;
src/pages/ko/api/get-agent.md lines 25-70 for Quick Reference, endpoint,
parameter, example, and response sections; src/pages/ko/api/index.md lines
28-269 for Summary, URL, endpoint, error, shared-type, and Glossary sections;
and src/pages/ko/api/list-agents.md lines 25-177 for Summary, Quick Reference,
endpoint, query, example, response, response-type, and usage sections. Make
every H2/H3 begin with a direct answer without removing or restructuring the
existing content.
In `@src/pages/ko/api/fund-agent.md`:
- Around line 2-3: Translate the Korean API page metadata consistently: update
title and metaTitle in src/pages/ko/api/fund-agent.md lines 2-3,
src/pages/ko/api/get-agent-card.md lines 2-3, src/pages/ko/api/get-agent.md
lines 2-3, and src/pages/ko/api/list-agents.md lines 2-3, and update the title
in src/pages/ko/api/index.md line 3. Translate the descriptive text into Korean
while preserving canonical names such as Metaplex API, A2A, and AgentCard.
- Around line 47-58: Translate the required-value labels in the Korean API
tables from English to consistent Korean labels: update
src/pages/ko/api/fund-agent.md lines 47-58, src/pages/ko/api/get-agent-card.md
lines 50-58, and src/pages/ko/api/get-agent.md lines 52-60 for both Yes and No;
update src/pages/ko/api/list-agents.md lines 52-62 for the optional-parameter No
labels only. No other prose or table content requires changes.
In `@src/pages/ko/api/index.md`:
- Around line 28-42: Add one concise declarative sentence immediately after each
listed H2/H3 heading in the Korean API documentation, before any bullets,
tables, or code blocks: Summary, 기본 URL, 런칭 엔드포인트, 에이전트 엔드포인트, 오류 코드, 공유 타입,
TypeScript, Rust, and Glossary. Keep the existing content unchanged and ensure
each sentence directly describes the section’s contents.
- Line 156: Make the Korean shared-types links resolve consistently by adding an
explicit shared-types anchor to the 공유 타입 section in
src/pages/ko/api/index.md:156-156; update the corresponding links in
src/pages/ko/api/get-launch.md:100-100,
src/pages/ko/api/get-launches-by-token.md:102-102,
src/pages/ko/api/get-spotlight.md:102-102, and
src/pages/ko/api/list-launches.md:105-105 only if choosing to use the generated
Korean heading slug instead, ensuring all references target the same anchor.
In `@src/pages/ko/api/list-agents.md`:
- Around line 25-70: Update the documented sections in this API page, including
the additional ranges, so every listed H2/H3 heading is immediately followed by
one direct declarative sentence before any bullets, table, or code block. Add
concise section-specific introductory sentences for Summary, Quick Reference,
엔드포인트, 쿼리 파라미터, 요청 예시, 응답, 응답 타입, TypeScript, Rust, 사용 예시, and Notes without
changing the existing content.
In `@src/pages/ko/smart-contracts/genesis/bonding-curve-parameters.md`:
- Around line 1-5: The frontmatter for the bonding-curve parameters page is
missing the required created field. Update the existing metadata block at the
top of the document to include created alongside updated, using the page’s
original publication date, and keep the current title/metaTitle/description
values unchanged.
- Around line 164-166: Update the post-graduation FAQ link in the bonding-curve
parameters documentation to target the Korean heading’s generated slug
`#졸업-후-raydium-cpmm-풀`, or add and reference an explicit stable anchor for that
heading.
- Around line 49-58: Replace the [TBD] entries for virtualSol, virtualTokens,
and the graduation target in the Genesis bonding-curve parameters table with the
fixed protocol values used by the implementation. Preserve the existing units,
Korean descriptions, formatting, and calculation references while ensuring the
values support starting-price and graduation-SOL calculations.
In `@src/pages/zh/api/claim-creator-rewards.md`:
- Around line 88-90: Update the note around the transaction submission guidance
to remove the requirement to submit transactions in order. In the callout,
instruct readers to submit all transactions returned for each claimed bucket,
while preserving the existing explanation that there are typically two
transactions.
- Around line 33-45: The endpoint reference pages lack the required Quick
Reference tables. Add a “## Quick Reference” section before “## 端点” in
src/pages/zh/api/claim-creator-rewards.md (lines 33-45) and
src/pages/zh/api/create-launch.md (lines 22-35), including method, path,
authentication, request, response, and network information.
- Around line 30-31: Prefix all listed internal links in the Chinese API pages
with /zh, preserving their existing anchors: update claim-creator-rewards.md at
lines 30-31, 40, 108, 115, and 120-124; create-launch.md at lines 22-25, 29, and
153-157; fund-agent.md at lines 85 and 98-99; get-launch.md at lines 100 and
160; and get-launches-by-token.md at line 102. Keep the localized pages
synchronized with the en, ja, and ko counterparts.
In `@src/pages/zh/api/fund-agent.md`:
- Around line 30-43: Update the documented paths in the Quick Reference and
endpoint blocks to match the executable cURL examples: use
/v1/agents/{address}/fund in src/pages/zh/api/fund-agent.md lines 30-43,
/v1/agents/{address}/agent-card.json in src/pages/zh/api/get-agent-card.md lines
32-45, and /v1/agents/{address} in src/pages/zh/api/get-agent.md lines 34-47.
Keep the existing base URL behavior unchanged.
In `@src/pages/zh/smart-contracts/genesis/bonding-curve-parameters.md`:
- Line 5: Add the missing created frontmatter field to the
bonding-curve-parameters documentation page, using the page’s creation date in
the same YYYY-MM-DD format and ordering conventions as other locale API pages.
Preserve the existing updated field and all other frontmatter.
- Around line 55-57: Replace every unresolved [TBD] value in the bonding-curve
parameters table and the referenced sections with the authoritative protocol
values for virtualSol, virtualTokens, and the graduation target. Ensure the
documented starting-price and graduation calculations use those same values
consistently.
- Line 166: Update the “毕业后费用计划” link in the bonding-curve parameters section to
use the URL fragment generated from the local heading “毕业后（Raydium CPMM 池）”
instead of the English fragment, while preserving the referenced table and
surrounding text.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: f4ba58e5-594f-4c65-9bc7-0252f8f7a34c
📒 Files selected for processing (99)
CLAUDE.mdpublic/llms.txtscripts/generate-llms-txt.mjssrc/components/products/agents/index.jssrc/components/products/api/index.jssrc/components/products/genesis/index.jssrc/components/products/index.jssrc/middleware.jssrc/pages/en/api/claim-creator-rewards.mdsrc/pages/en/api/create-launch.mdsrc/pages/en/api/fund-agent.mdsrc/pages/en/api/get-agent-card.mdsrc/pages/en/api/get-agent.mdsrc/pages/en/api/get-launch.mdsrc/pages/en/api/get-launches-by-token.mdsrc/pages/en/api/get-spotlight.mdsrc/pages/en/api/index.mdsrc/pages/en/api/list-agents.mdsrc/pages/en/api/list-launches.mdsrc/pages/en/api/mint-agent.mdsrc/pages/en/api/register.mdsrc/pages/en/api/verify-twitter.mdsrc/pages/en/api/withdraw-agent.mdsrc/pages/en/smart-contracts/genesis/bonding-curve-parameters.mdsrc/pages/en/smart-contracts/genesis/creator-fees.mdsrc/pages/en/smart-contracts/genesis/getting-started.mdsrc/pages/en/smart-contracts/genesis/index.mdsrc/pages/en/smart-contracts/genesis/launch-pool.mdsrc/pages/en/smart-contracts/genesis/sdk/javascript.mdsrc/pages/en/tokens/launch-token.mdsrc/pages/ja/api/claim-creator-rewards.mdsrc/pages/ja/api/create-launch.mdsrc/pages/ja/api/fund-agent.mdsrc/pages/ja/api/get-agent-card.mdsrc/pages/ja/api/get-agent.mdsrc/pages/ja/api/get-launch.mdsrc/pages/ja/api/get-launches-by-token.mdsrc/pages/ja/api/get-spotlight.mdsrc/pages/ja/api/index.mdsrc/pages/ja/api/list-agents.mdsrc/pages/ja/api/list-launches.mdsrc/pages/ja/api/mint-agent.mdsrc/pages/ja/api/register.mdsrc/pages/ja/api/verify-twitter.mdsrc/pages/ja/api/withdraw-agent.mdsrc/pages/ja/smart-contracts/genesis/bonding-curve-parameters.mdsrc/pages/ja/smart-contracts/genesis/creator-fees.mdsrc/pages/ja/smart-contracts/genesis/getting-started.mdsrc/pages/ja/smart-contracts/genesis/index.mdsrc/pages/ja/smart-contracts/genesis/integration-apis/index.mdsrc/pages/ja/smart-contracts/genesis/launch-pool.mdsrc/pages/ja/smart-contracts/genesis/sdk/javascript.mdsrc/pages/ja/tokens/launch-token.mdsrc/pages/ko/api/claim-creator-rewards.mdsrc/pages/ko/api/create-launch.mdsrc/pages/ko/api/fund-agent.mdsrc/pages/ko/api/get-agent-card.mdsrc/pages/ko/api/get-agent.mdsrc/pages/ko/api/get-launch.mdsrc/pages/ko/api/get-launches-by-token.mdsrc/pages/ko/api/get-spotlight.mdsrc/pages/ko/api/index.mdsrc/pages/ko/api/list-agents.mdsrc/pages/ko/api/list-launches.mdsrc/pages/ko/api/mint-agent.mdsrc/pages/ko/api/register.mdsrc/pages/ko/api/verify-twitter.mdsrc/pages/ko/api/withdraw-agent.mdsrc/pages/ko/smart-contracts/genesis/bonding-curve-parameters.mdsrc/pages/ko/smart-contracts/genesis/creator-fees.mdsrc/pages/ko/smart-contracts/genesis/getting-started.mdsrc/pages/ko/smart-contracts/genesis/index.mdsrc/pages/ko/smart-contracts/genesis/integration-apis/index.mdsrc/pages/ko/smart-contracts/genesis/launch-pool.mdsrc/pages/ko/smart-contracts/genesis/sdk/javascript.mdsrc/pages/ko/tokens/launch-token.mdsrc/pages/zh/api/claim-creator-rewards.mdsrc/pages/zh/api/create-launch.mdsrc/pages/zh/api/fund-agent.mdsrc/pages/zh/api/get-agent-card.mdsrc/pages/zh/api/get-agent.mdsrc/pages/zh/api/get-launch.mdsrc/pages/zh/api/get-launches-by-token.mdsrc/pages/zh/api/get-spotlight.mdsrc/pages/zh/api/index.mdsrc/pages/zh/api/list-agents.mdsrc/pages/zh/api/list-launches.mdsrc/pages/zh/api/mint-agent.mdsrc/pages/zh/api/register.mdsrc/pages/zh/api/verify-twitter.mdsrc/pages/zh/api/withdraw-agent.mdsrc/pages/zh/smart-contracts/genesis/bonding-curve-parameters.mdsrc/pages/zh/smart-contracts/genesis/creator-fees.mdsrc/pages/zh/smart-contracts/genesis/getting-started.mdsrc/pages/zh/smart-contracts/genesis/index.mdsrc/pages/zh/smart-contracts/genesis/integration-apis/index.mdsrc/pages/zh/smart-contracts/genesis/launch-pool.mdsrc/pages/zh/smart-contracts/genesis/sdk/javascript.mdsrc/pages/zh/tokens/launch-token.md
💤 Files with no reviewable changes (3)
- src/pages/zh/smart-contracts/genesis/integration-apis/index.md
- src/pages/ja/smart-contracts/genesis/integration-apis/index.md
- src/pages/ko/smart-contracts/genesis/integration-apis/index.md
Contributor
There was a problem hiding this comment.
Caution
Inline review comments failed to post. This is likely due to GitHub's internal server error or limits when posting large numbers of comments. If you are seeing this consistently it is likely a permissions issue. Please check "Moderation" -> "Code review limits" under your organization settings.
Actionable comments posted: 35
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/components/products/index.js`:
- Line 70: Reorder the product registry entries around api so the full registry
remains alphabetically sorted, placing api before das while preserving all
existing entries.
In `@src/pages/en/api/index.md`:
- Around line 66-98: Add the required ## Quick Reference, ## Glossary, and ##
Notes sections to the API overview, placing the endpoint summary under Quick
Reference, API terminology under Glossary, and compatibility or usage caveats
under Notes. Preserve the existing launch, agent, and transaction-building
endpoint content while organizing it beneath the appropriate section headings.
- Around line 140-145: Update the API docs table in the index page so the
canonical OpenAPI specification is labeled on the YAML entry rather than the
JSON entry. Keep the `openapi.json` row as an alternate representation, and use
the existing URL symbols (`/v1/openapi.yaml`, `/v1/openapi.json`) to make the
canonical-vs-alternate distinction explicit without changing the rest of the
table.
In `@src/pages/en/api/list-agents.md`:
- Around line 175-176: Update the agent-list response handling around
response["data"]["agents"] to check the response success status before accessing
nested data, and validate that agents is an array before reading its length.
Replace the unwrap-based access with safe handling that preserves the endpoint’s
error response behavior and avoids panics.
In `@src/pages/en/smart-contracts/genesis/bonding-curve-parameters.md`:
- Around line 2-5: Add the required created frontmatter field alongside updated
in the Bonding Curve Protocol Parameters page, using the page’s creation date
while preserving the existing metadata values.
- Around line 47-58: Update the Genesis product configuration in the Bonding
Curve navigation within src/components/products/genesis/index.js to add a
“Protocol Parameters” child linking to
/smart-contracts/genesis/bonding-curve-parameters. Preserve the existing
navigation structure and labels.
- Around line 47-58: Add a concise declarative summary sentence immediately
after each of the Protocol Parameters, Fee Schedule, Starting Price, and
Constant Product Invariant headings, before their existing tables, nested
headings, or code blocks; ensure each sentence directly states the section’s key
answer and leave the supporting structures unchanged.
- Around line 83-88: Update the post-bond fee values in the bonding-curve
parameters page to match the postBondTrading constants: use 0.21% for LP fees
and 0.04% for the Raydium fee. Apply the same values consistently in the FAQ
answer and Quick Reference table.
- Around line 96-110: Update the startingPrice and graduation fdv formulas in
this document, plus their duplicated definitions in the frontmatter FAQ and page
FAQ, to convert raw token units to tokens and lamports to SOL before labeling
results as tokens per SOL or SOL. Keep the bonding-curve calculations unchanged
otherwise, and ensure all duplicated formulas use the same unit-consistent
definitions.
- Around line 55-57: Replace the [TBD] placeholders for virtualSol,
virtualTokens, and Graduation target in the protocol parameter table and quick
reference with the canonical values from the Genesis source, keeping the
documented units and descriptions accurate.
In `@src/pages/en/smart-contracts/genesis/index.md`:
- Line 92: Update the migrated `/api` links across the Genesis docs to use the
unified API product name instead of the Genesis-specific “Integration APIs”
label: change the link text in src/pages/en/smart-contracts/genesis/index.md at
the anchor site and in the sibling sites in
src/pages/en/smart-contracts/genesis/launch-pool.md and
src/pages/en/smart-contracts/genesis/sdk/javascript.md so they read “REST API”
or “Metaplex API” while keeping the same `/api` targets and preserving the rest
of the surrounding content.
In `@src/pages/ja/api/claim-creator-rewards.md`:
- Around line 33-50: Add a `## Quick Reference` section to the endpoint
documentation between the Summary and `## エンドポイント` sections, using a compact
table that documents the HTTP method, path, authentication requirement, response
format, and transaction-signing behavior described by the existing summary.
In `@src/pages/ja/api/fund-agent.md`:
- Around line 2-3: Translate the localized frontmatter metadata in each affected
page so the user-facing title and metaTitle are no longer left in English:
update src/pages/ja/api/fund-agent.md#L2-L3 and
src/pages/ja/api/get-agent-card.md#L2-L3 for the Japanese pages, and
src/pages/ko/api/mint-agent.md#L2-L3, src/pages/ko/api/verify-twitter.md#L2-L3,
and src/pages/ko/api/withdraw-agent.md#L2-L3 for the Korean pages; keep the
existing page body content unchanged and only replace the title/metaTitle values
in each file.
In `@src/pages/ja/api/withdraw-agent.md`:
- Line 83: Update the Japanese documentation links to use localized API routes:
in src/pages/ja/api/withdraw-agent.md lines 83-83 and 98-98, use
/ja/api/mint-agent#signing-and-submitting and /ja/api/fund-agent; in
src/pages/ja/smart-contracts/genesis/creator-fees.md lines 212-212, use
/ja/api/claim-creator-rewards; and in
src/pages/ja/smart-contracts/genesis/index.md lines 84-84, use /ja/api.
In `@src/pages/ja/smart-contracts/genesis/bonding-curve-parameters.md`:
- Line 5: Add the required created frontmatter field to the
bonding-curve-parameters documentation page, placing the creation date alongside
the existing updated field before release.
- Around line 55-57: Replace the [TBD] entries for virtualSol, virtualTokens,
and 卒業目標 in the documented parameter tables with the canonical protocol values,
including the corresponding entries at the additional graduation-calculation
section. Ensure the published starting-price and graduation formulas use those
same values consistently; if canonical values are unavailable, remove the claims
of concrete calculations instead.
In `@src/pages/ko/api/claim-creator-rewards.md`:
- Around line 39-40: Update the Korean documentation around the “오류” and HTTP
400 descriptions to use one consistent contract: state that the server returns
HTTP 400 with “No rewards available to claim” when no rewards exist, while
clients should treat this specific response as an expected no-rewards outcome
rather than an exceptional failure. Keep the claimCreatorRewards SDK wrapper
description unchanged.
- Around line 42-46: Update the sections `엔드포인트`, `요청 본문`, `요청 예시`, `성공 응답`, and
`알려진 오류 메시지` in the creator rewards claim documentation so each heading is
immediately followed by one short, direct declarative sentence before any code
block, table, or import. Keep the existing content unchanged after adding these
section-introducing sentences.
- Around line 42-50: Add the required Quick Reference table to
src/pages/ko/api/claim-creator-rewards.md at lines 42-50, covering method, path,
authentication, request, and response details. Add the corresponding Quick
Reference table to src/pages/ko/api/index.md at lines 38-42, covering base URL,
authentication, network, and specification details.
- Around line 42-70: In src/pages/ko/api/claim-creator-rewards.md lines 42-70,
add one short declarative sentence immediately under the 엔드포인트, 요청 본문, 요청 예시,
and 성공 응답 headings before their existing blocks. Apply the same heading-first
declarative-answer pattern to src/pages/ko/api/fund-agent.md lines 24-72 for
Summary, Quick Reference, endpoint, parameter, request, example, and response
sections; src/pages/ko/api/get-agent-card.md lines 32-70 for Quick Reference,
endpoint, parameter, example, response, and error sections;
src/pages/ko/api/get-agent.md lines 25-70 for Quick Reference, endpoint,
parameter, example, and response sections; src/pages/ko/api/index.md lines
28-269 for Summary, URL, endpoint, error, shared-type, and Glossary sections;
and src/pages/ko/api/list-agents.md lines 25-177 for Summary, Quick Reference,
endpoint, query, example, response, response-type, and usage sections. Make
every H2/H3 begin with a direct answer without removing or restructuring the
existing content.
In `@src/pages/ko/api/fund-agent.md`:
- Around line 2-3: Translate the Korean API page metadata consistently: update
title and metaTitle in src/pages/ko/api/fund-agent.md lines 2-3,
src/pages/ko/api/get-agent-card.md lines 2-3, src/pages/ko/api/get-agent.md
lines 2-3, and src/pages/ko/api/list-agents.md lines 2-3, and update the title
in src/pages/ko/api/index.md line 3. Translate the descriptive text into Korean
while preserving canonical names such as Metaplex API, A2A, and AgentCard.
- Around line 47-58: Translate the required-value labels in the Korean API
tables from English to consistent Korean labels: update
src/pages/ko/api/fund-agent.md lines 47-58, src/pages/ko/api/get-agent-card.md
lines 50-58, and src/pages/ko/api/get-agent.md lines 52-60 for both Yes and No;
update src/pages/ko/api/list-agents.md lines 52-62 for the optional-parameter No
labels only. No other prose or table content requires changes.
In `@src/pages/ko/api/index.md`:
- Around line 28-42: Add one concise declarative sentence immediately after each
listed H2/H3 heading in the Korean API documentation, before any bullets,
tables, or code blocks: Summary, 기본 URL, 런칭 엔드포인트, 에이전트 엔드포인트, 오류 코드, 공유 타입,
TypeScript, Rust, and Glossary. Keep the existing content unchanged and ensure
each sentence directly describes the section’s contents.
- Line 156: Make the Korean shared-types links resolve consistently by adding an
explicit shared-types anchor to the 공유 타입 section in
src/pages/ko/api/index.md:156-156; update the corresponding links in
src/pages/ko/api/get-launch.md:100-100,
src/pages/ko/api/get-launches-by-token.md:102-102,
src/pages/ko/api/get-spotlight.md:102-102, and
src/pages/ko/api/list-launches.md:105-105 only if choosing to use the generated
Korean heading slug instead, ensuring all references target the same anchor.
In `@src/pages/ko/api/list-agents.md`:
- Around line 25-70: Update the documented sections in this API page, including
the additional ranges, so every listed H2/H3 heading is immediately followed by
one direct declarative sentence before any bullets, table, or code block. Add
concise section-specific introductory sentences for Summary, Quick Reference,
엔드포인트, 쿼리 파라미터, 요청 예시, 응답, 응답 타입, TypeScript, Rust, 사용 예시, and Notes without
changing the existing content.
In `@src/pages/ko/smart-contracts/genesis/bonding-curve-parameters.md`:
- Around line 1-5: The frontmatter for the bonding-curve parameters page is
missing the required created field. Update the existing metadata block at the
top of the document to include created alongside updated, using the page’s
original publication date, and keep the current title/metaTitle/description
values unchanged.
- Around line 164-166: Update the post-graduation FAQ link in the bonding-curve
parameters documentation to target the Korean heading’s generated slug
`#졸업-후-raydium-cpmm-풀`, or add and reference an explicit stable anchor for that
heading.
- Around line 49-58: Replace the [TBD] entries for virtualSol, virtualTokens,
and the graduation target in the Genesis bonding-curve parameters table with the
fixed protocol values used by the implementation. Preserve the existing units,
Korean descriptions, formatting, and calculation references while ensuring the
values support starting-price and graduation-SOL calculations.
In `@src/pages/zh/api/claim-creator-rewards.md`:
- Around line 88-90: Update the note around the transaction submission guidance
to remove the requirement to submit transactions in order. In the callout,
instruct readers to submit all transactions returned for each claimed bucket,
while preserving the existing explanation that there are typically two
transactions.
- Around line 33-45: The endpoint reference pages lack the required Quick
Reference tables. Add a “## Quick Reference” section before “## 端点” in
src/pages/zh/api/claim-creator-rewards.md (lines 33-45) and
src/pages/zh/api/create-launch.md (lines 22-35), including method, path,
authentication, request, response, and network information.
- Around line 30-31: Prefix all listed internal links in the Chinese API pages
with /zh, preserving their existing anchors: update claim-creator-rewards.md at
lines 30-31, 40, 108, 115, and 120-124; create-launch.md at lines 22-25, 29, and
153-157; fund-agent.md at lines 85 and 98-99; get-launch.md at lines 100 and
160; and get-launches-by-token.md at line 102. Keep the localized pages
synchronized with the en, ja, and ko counterparts.
In `@src/pages/zh/api/fund-agent.md`:
- Around line 30-43: Update the documented paths in the Quick Reference and
endpoint blocks to match the executable cURL examples: use
/v1/agents/{address}/fund in src/pages/zh/api/fund-agent.md lines 30-43,
/v1/agents/{address}/agent-card.json in src/pages/zh/api/get-agent-card.md lines
32-45, and /v1/agents/{address} in src/pages/zh/api/get-agent.md lines 34-47.
Keep the existing base URL behavior unchanged.
In `@src/pages/zh/smart-contracts/genesis/bonding-curve-parameters.md`:
- Line 5: Add the missing created frontmatter field to the
bonding-curve-parameters documentation page, using the page’s creation date in
the same YYYY-MM-DD format and ordering conventions as other locale API pages.
Preserve the existing updated field and all other frontmatter.
- Around line 55-57: Replace every unresolved [TBD] value in the bonding-curve
parameters table and the referenced sections with the authoritative protocol
values for virtualSol, virtualTokens, and the graduation target. Ensure the
documented starting-price and graduation calculations use those same values
consistently.
- Line 166: Update the “毕业后费用计划” link in the bonding-curve parameters section to
use the URL fragment generated from the local heading “毕业后（Raydium CPMM 池）”
instead of the English fragment, while preserving the referenced table and
surrounding text.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: f4ba58e5-594f-4c65-9bc7-0252f8f7a34c
📒 Files selected for processing (99)
CLAUDE.mdpublic/llms.txtscripts/generate-llms-txt.mjssrc/components/products/agents/index.jssrc/components/products/api/index.jssrc/components/products/genesis/index.jssrc/components/products/index.jssrc/middleware.jssrc/pages/en/api/claim-creator-rewards.mdsrc/pages/en/api/create-launch.mdsrc/pages/en/api/fund-agent.mdsrc/pages/en/api/get-agent-card.mdsrc/pages/en/api/get-agent.mdsrc/pages/en/api/get-launch.mdsrc/pages/en/api/get-launches-by-token.mdsrc/pages/en/api/get-spotlight.mdsrc/pages/en/api/index.mdsrc/pages/en/api/list-agents.mdsrc/pages/en/api/list-launches.mdsrc/pages/en/api/mint-agent.mdsrc/pages/en/api/register.mdsrc/pages/en/api/verify-twitter.mdsrc/pages/en/api/withdraw-agent.mdsrc/pages/en/smart-contracts/genesis/bonding-curve-parameters.mdsrc/pages/en/smart-contracts/genesis/creator-fees.mdsrc/pages/en/smart-contracts/genesis/getting-started.mdsrc/pages/en/smart-contracts/genesis/index.mdsrc/pages/en/smart-contracts/genesis/launch-pool.mdsrc/pages/en/smart-contracts/genesis/sdk/javascript.mdsrc/pages/en/tokens/launch-token.mdsrc/pages/ja/api/claim-creator-rewards.mdsrc/pages/ja/api/create-launch.mdsrc/pages/ja/api/fund-agent.mdsrc/pages/ja/api/get-agent-card.mdsrc/pages/ja/api/get-agent.mdsrc/pages/ja/api/get-launch.mdsrc/pages/ja/api/get-launches-by-token.mdsrc/pages/ja/api/get-spotlight.mdsrc/pages/ja/api/index.mdsrc/pages/ja/api/list-agents.mdsrc/pages/ja/api/list-launches.mdsrc/pages/ja/api/mint-agent.mdsrc/pages/ja/api/register.mdsrc/pages/ja/api/verify-twitter.mdsrc/pages/ja/api/withdraw-agent.mdsrc/pages/ja/smart-contracts/genesis/bonding-curve-parameters.mdsrc/pages/ja/smart-contracts/genesis/creator-fees.mdsrc/pages/ja/smart-contracts/genesis/getting-started.mdsrc/pages/ja/smart-contracts/genesis/index.mdsrc/pages/ja/smart-contracts/genesis/integration-apis/index.mdsrc/pages/ja/smart-contracts/genesis/launch-pool.mdsrc/pages/ja/smart-contracts/genesis/sdk/javascript.mdsrc/pages/ja/tokens/launch-token.mdsrc/pages/ko/api/claim-creator-rewards.mdsrc/pages/ko/api/create-launch.mdsrc/pages/ko/api/fund-agent.mdsrc/pages/ko/api/get-agent-card.mdsrc/pages/ko/api/get-agent.mdsrc/pages/ko/api/get-launch.mdsrc/pages/ko/api/get-launches-by-token.mdsrc/pages/ko/api/get-spotlight.mdsrc/pages/ko/api/index.mdsrc/pages/ko/api/list-agents.mdsrc/pages/ko/api/list-launches.mdsrc/pages/ko/api/mint-agent.mdsrc/pages/ko/api/register.mdsrc/pages/ko/api/verify-twitter.mdsrc/pages/ko/api/withdraw-agent.mdsrc/pages/ko/smart-contracts/genesis/bonding-curve-parameters.mdsrc/pages/ko/smart-contracts/genesis/creator-fees.mdsrc/pages/ko/smart-contracts/genesis/getting-started.mdsrc/pages/ko/smart-contracts/genesis/index.mdsrc/pages/ko/smart-contracts/genesis/integration-apis/index.mdsrc/pages/ko/smart-contracts/genesis/launch-pool.mdsrc/pages/ko/smart-contracts/genesis/sdk/javascript.mdsrc/pages/ko/tokens/launch-token.mdsrc/pages/zh/api/claim-creator-rewards.mdsrc/pages/zh/api/create-launch.mdsrc/pages/zh/api/fund-agent.mdsrc/pages/zh/api/get-agent-card.mdsrc/pages/zh/api/get-agent.mdsrc/pages/zh/api/get-launch.mdsrc/pages/zh/api/get-launches-by-token.mdsrc/pages/zh/api/get-spotlight.mdsrc/pages/zh/api/index.mdsrc/pages/zh/api/list-agents.mdsrc/pages/zh/api/list-launches.mdsrc/pages/zh/api/mint-agent.mdsrc/pages/zh/api/register.mdsrc/pages/zh/api/verify-twitter.mdsrc/pages/zh/api/withdraw-agent.mdsrc/pages/zh/smart-contracts/genesis/bonding-curve-parameters.mdsrc/pages/zh/smart-contracts/genesis/creator-fees.mdsrc/pages/zh/smart-contracts/genesis/getting-started.mdsrc/pages/zh/smart-contracts/genesis/index.mdsrc/pages/zh/smart-contracts/genesis/integration-apis/index.mdsrc/pages/zh/smart-contracts/genesis/launch-pool.mdsrc/pages/zh/smart-contracts/genesis/sdk/javascript.mdsrc/pages/zh/tokens/launch-token.md
💤 Files with no reviewable changes (3)
- src/pages/zh/smart-contracts/genesis/integration-apis/index.md
- src/pages/ja/smart-contracts/genesis/integration-apis/index.md
- src/pages/ko/smart-contracts/genesis/integration-apis/index.md
🛑 Comments failed to post (8)
src/pages/ja/api/claim-creator-rewards.md (1)
33-50: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Add the required
## Quick Referencetable.This endpoint reference has a Summary section but no Quick Reference section. Add a compact table for the method, path, authentication, response, and signing behavior.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/pages/ja/api/claim-creator-rewards.md` around lines 33 - 50, Add a `## Quick Reference` section to the endpoint documentation between the Summary and `## エンドポイント` sections, using a compact table that documents the HTTP method, path, authentication requirement, response format, and transaction-signing behavior described by the existing summary.Source: Coding guidelines
src/pages/ko/api/claim-creator-rewards.md (4)
39-40: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Use one error-handling contract.
Line [39] says callers should branch to an error. Lines [104] and [108] say the HTTP
400response is an expected, non-exceptional “nothing to do” case. State that the server returns HTTP400, while clients should handle this specific response as an expected no-rewards outcome.Also applies to: 104-108
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/pages/ko/api/claim-creator-rewards.md` around lines 39 - 40, Update the Korean documentation around the “오류” and HTTP 400 descriptions to use one consistent contract: state that the server returns HTTP 400 with “No rewards available to claim” when no rewards exist, while clients should treat this specific response as an expected no-rewards outcome rather than an exceptional failure. Keep the claimCreatorRewards SDK wrapper description unchanged.
42-46: 📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Add a declarative sentence after each section heading.
Several sections start with a code block, table, or Markdoc import instead of a direct declarative sentence. Add one short sentence under
## 엔드포인트,## 요청 본문,## 요청 예시,## 성공 응답, and### 알려진 오류 메시지.As per coding guidelines, every H2/H3 must start with a direct declarative answer.
Also applies to: 52-66, 68-70, 100-104
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/pages/ko/api/claim-creator-rewards.md` around lines 42 - 46, Update the sections `엔드포인트`, `요청 본문`, `요청 예시`, `성공 응답`, and `알려진 오류 메시지` in the creator rewards claim documentation so each heading is immediately followed by one short, direct declarative sentence before any code block, table, or import. Keep the existing content unchanged after adding these section-introducing sentences.Source: Coding guidelines
42-50: 📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Add Quick Reference tables to the two page types.
Both pages omit the required Quick Reference section.
src/pages/ko/api/claim-creator-rewards.md#L42-L50: add method, path, authentication, request, and response details.src/pages/ko/api/index.md#L38-L42: add base URL, authentication, network, and specification details.As per coding guidelines, Reference and Overview pages must include Quick Reference tables.
📍 Affects 2 files
src/pages/ko/api/claim-creator-rewards.md#L42-L50(this comment)src/pages/ko/api/index.md#L38-L42🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/pages/ko/api/claim-creator-rewards.md` around lines 42 - 50, Add the required Quick Reference table to src/pages/ko/api/claim-creator-rewards.md at lines 42-50, covering method, path, authentication, request, and response details. Add the corresponding Quick Reference table to src/pages/ko/api/index.md at lines 38-42, covering base URL, authentication, network, and specification details.Source: Coding guidelines
42-70: 📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Add direct declarative answers under documentation headings.
These pages place bullets, tables, code blocks, or imports immediately after several H2/H3 headings. Add one short declarative sentence before each block.
src/pages/ko/api/claim-creator-rewards.md#L42-L70: add sentences under## 엔드포인트,## 요청 본문,## 요청 예시, and## 성공 응답.src/pages/ko/api/fund-agent.md#L24-L72: add sentences under the Summary, Quick Reference, endpoint, parameter, request, example, and response sections.src/pages/ko/api/get-agent-card.md#L32-L70: add sentences under the Quick Reference, endpoint, parameter, example, response, and error sections.src/pages/ko/api/get-agent.md#L25-L70: add sentences under the Quick Reference, endpoint, parameter, example, and response sections.src/pages/ko/api/index.md#L28-L269: add sentences under the Summary, URL, endpoint, error, shared-type, and Glossary sections.src/pages/ko/api/list-agents.md#L25-L177: add sentences under the Summary, Quick Reference, endpoint, query, example, response, response-type, and usage sections.As per coding guidelines, every H2/H3 must start with a direct declarative answer.
📍 Affects 6 files
src/pages/ko/api/claim-creator-rewards.md#L42-L70(this comment)src/pages/ko/api/fund-agent.md#L24-L72src/pages/ko/api/get-agent-card.md#L32-L70src/pages/ko/api/get-agent.md#L25-L70src/pages/ko/api/index.md#L28-L269src/pages/ko/api/list-agents.md#L25-L177🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/pages/ko/api/claim-creator-rewards.md` around lines 42 - 70, In src/pages/ko/api/claim-creator-rewards.md lines 42-70, add one short declarative sentence immediately under the 엔드포인트, 요청 본문, 요청 예시, and 성공 응답 headings before their existing blocks. Apply the same heading-first declarative-answer pattern to src/pages/ko/api/fund-agent.md lines 24-72 for Summary, Quick Reference, endpoint, parameter, request, example, and response sections; src/pages/ko/api/get-agent-card.md lines 32-70 for Quick Reference, endpoint, parameter, example, response, and error sections; src/pages/ko/api/get-agent.md lines 25-70 for Quick Reference, endpoint, parameter, example, and response sections; src/pages/ko/api/index.md lines 28-269 for Summary, URL, endpoint, error, shared-type, and Glossary sections; and src/pages/ko/api/list-agents.md lines 25-177 for Summary, Quick Reference, endpoint, query, example, response, response-type, and usage sections. Make every H2/H3 begin with a direct answer without removing or restructuring the existing content.Source: Coding guidelines
src/pages/zh/api/claim-creator-rewards.md (3)
30-31: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Keep internal links locale-prefixed in Chinese pages.
The listed links omit
/zh, while the pages are under/zh. Prefix each internal target with/zhso Chinese readers do not leave the localized documentation.
src/pages/zh/api/claim-creator-rewards.md#L30-L31: prefix the SDK and Umi links, and apply the same fix to Lines 40, 108, 115, and 120-124.src/pages/zh/api/create-launch.md#L22-L25: prefix/api/registerand the SDK link, and apply the same fix to Line 29 and Lines 153-157.src/pages/zh/api/fund-agent.md#L85-L85: prefix the signing link, and apply the same fix to Lines 98-99.src/pages/zh/api/get-launch.md#L100-L100: change/api#shared-typesto/zh/api#shared-types, and apply the same fix to Line 160.src/pages/zh/api/get-launches-by-token.md#L102-L102: change/api#shared-typesto/zh/api#shared-types.As per coding guidelines, localized pages must remain synchronized across the
en,ja,ko, andzhlocale directories.📍 Affects 5 files
src/pages/zh/api/claim-creator-rewards.md#L30-L31(this comment)src/pages/zh/api/create-launch.md#L22-L25src/pages/zh/api/fund-agent.md#L85-L85src/pages/zh/api/get-launch.md#L100-L100src/pages/zh/api/get-launches-by-token.md#L102-L102🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/pages/zh/api/claim-creator-rewards.md` around lines 30 - 31, Prefix all listed internal links in the Chinese API pages with /zh, preserving their existing anchors: update claim-creator-rewards.md at lines 30-31, 40, 108, 115, and 120-124; create-launch.md at lines 22-25, 29, and 153-157; fund-agent.md at lines 85 and 98-99; get-launch.md at lines 100 and 160; and get-launches-by-token.md at line 102. Keep the localized pages synchronized with the en, ja, and ko counterparts.Source: Coding guidelines
33-45: 📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Add the required Quick Reference table to each endpoint reference.
Both pages move from introductory content directly to endpoint details. Add method, path, authentication, request, response, and network information before the endpoint section.
src/pages/zh/api/claim-creator-rewards.md#L33-L45: add## Quick Referencebefore## 端点.src/pages/zh/api/create-launch.md#L22-L35: add## Quick Referencebefore## 端点.As per coding guidelines, Reference pages must include a Quick Reference table.
📍 Affects 2 files
src/pages/zh/api/claim-creator-rewards.md#L33-L45(this comment)src/pages/zh/api/create-launch.md#L22-L35🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/pages/zh/api/claim-creator-rewards.md` around lines 33 - 45, The endpoint reference pages lack the required Quick Reference tables. Add a “## Quick Reference” section before “## 端点” in src/pages/zh/api/claim-creator-rewards.md (lines 33-45) and src/pages/zh/api/create-launch.md (lines 22-35), including method, path, authentication, request, response, and network information.Source: Coding guidelines
88-90: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Make the transaction submission guidance consistent.
The note says to submit transactions in order and then says that order does not matter. If order is irrelevant, instruct readers to submit all returned transactions without requiring a specific order.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/pages/zh/api/claim-creator-rewards.md` around lines 88 - 90, Update the note around the transaction submission guidance to remove the requirement to submit transactions in order. In the callout, instruct readers to submit all transactions returned for each claimed bucket, while preserving the existing explanation that there are typically two transactions.
…urve parameters - Label the YAML OpenAPI spec as canonical (JSON as alternate) in all locales - Fix post-graduation fee split to match protocol values (0.21% LP / 0.04% Raydium) - Make starting-price and graduation formulas unit-consistent (raw units/lamports vs tokens/SOL) - Add created/corrected updated dates on bonding-curve-parameters pages - Register Protocol Parameters page in the Genesis sidebar nav - Add BLUF lead sentences to bonding-curve-parameters sections and API index Summary - Harden list-agents Rust example against error responses - Localize all /api links in ja/ko/zh pages and add explicit anchors on CJK headings - Translate remaining English titles/metaTitles on ja/ko/zh API pages - Translate Yes/No table cells on ko API pages - Rename 'Integration APIs' link labels to 'Metaplex API'
Contributor
There was a problem hiding this comment.
Actionable comments posted: 9
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/components/products/genesis/index.js`:
- Around line 129-132: Update the localized Genesis link maps used by usePage.js
to add the Protocol Parameters/Bonding Curve navigation key with Japanese,
Korean, and Chinese translations; leave the existing English entry unchanged and
preserve the current link key so localized menus resolve the translated title.
In `@src/pages/en/smart-contracts/genesis/sdk/javascript.md`:
- Line 396: Update the two JavaScript markdown passages that mention the
Metaplex API so the verb agrees with the singular subject, changing the phrasing
in the affected text blocks around the API reference to use “returns” instead of
“return.” Keep the rest of the sentence content and the on-chain SDK comparison
unchanged.
In `@src/pages/ja/api/withdraw-agent.md`:
- Line 98: Translate the user-facing “Fund Agent” link label at
src/pages/ja/api/withdraw-agent.md:98-98 into Japanese while preserving the
/ja/api/fund-agent route. Also translate the “Withdraw” link label at
src/pages/ko/api/fund-agent.md:98-98 into Korean while preserving its localized
route.
In `@src/pages/ja/smart-contracts/genesis/index.md`:
- Line 84: Update the SDK link in
src/pages/ja/smart-contracts/genesis/index.md:84 to
/ja/smart-contracts/genesis/sdk/javascript#genesis-account. Check for localized
api-client pages and, if present, update the links in
src/pages/ja/api/create-launch.md:25 to use /ja/ and
src/pages/ko/api/create-launch.md:25 to use /ko/; otherwise leave those links
unchanged.
In `@src/pages/ja/smart-contracts/genesis/sdk/javascript.md`:
- Line 479: Update the Japanese docs link in the Genesis SDK section so the GPA
builder reference points to an explicit anchor instead of the auto-generated CJK
slug. Add a stable anchor to the heading for the GPA builder query section in
the same document, and change the link text target in this paragraph to use that
anchor; keep the existing section content and wording otherwise unchanged.
In `@src/pages/ko/smart-contracts/genesis/creator-fees.md`:
- Line 212: Update the transaction-confirmation warning in the SDK response
guidance to clearly state that fetching a new blockhash can cause a race
condition during transaction confirmation, replacing the awkward “그렇지 않으면 확인이
경합합니다” wording while preserving the instruction to confirm each transaction with
the returned blockhash.
In `@src/pages/ko/smart-contracts/genesis/sdk/javascript.md`:
- Line 475: Update the Korean docs section around the “GPA 빌더 — 런칭 타입으로 조회”
heading so it has an explicit ASCII Markdoc anchor. Then change the inline link
in the `fetchGenesisAccountV2FromSeeds()` paragraph to point to that anchor
instead of relying on the localized slug. Keep the existing heading text and
surrounding content unchanged.
In `@src/pages/zh/api/get-launch.md`:
- Line 3: Update the page’s metaTitle value to use “Metaplex API” instead of
“Genesis,” while preserving the existing localized title text and metadata
format.
In `@src/pages/zh/api/get-launches-by-token.md`:
- Around line 2-3: Update the metaTitle in
src/pages/zh/api/get-launches-by-token.md lines 2-3 to use the canonical
“Metaplex API” name instead of “Genesis,” while preserving the Chinese localized
text. Apply the same metaTitle change in src/pages/zh/api/get-spotlight.md lines
2-3, replacing “Genesis” with “Metaplex API” and leaving the translated title
unchanged.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: b3d06327-f39f-4c78-a064-e6ed0c03f2c9
📒 Files selected for processing (72)
src/components/MobileNavigation.jsxsrc/components/NavList.jsxsrc/components/products/genesis/index.jssrc/locales/en.jsonsrc/locales/ja.jsonsrc/locales/ko.jsonsrc/locales/zh.jsonsrc/pages/en/api/index.mdsrc/pages/en/api/list-agents.mdsrc/pages/en/smart-contracts/genesis/bonding-curve-parameters.mdsrc/pages/en/smart-contracts/genesis/index.mdsrc/pages/en/smart-contracts/genesis/launch-pool.mdsrc/pages/en/smart-contracts/genesis/sdk/javascript.mdsrc/pages/en/tokens/launch-token.mdsrc/pages/ja/api/create-launch.mdsrc/pages/ja/api/fund-agent.mdsrc/pages/ja/api/get-agent-card.mdsrc/pages/ja/api/get-agent.mdsrc/pages/ja/api/get-launch.mdsrc/pages/ja/api/get-launches-by-token.mdsrc/pages/ja/api/get-spotlight.mdsrc/pages/ja/api/index.mdsrc/pages/ja/api/list-agents.mdsrc/pages/ja/api/list-launches.mdsrc/pages/ja/api/mint-agent.mdsrc/pages/ja/api/register.mdsrc/pages/ja/api/verify-twitter.mdsrc/pages/ja/api/withdraw-agent.mdsrc/pages/ja/smart-contracts/genesis/bonding-curve-parameters.mdsrc/pages/ja/smart-contracts/genesis/creator-fees.mdsrc/pages/ja/smart-contracts/genesis/index.mdsrc/pages/ja/smart-contracts/genesis/launch-pool.mdsrc/pages/ja/smart-contracts/genesis/sdk/javascript.mdsrc/pages/ja/tokens/launch-token.mdsrc/pages/ko/api/create-launch.mdsrc/pages/ko/api/fund-agent.mdsrc/pages/ko/api/get-agent-card.mdsrc/pages/ko/api/get-agent.mdsrc/pages/ko/api/get-launch.mdsrc/pages/ko/api/get-launches-by-token.mdsrc/pages/ko/api/get-spotlight.mdsrc/pages/ko/api/index.mdsrc/pages/ko/api/list-agents.mdsrc/pages/ko/api/list-launches.mdsrc/pages/ko/api/mint-agent.mdsrc/pages/ko/api/register.mdsrc/pages/ko/api/verify-twitter.mdsrc/pages/ko/api/withdraw-agent.mdsrc/pages/ko/smart-contracts/genesis/bonding-curve-parameters.mdsrc/pages/ko/smart-contracts/genesis/creator-fees.mdsrc/pages/ko/smart-contracts/genesis/index.mdsrc/pages/ko/smart-contracts/genesis/launch-pool.mdsrc/pages/ko/smart-contracts/genesis/sdk/javascript.mdsrc/pages/ko/tokens/launch-token.mdsrc/pages/zh/api/create-launch.mdsrc/pages/zh/api/fund-agent.mdsrc/pages/zh/api/get-launch.mdsrc/pages/zh/api/get-launches-by-token.mdsrc/pages/zh/api/get-spotlight.mdsrc/pages/zh/api/index.mdsrc/pages/zh/api/list-agents.mdsrc/pages/zh/api/list-launches.mdsrc/pages/zh/api/mint-agent.mdsrc/pages/zh/api/register.mdsrc/pages/zh/api/verify-twitter.mdsrc/pages/zh/api/withdraw-agent.mdsrc/pages/zh/smart-contracts/genesis/bonding-curve-parameters.mdsrc/pages/zh/smart-contracts/genesis/creator-fees.mdsrc/pages/zh/smart-contracts/genesis/index.mdsrc/pages/zh/smart-contracts/genesis/launch-pool.mdsrc/pages/zh/smart-contracts/genesis/sdk/javascript.mdsrc/pages/zh/tokens/launch-token.md
- Add Protocol Parameters to localized Genesis nav link maps (en/ja/ko/zh) - Fix verb agreement after Integration APIs -> Metaplex API rename - Replace broken CJK/double-hyphen GPA builder fragments with explicit anchors - Translate remaining English link labels in ja/ko API page prose - Localize remaining internal links in ja/ko/zh API pages and genesis index - Use Metaplex API product name in launch-endpoint metaTitles (21 locale files) - Add stable anchor for the no-rewards case in locale creator-fees pages - Clarify ko transaction-confirmation race condition wording
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
1 participant
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.
Moves everything to a generic /api page (with corrected routing to mitigate nextjs default /api routing) since metaplex.com isn't 'genesis' anymore it's more generic.
Moving these out provides a generic metaplex.com/docs/api page where we can just put everything API related for metaplex.com