Ai bankofai patch 1 - #40
Conversation
Server url fix
bug fix
fix baseurl
Code Review ReportProject: BofAI Documentation (Docusaurus) PR OverviewBranch Information
Commit History (Recent)
Review SummaryVerdict
Findings at a Glance
SummaryThis PR is a documentation-only update covering four logical areas: a substantial API reference rewrite, new Memory Service documentation, model renaming (ChatGPT-5.x → GPT-5.x) with three new GPT-5.4 model pages, and pricing/sidebar updates. The overall quality is good — the restructured API reference is significantly more developer-friendly with inline request/response examples, and the new model pages are thorough. However, three major correctness issues require fixes before merge: a pricing calculation example in the English docs uses stale per-token rates that produce a wrong credit total; a pricing number within the same GPT-5.4 Nano file is internally self-contradictory; and the API base URL domain change ( Five minor issues also need attention: missing top-level H1 page titles in six model/pricing files (breaking Docusaurus page rendering), trailing whitespace in sidebar config files, a broken/incomplete pricing link sentence, and inconsistent pricing unit notation across files. Change SummaryGroup 1 — API Reference Overhaul
Purpose: Improve developer experience by replacing terse schema-table references with concrete request/response JSON examples, and expand the Messages endpoint docs with full Claude-compatible field documentation. Group 2 — Memory Service Documentation (New)
Purpose: Document a new Memory persistence feature that gives agents long-term context across sessions. Group 3 — Model Renaming & New GPT-5.4 Pages
Purpose: Rebrand GPT-5.x models from "ChatGPT-5.x" to "GPT-5.x" naming and document three new GPT-5.4 variants released in March 2026. Group 4 — Pricing & Usage Update
Purpose: Reflect new model offerings (GPT-5.4 variants, MiniMax-M2.5, Kimi-K2.5, GLM-5), update deposit language to TRON/TronLink specifics, and improve readability. Detailed FindingsMajor[MJ-01] Pricing Calculation Example Uses Wrong Input/Output Rates (EN)
Description The English pricing calculation example references GPT-5.2 but uses per-token rates that no longer exist in the pricing table. The table correctly lists GPT-5.2 at 1.75 input / 14.00 output, but the example formula uses Notably, the Chinese (i18n) version of this same file was updated correctly to 717.5 credits using 1.75/14 rates, making this an English-only regression that creates a factual inconsistency between the two language editions. Code For example, if you use GPT-5.2 to ask a question (10 input tokens) and the AI responds with
an answer (50 output tokens), the entire dialogue consumes 512.5 credits
(calculated as: 10 × 1.25 + 50 × 10).Recommendation For example, if you use GPT-5.2 to ask a question (10 input tokens) and the AI responds with
an answer (50 output tokens), the entire dialogue consumes 717.5 credits
(calculated as: 10 × 1.75 + 50 × 14.00).[MJ-02] GPT-5.4 Nano Output Pricing Self-Contradictory Within Same File
Description The GPT-5.4 Nano model page states the output price as $1.25/1M tokens in two places (the overview paragraph and the Key Features bullet), but the Credits and Pricing table at the bottom of the same file shows $1.20 output. The two values disagree within the same file, and users relying on either will have inaccurate cost expectations. The pricing table in Code <!-- Overview paragraph (line ~4) -->
At just $0.20/$1.25 per MTok, it delivers reasoning capabilities…
<!-- Key Features bullet (line ~8) -->
- **Extreme Cost Efficiency**: $0.20/1M input + $1.25/1M output …
<!-- Credits and Pricing table (line ~34) -->
| GPT-5.4 Nano | $0.20 | $1.2 |Recommendation Unify to a single value (verify against the authoritative source). If $1.20 is correct, update Overview and Key Features prose: At just $0.20/$1.20 per MTok, …
- **Extreme Cost Efficiency**: $0.20/1M input + $1.20/1M output …
| GPT-5.4 Nano | $0.20 | $1.20 |[MJ-03] API Base URL Domain Change With No Migration Notice
Description The API Base URL was silently changed from Code -| `https://api.bankofai.com` | Production |
+- **Base URL:** `https://api.bankofai.io`Recommendation Add a migration notice (inline callout or a dedicated section) informing users of the URL change: > **Migration Notice:** The production API base URL has changed from
> `https://api.bankofai.com` to `https://api.bankofai.io`.
> The old domain will continue to be supported until [date]. Please update
> your integrations accordingly.Minor[MN-01] H1 Page Titles Removed From Six Documentation Files
Description The three renamed model files had their H1 ( Code (example — gpt-5-mini.md) -# ChatGPT-5-mini
+
## OverviewRecommendation Restore or add H1 headings that reflect the new model names: # GPT-5-mini
## Overview
…For # Credits & Pricing[MN-02] Incomplete/Broken Link Placeholder in Pricing Page (EN)
Description The sentence "For specific model pricing, please check here：" ends with a Chinese full-width colon Code …Some models do not support web search marked as "-". For specific model pricing, please check here：
| Model | Input (Credits/Token) | …Recommendation Either add the intended link or remove the trailing phrase: …Some models do not support web search marked as "-".
| Model | Input (Credits/Token) | …[MN-03] Inconsistent Pricing Unit Notation Across Files
Description Two different pricing unit systems are used across the changed files without cross-referencing:
While the numeric values appear to be consistent (the Credit values align with dollar values), the notation is entirely different. A user reading a model page and then the pricing page will encounter two measurement systems with no explanation of equivalence. Recommendation Adopt a consistent notation in all model pages. Either:
[MN-04] Auth Section Internally Inconsistent in API.md
Description The Authentication section header labels the API Key method as "Messages endpoint only": ### API Key (Messages endpoint only)However, the Messages endpoint description further down says: **Auth:** API Key (`x-api-key`) or Bearer TokenIf Bearer Token is now also accepted on Recommendation If both auth methods are now supported on ### API Key
- **Type:** API Key
- **Header:** `x-api-key: <your-api-key>`
- **Endpoints:** `/v1/messages` (and `/v1/chat/completions` if applicable)And update endpoint-level auth notes to be explicit: **Auth:** Bearer Token or API Key (`x-api-key`)[MN-05] Trailing Whitespace in Sidebar Configuration Files
Description The newly added Code // sidebars.js
'llmservice/models/gpt-5-4-nano',
// i18n/zh-Hans/.../sidebars.js
'llmservice/models/gpt-5-4-nano',Recommendation 'llmservice/models/gpt-5-4-nano',Suggestions[S-01] Memory Service Docs Lack API/SDK Integration SectionFile: [S-02] Squash or Rebase Noisy Commit History Before MergeFile: Branch-level observation Positive Observations
Checklist Results
DisclaimerThis is an automated code review. It supplements but does not replace human review. The reviewer analyzed only the diff between Report generated by Code Review Skill v1.0.0 |
Code Review ReportProject: BofAI Documentation (Docusaurus) PR OverviewBranch Information
Commit History (Recent)
Review SummaryVerdict
Findings at a Glance
SummaryThis PR is a documentation-only update to a Docusaurus site. It introduces three categories of changes: (1) a significant overhaul of the LLM Service API reference — including a base URL domain migration, endpoint reordering, and richer inline examples; (2) model file renames ( Overall quality is good: the API docs are substantially clearer and more complete in their new form, the new model pages are detailed and well-structured, and the bilingual Memory Service doc is consistent between locales. However, three issues require attention before merge. Most notably, the English pricing calculation example contains arithmetically incorrect rates for GPT-5.2 (the Chinese counterpart was fixed; the English one was not). The base URL domain migration ( Change Summary1. API Reference Overhaul
Purpose: Replace terse table-based schema documentation with richer, example-driven reference docs aligned with the new 2. Model File Renames
Purpose: Standardise model naming to drop the "ChatGPT" prefix. 3. New Model Pages
Purpose: Document the newly supported GPT-5.4 model family. 4. Memory Service Documentation
Purpose: Introduce user-facing documentation for the new persistent memory feature. 5. Pricing & Usage Updates
Purpose: Keep pricing documentation current with the expanded model catalogue and the TRON-only deposit constraint. 6. Sidebar Configuration
Purpose: Expose newly added pages in the navigation tree. Detailed FindingsMajor[MJ-01] English Pricing Example Uses Wrong Rates for GPT-5.2
Description
Code (new English text): For example, if you use GPT-5.2 to ask a question (10 input tokens) and the AI responds
with an answer (50 output tokens), the entire dialogue consumes 512.5 credits
(calculated as: 10 × 1.25 + 50 × 10).Expected (matching Chinese locale and GPT-5.2 pricing): For example, if you use GPT-5.2 to ask a question (10 input tokens) and the AI responds
with an answer (50 output tokens), the entire dialogue consumes 717.5 credits
(calculated as: 10 × 1.75 + 50 × 14.00).Recommendation: Replace the rate values and result with the correct GPT-5.2 figures to match the Chinese locale and the pricing table on the same page. [MJ-02] Base URL Domain Migration Has No Migration / Deprecation Notice
Description
Code: -| `https://api.bankofai.com` | Production |
+- **Base URL:** `https://api.bankofai.io`Recommendation: Add an info/warning callout block immediately below the base URL noting the migration: > **⚠️ Base URL Migration:** The production base URL has changed from
> `https://api.bankofai.com` to `https://api.bankofai.io`.
> The old domain will remain active until **[DATE]**. Please update
> your integrations before that date.[MJ-03] Messages API Response Example Shows Wrong Model ID
Description
Code: {
"id": "chatcmpl-xxx",
"type": "message",
"role": "assistant",
"content": [
{ "type": "text", "text": "Hello! How can I help you?" }
],
"stop_reason": "end_turn",
"model": "gpt-5", // ← should be a Claude model ID
...
}Recommendation: Replace "model": "claude-sonnet-4-6",Minor[MN-01] H1 Headings Removed from Three Renamed Model Pages
Description
Code (diff from gpt-5-2.md): -# ChatGPT-5.2
+
## OverviewRecommendation: Add an H1 heading to each file that matches the model's display name, consistent with the sidebar label: # GPT-5.2Apply the same fix to the three new GPT-5.4 model pages ( [MN-02] Page-Level H1 Heading Removed from Pricing Pages
Description
Code: -# Pricing and Usage
-
## Credits & PricingRecommendation: Restore H1 headings: # Pricing and Usage
## Credits & Pricing[MN-03] GPT-5.4 Nano Pricing Shows Inconsistent Decimal Formatting
Description
Code: | GPT-5.4 Nano | $0.20 | $1.2 |Recommendation: Standardise to two decimal places: | GPT-5.4 Nano | $0.20 | $1.20 |[MN-04] Trailing Whitespace in Sidebar Configuration Files
Description
Code: 'llmservice/models/gpt-5-4-nano',(two trailing spaces after the comma) Recommendation: Remove trailing whitespace: 'llmservice/models/gpt-5-4-nano',[MN-05] Deposit Section Silently Drops BNB Chain / BscScan Support
Description
Code (old): **Supported Token Types:** The platform supports various mainstream tokens on supported
networks (including TRON and BNB Chain).Code (new): **Supported Token Types:** The platform supports various mainstream tokens within the
TRON ecosystem, including TRX, USDT, USDD, and USD1.Recommendation: If BNB Chain support has been discontinued, add a callout noting the change and any migration steps for users holding BNB Chain balances. If it is still supported but simply not mentioned, restore the reference. [MN-06] Endpoint Reordering May Break Existing Deep Links
Description
Recommendation: Either (a) keep the original anchor IDs by adding explicit Markdown anchor tags, or (b) document the changed section links in the PR description so that any external sites linking to the old anchors can be updated. Suggestions[S-01] Sidebar Model Ordering Could Follow Capability TierFile: [S-02] New Model Pages Missing Knowledge Cutoff Callout BoxFile: [S-03] API Doc Schema Cross-References Removed Without ReplacementFile: Positive Observations
Checklist Results
DisclaimerThis is an automated code review. It supplements but does not replace human review. The reviewer analyzed only the diff between the specified branches. Runtime behavior, integration testing, and deployment impact are not covered. Report generated by Code Review Skill v1.0.0 |
Code Review ReportProject: BofAI Documentation Site PR OverviewBranch Information
Commit History (Recent)
Review SummaryVerdict
Findings at a Glance
SummaryThis PR is a documentation-only update that expands the BofAI docs site in several meaningful ways: a complete API reference overhaul (both EN and ZH), new model pages for the GPT-5.4 family, a brand-new Memory service page, a rebranding of "ChatGPT-5" models to "GPT-5", and a payment-stack clarification (TRON-only). The overall direction is excellent — the API docs are dramatically more useful with inline JSON examples, full parameter tables, and stream event listings. However, several issues require attention before merge. The most impactful is a widespread missing H1 heading across six model files (three renamed, three newly created), which affects page rendering, SEO, and Docusaurus navigation. A wrong model name in the Messages API response example ( Change Summary1. API Reference Overhaul (EN + ZH)
Purpose: Transform a sparse table-based API reference into a developer-friendly reference with inline code examples, explicit request/response schemas, and stream event documentation for both OpenAI-compatible and Claude-compatible endpoints. 2. Memory Service Documentation (New)
Purpose: Document the Memory (persistent context) service for users, covering smart learning, history import, user control, and incognito mode. 3. Model Rebranding: ChatGPT-5 → GPT-5
Purpose: Align public-facing model names with 4. New GPT-5.4 Family Model Pages
Purpose: Document three newly released GPT-5.4-series models with overviews, benchmarks, use cases, capability tables, and pricing. 5. Pricing & Usage Page Updates
Purpose: Add pricing for MiniMax-M2.5, Kimi-K2.5, GLM-5, GPT-5.4 family; clarify TRON-only deposit; align example calculation to real model pricing. Detailed FindingsMajor[MJ-01] Wrong Model Name in Messages API Response Example
Description
Code {
"id": "chatcmpl-xxx",
"type": "message",
"role": "assistant",
"content": [
{ "type": "text", "text": "Hello! How can I help you?" }
],
"stop_reason": "end_turn",
"model": "gpt-5", <-- Should be a Claude model ID
...
}Recommendation {
"id": "msg-xxx",
"type": "message",
"role": "assistant",
"content": [
{ "type": "text", "text": "Hello! How can I help you?" }
],
"stop_reason": "end_turn",
"model": "claude-sonnet-4-6",
...
}Additionally, the [MJ-02] All Model Pages Missing H1 Heading
Description
Code -# ChatGPT-5.2
+
## Overview(Similarly missing in all other model files) Recommendation Add an H1 heading matching the model's display name to each affected file. For example: # GPT-5.2
## Overview
GPT-5.2 is the latest generation...For new files: # GPT-5.4
## Overview
GPT-5.4 is OpenAI's flagship...[MJ-03] Pricing Data Inconsistency: GPT-5.4 Nano Output Price
Description
Code <!-- In the Key Features list -->
- **Extreme Cost Efficiency**: $0.20/1M input + $1.25/1M output ...
<!-- In the pricing table -->
| GPT-5.4 Nano | $0.20 | $1.2 |Recommendation Standardize to the correct value. If the price is | GPT-5.4 Nano | $0.20 | $1.25 |If the price is [MJ-04] Base URL Changed Without Migration/Deprecation Notice
Description
Code -| `https://api.bankofai.com` | Production |
+- **Base URL:** `https://api.bankofai.io`Recommendation Add a callout or note near the Base URL clarifying the change and any transition period: > **Note:** The production base URL has changed to `https://api.bankofai.io`.
> The previous URL (`https://api.bankofai.com`) will continue to work until [date].
> Please update your integration accordingly.[MJ-05] Incomplete Sentence in Pricing Page ("please check here:")
Description
Code **Pricing for Different Models:** ...Some models do not support web search and are marked with "-".
For specific model pricing, please check here:
| Model | Input ...Recommendation Either remove the trailing phrase or complete it with a valid anchor/link: **Pricing for Different Models:** ...Some models do not support web search and are marked with "-".
Refer to the table below for specific model pricing:
| Model | Input ...Minor[MN-01] H1 Heading Removed from Pricing and Usage Pages
Description
Recommendation Restore the H1 headings: # Pricing and Usage
## Credits & Pricing[MN-02] Authentication Section Inconsistency (x-api-key Scope)
Description
Recommendation Update the header to remove the ambiguity: ### API Key
- **Type:** API Key
- **Header:** `x-api-key: <your-api-key>`
- **Supported on:** Messages endpoint (`/v1/messages`)Then in the endpoint section, clarify: "Auth: [MN-03] Sidebar Navigation Order: GPT-5.4 Models Interleaved with GPT-5
Description
Recommendation Group by family and order consistently (flagship first, or smallest-to-largest — pick one): // Option A: Flagship first within each family, newest family first
'llmservice/models/gpt-5-4',
'llmservice/models/gpt-5-4-mini',
'llmservice/models/gpt-5-4-nano',
'llmservice/models/gpt-5-2',
'llmservice/models/gpt-5-mini',
'llmservice/models/gpt-5-nano',[MN-04] Trailing Whitespace in sidebars.js
Description
Code 'llmservice/models/gpt-5-4-nano', ← trailing whitespace hereRecommendation Remove trailing whitespace: [MN-05] Deposit Section Silently Removes BNB Chain Support
Description
Recommendation Either add a deprecation callout for BNB Chain support, or briefly acknowledge legacy transaction history: > **Note:** BNB Chain deposits are no longer supported for new top-ups as of [date].
> Existing BNB Chain transaction history remains viewable via BscScan.Suggestions[S-01] New GPT-5.4 Model Pages Should Include a "Release Date" CalloutFile: [S-02] Memory Service Page Lacks API/Integration DetailsFile: [S-03] Pricing Example Should Use a Consistent Model ReferenceFile: Positive Observations
Checklist Results
DisclaimerThis is an automated code review. It supplements but does not replace human review. The reviewer analyzed only the diff between the specified branches. Runtime behavior, integration testing, and deployment impact are not covered. Report generated by Code Review Skill v1.0.0 |
Code Review ReportProject: Bank of AI (BofAI) Documentation Site PR OverviewBranch Information
Commit History (Recent, Representative)
Review SummaryVerdict
Findings at a Glance
SummaryThis PR is a documentation-only update to a Docusaurus-based documentation site for the Bank of AI (BofAI) LLM gateway service. It delivers several meaningful improvements: a comprehensive API reference overhaul (adding the Claude-compatible However, several issues require resolution before merge. The most impactful is that the newly added GPT-5.4 Pro model page is orphaned — it does not appear in either the English or Chinese sidebar navigation, making it unreachable through normal browsing. The pricing table on the pricing page is similarly incomplete, omitting GPT-5.4 Pro's rates. A pricing unit inconsistency between the per-model docs (which quote USD per 1M tokens) and the central pricing table (which quotes Credits per Token) will create serious user confusion. Finally, the Deposit section in the pricing page dropped its mention of BNB Chain support, which is a potential documentation regression if that deposit path is still active. Change Summary1. API Reference Overhaul (
|
| File | Change Type | Description |
|---|---|---|
docs/llmservice/api/API.md |
Modified | Full rewrite with JSON response examples, new /v1/messages endpoint, extended data models, and URL update |
i18n/zh-Hans/.../llmservice/api/API.md |
Modified | Chinese mirror of same changes |
Purpose: Significantly improves the API reference from terse table-only descriptions to full, developer-friendly documentation with concrete request/response examples, SSE event tables, and the complete Anthropic-compatible Messages endpoint.
2. New Memory Service Documentation (docs/llmservice/memory.md + zh-Hans mirror)
| File | Change Type | Description |
|---|---|---|
docs/llmservice/memory.md |
Added | New page documenting the Memory service (smart auto-learning, incognito mode, user control) |
i18n/zh-Hans/.../llmservice/memory.md |
Added | Chinese mirror |
Purpose: Introduces a brand-new doc page explaining the platform's long-term memory/context persistence feature.
3. Model Renaming: chatgpt-5-* → gpt-5-*
| File | Change Type | Description |
|---|---|---|
docs/llmservice/models/chatgpt-5-2.md → gpt-5-2.md |
Renamed + Modified | Model renamed + minor content updates |
docs/llmservice/models/chatgpt-5-mini.md → gpt-5-mini.md |
Renamed + Modified | Same |
docs/llmservice/models/chatgpt-5-nano.md → gpt-5-nano.md |
Renamed + Modified | Same |
| (zh-Hans mirrors) | Renamed + Modified | Same for all three |
Purpose: Aligns model page filenames/identifiers with the updated model ID convention.
4. New GPT-5.4 Family Model Pages
| File | Change Type | Description |
|---|---|---|
docs/llmservice/models/gpt-5-4.md |
Added | GPT-5.4 flagship model documentation |
docs/llmservice/models/gpt-5-4-mini.md |
Added | GPT-5.4 Mini documentation |
docs/llmservice/models/gpt-5-4-nano.md |
Added | GPT-5.4 Nano documentation |
docs/llmservice/models/gpt-5-4-pro.md |
Added | GPT-5.4 Pro documentation |
| (zh-Hans mirrors) | Added | Same four files |
Purpose: Adds dedicated documentation pages for the new GPT-5.4 model family.
5. Pricing & Usage Page Update (docs/llmservice/pricing-and-usage.md + zh-Hans mirror)
| File | Change Type | Description |
|---|---|---|
docs/llmservice/pricing-and-usage.md |
Modified | Expanded pricing table (GPT-5.4 family, MiniMax, Kimi, GLM), rewrote deposit section |
i18n/zh-Hans/.../pricing-and-usage.md |
Modified | Chinese mirror |
Purpose: Reflects newly added models and updated deposit instructions.
6. Sidebar Navigation Updates (sidebars.js + zh-Hans mirror)
| File | Change Type | Description |
|---|---|---|
sidebars.js |
Modified | Replaced chatgpt-5-* refs with gpt-5-*, added gpt-5-4/mini/nano, added Memory doc |
i18n/zh-Hans/.../sidebars.js |
Modified | Chinese mirror of same |
Purpose: Keeps navigation consistent with renamed and newly added model pages.
Detailed Findings
Major
[MJ-01] GPT-5.4 Pro Model Page Orphaned — Not in Sidebar Navigation
| Property | Value |
|---|---|
| Severity | Major |
| Category | Documentation / Correctness |
| File | sidebars.js : Lines 185-204 · i18n/zh-Hans/.../sidebars.js (same area) |
Description
The file docs/llmservice/models/gpt-5-4-pro.md (and its zh-Hans mirror) was added, but the model is never registered in either sidebars.js or the zh-Hans sidebar. As a result:
- The page is completely unreachable via normal sidebar navigation.
- Docusaurus may emit a build warning for an orphaned document.
- Users would only find this page through a direct URL or a manual search — undermining discoverability.
The three sibling models (gpt-5-4, gpt-5-4-mini, gpt-5-4-nano) were all correctly added to the sidebar. GPT-5.4 Pro was simply omitted.
Code
// sidebars.js — Models items list (current state, line ~193)
items: [
'llmservice/models/gpt-5-mini',
'llmservice/models/gpt-5-nano',
'llmservice/models/gpt-5-2',
'llmservice/models/gpt-5-4',
'llmservice/models/gpt-5-4-mini',
'llmservice/models/gpt-5-4-nano', // <-- gpt-5-4-pro is MISSING here
'llmservice/models/claude-haiku-4-5',
...Recommendation
items: [
'llmservice/models/gpt-5-mini',
'llmservice/models/gpt-5-nano',
'llmservice/models/gpt-5-2',
'llmservice/models/gpt-5-4',
'llmservice/models/gpt-5-4-mini',
'llmservice/models/gpt-5-4-nano',
'llmservice/models/gpt-5-4-pro', // Add this entry
'llmservice/models/claude-haiku-4-5',
...Apply the same fix to i18n/zh-Hans/docusaurus-plugin-content-docs/current/sidebars.js.
[MJ-02] GPT-5.4 Pro Omitted from the Central Pricing Table
| Property | Value |
|---|---|
| Severity | Major |
| Category | Documentation / Correctness |
| File | docs/llmservice/pricing-and-usage.md : Pricing table |
Description
The pricing-and-usage.md pricing table now lists GPT-5.4, GPT-5.4-mini, and GPT-5.4-nano, but GPT-5.4 Pro is absent. The model's own page (gpt-5-4-pro.md) quotes rates of 30.00 Credits/Token (input) and 180.00 Credits/Token (output) — the most expensive model in the catalogue by a wide margin. Users consulting the central pricing page cannot discover or budget for this model.
Code
<!-- pricing-and-usage.md — current table, GPT-5.4 Pro is nowhere present -->
| GPT-5.4 | 2.50 | 15.00 | 10,000 |
| GPT-5.2 | 1.75 | 14.00 | 10,000 |
| GPT-5.4-mini | 0.75 | 4.50 | 10,000 |
<!-- GPT-5.4 Pro MISSING -->Recommendation
Add a row to the pricing table:
| GPT-5.4 Pro | 30.00 | 180.00 | 10,000 |Apply the same fix to the zh-Hans mirror.
[MJ-03] Pricing Unit Inconsistency Between Model Pages and the Pricing Table
| Property | Value |
|---|---|
| Severity | Major |
| Category | Documentation / Correctness |
| File | docs/llmservice/models/gpt-5-4.md, gpt-5-4-mini.md, gpt-5-4-nano.md vs. docs/llmservice/pricing-and-usage.md |
Description
The new model-specific pages quote pricing in USD per 1 million tokens:
<!-- gpt-5-4.md -->
| GPT-5.4 | $2.50 | $15.00 | ← "per 1M tokens (USD)"But the central pricing table quotes pricing in Credits per individual token:
<!-- pricing-and-usage.md -->
| GPT-5.4 | 2.50 | 15.00 | ← "Credits/Token"The numbers happen to be identical (2.50 and 15.00), which makes the discrepancy invisible at a glance but deeply misleading: $2.50 per 1M tokens ≠ 2.50 Credits per token. A user comparing the two pages will either assume they are the same unit (incorrect) or be thoroughly confused about actual costs. For GPT-5.4 Pro the model page says 30.00/180.00 — in dollar-per-million-tokens terms these are consistent, but a developer reading the pricing table would interpret them as Credits-per-token, implying a 12,000× cost difference versus the model page.
Code
<!-- gpt-5-4.md — header row says "per 1M tokens" in USD -->
| Model | Input (per 1M tokens) | Output (per 1M tokens) |
| :--- | :--- | :--- |
| GPT-5.4 | $2.50 | $15.00 |
<!-- pricing-and-usage.md — header row says "Credits/Token" -->
| Model | Input (Credits/Token) | Output (Credits/Token) |
| GPT-5.4 | 2.50 | 15.00 |Recommendation
Decide on a single canonical unit (e.g., Credits per 1M tokens or Credits per token) and apply it consistently across all model pages and the pricing table. Update the column headers and values uniformly. Clarify the Credits-to-USD conversion rate (if any) in the pricing page introduction so users can cross-reference.
[MJ-04] Deposit Section Drops BNB Chain Support — Potential Documentation Regression
| Property | Value |
|---|---|
| Severity | Major |
| Category | Documentation / Correctness |
| File | docs/llmservice/pricing-and-usage.md : Deposit section |
Description
The main branch version of the deposit section stated:
"The platform supports various mainstream tokens on supported networks (including TRON and BNB Chain)."
The new version now reads:
"The platform supports various mainstream tokens within the TRON ecosystem, including TRX, USDT, USDD, and USD1."
BNB Chain (and any associated tokens) is completely removed. If BNB Chain deposits remain available in the actual product, this change constitutes a documentation regression that will mislead users into believing only TRON is supported — potentially causing failed deposit attempts. The zh-Hans mirror carries the same TRON-only text.
Code
<!-- main branch -->
* **Supported Token Types:** The platform supports various mainstream tokens
on supported networks (including TRON and BNB Chain).
<!-- ai-bankofai-patch-1 -->
**Supported Token Types:** The platform supports various mainstream tokens within
the TRON ecosystem, including TRX, USDT, USDD, and USD1.Recommendation
If BNB Chain deposits are still supported, restore the multi-network language and enumerate supported tokens per network. If BNB Chain has been discontinued, the change is intentional but should be accompanied by a clear notice (e.g., a deprecation callout block) for existing users. Verify the product state before merging.
Minor
[MN-01] Missing H1 Title on Pricing Page
| Property | Value |
|---|---|
| Severity | Minor |
| Category | Documentation Quality |
| File | docs/llmservice/pricing-and-usage.md : Line 1 |
Description
The original file opened with a top-level heading # Pricing and Usage. The new version omits this and starts directly at an H2 (## Credits & Pricing). Docusaurus uses the first H1 as the browser tab title and breadcrumb label. Without it, the page title may fall back to the sidebar label or be blank, degrading the user experience.
Recommendation
Restore the H1 title:
# Pricing and Usage
## Credits & Pricing
...Apply the same fix to the zh-Hans mirror.
[MN-02] Internal Cache Field Names Exposed in Messages API Response Example
| Property | Value |
|---|---|
| Severity | Minor |
| Category | Documentation Quality |
| File | docs/llmservice/api/API.md : Messages endpoint response example |
Description
The non-streaming response example for the /v1/messages endpoint includes two unusual fields:
"claude_cache_creation_5_m_tokens": 0,
"claude_cache_creation_1_h_tokens": 0These field names look like internal implementation artefacts (referencing raw Anthropic cache TTL durations). Exposing them as first-class documented API fields may:
- Confuse developers trying to understand their meaning (
5_m= 5 minutes?1_h= 1 hour?). - Create implicit API contract obligations if clients start depending on them.
- Leak internal infrastructure terminology.
Recommendation
Either remove these fields from the public-facing example (if they are internal), or rename and document them explicitly (e.g., cache_creation_tokens_5min, cache_creation_tokens_1hr) with a clear description of what each represents and when it is non-zero.
[MN-03] Trailing Whitespace in Sidebar Files
| Property | Value |
|---|---|
| Severity | Minor |
| Category | Code Quality |
| File | sidebars.js : Line ~198 · i18n/zh-Hans/.../sidebars.js : same |
Description
Both sidebar files contain a line with trailing whitespace:
'llmservice/models/gpt-5-4-nano',While harmless at runtime, trailing whitespace commonly triggers linter warnings, pollutes diffs, and is inconsistent with the rest of the file.
Recommendation
Remove the trailing spaces from both files:
'llmservice/models/gpt-5-4-nano',[MN-04] API Base URL Changed Without Explicit Callout
| Property | Value |
|---|---|
| Severity | Minor |
| Category | Documentation / Correctness |
| File | docs/llmservice/api/API.md : Line 5 |
Description
The API base URL was silently changed from https://api.bankofai.com (listed in the former Servers table) to https://api.bankofai.io (new header field). This change is significant for any developer who has already integrated against the documented endpoint. There is no changelog note, migration callout, or deprecation notice explaining the change. If the old domain is no longer the canonical API endpoint, existing integrations will break without warning.
Code
<!-- main branch -->
| `https://api.bankofai.com` | Production |
<!-- ai-bankofai-patch-1 -->
- **Base URL:** `https://api.bankofai.io`Recommendation
Add an info/warning callout block in the API doc clarifying the domain change:
:::info Base URL Update
The production base URL has changed from `api.bankofai.com` to `api.bankofai.io`.
Please update any existing integrations accordingly.
:::Additionally, verify that api.bankofai.com is either redirecting to api.bankofai.io or has been decommissioned before finalizing this documentation.
Suggestions
[S-01] GPT-5.4 Nano Output Pricing Formatted Inconsistently
File: docs/llmservice/models/gpt-5-4-nano.md
Description: The Credits and Pricing table in the Nano model page uses $1.2 for output, while all other model pages use two-decimal formatting ($1.20, $4.50, $15.00, etc.).
Suggestion: Normalise to two decimal places: change $1.2 → $1.20 for consistency.
[S-02] Duplicate Commit Pairs Suggest Force-Push History Was Not Cleaned
File: Git history
Description: The commit log contains several duplicate pairs with identical messages: "Create gpt-5-4-pro.md" appears twice (5328cda, 0044127), "Update pricing-and-usage.md" appears multiple times (2a6a7fd, a2b2d5f, 9e2e104, 8455399), and so on. This indicates iterative direct-to-branch commits without squashing, which creates noisy history.
Suggestion: Before merging, squash or consolidate related commits into logical units (e.g., "Add GPT-5.4 family model documentation", "Update API reference to v1.1") to produce a cleaner, reviewable commit history.
Positive Observations
| Area | Observation |
|---|---|
| API documentation quality | The API.md rewrite is a substantial improvement — replacing cryptic one-liner table entries with full JSON request/response examples, explicit parameter tables, and SSE event-type breakdowns. This is significantly more useful for developers. |
| i18n parity | Every English change in docs/ has a corresponding Chinese translation in i18n/zh-Hans/. The two locales are in sync. |
| New Memory documentation | The memory.md page is clearly structured, uses consistent headers, and covers all key aspects of the feature (auto-learning, import, user control, incognito mode). |
| Model capability tables | The new GPT-5.4 family model pages include consistent, detailed capability tables (reasoning, creative, multimodal, speed, context window, knowledge cutoff) — a strong pattern to continue for future model additions. |
| Sidebar Memory entry | Adding { type: 'doc', id: 'llmservice/memory', label: 'Memory' } to the sidebar correctly exposes the new memory.md page in the navigation. |
| Pricing example updated | The new pricing example correctly recalculates using the current GPT-5.2 rates (10 × 1.75 + 50 × 14 = 717.5), replacing the outdated placeholder example. |
Checklist Results
| Category | Items Checked | Pass | Fail | N/A | Notes |
|---|---|---|---|---|---|
| Correctness | 6 | 3 | 3 | 3 | URL change unverified; pricing units inconsistent; BNB Chain dropped |
| Security | 8 | 7 | 1 | 0 | Internal cache field names exposed in response example |
| Performance | 7 | 0 | 0 | 7 | No code changes; docs only |
| Code Quality | 8 | 6 | 2 | 0 | Trailing whitespace; missing H1 title |
| Testing | 7 | 0 | 0 | 7 | Documentation PR — no functional test coverage needed |
| Documentation | 6 | 4 | 2 | 0 | Sidebar orphan; pricing table missing GPT-5.4 Pro |
| Compatibility | 5 | 4 | 1 | 0 | API URL change without backward-compat notice |
| Observability | 4 | 0 | 0 | 4 | Not applicable to a docs-only change |
Disclaimer
This is an automated code review. It supplements but does not replace human review. The reviewer analyzed only the diff between origin/main and origin/ai-bankofai-patch-1. Runtime behavior, integration testing, and deployment impact are not covered.
Report generated by Code Review Skill v1.0.0
Date: 2026-04-07
Code Review ReportProject: Bank of AI Documentation ( PR OverviewBranch Information
Commit History (Recent)
Review SummaryVerdict
Findings at a Glance
SummaryThis PR is a significant documentation update that renames the GPT model family ( Overall the changes are well-structured and the quality of the new content is good. However, several factual inconsistencies and a breaking change require resolution before merge. The most impactful issues are: a silent change of the production API base URL with no migration guidance, a pricing discrepancy in GPT-5.4 Nano, a wrong model name in a response example, GPT-5.4 Pro absent from the pricing table, and the undocumented removal of BNB Chain deposit support. Additionally, seven documentation pages were left without H1 titles, which will render as untitled pages on the site. Change Summary1. Model Renames: ChatGPT-5.x → GPT-5.x
Purpose: Align model names with upstream OpenAI branding (dropping the "Chat" prefix). 2. New Model Documentation (GPT-5.4 Family)
Purpose: Document four newly supported models in the GPT-5.4 series. 3. API Reference Overhaul
Purpose: Improve readability, add concrete request/response examples, document the Claude-compatible Messages endpoint more thoroughly. 4. New Memory Service Page
Purpose: Introduce long-term memory capabilities for AI agents. 5. Pricing, Sidebar & Package Updates
Purpose: Surface new models and Memory in navigation; reflect deposit network changes; bump package version. Detailed FindingsMajor[MJ-01] Breaking API Base URL Change with No Migration Guidance
Description The production API base URL changed from If the domain change is live on the backend, users relying on Code -## Servers
-| URL | Description |
-|-----|-------------|
-| `https://api.bankofai.com` | Production |
+- **Base URL:** `https://api.bankofai.io`Recommendation Add an explicit deprecation notice near the base URL change. For example: > **Note (Migration):** The API base URL has changed from `https://api.bankofai.com`
> to `https://api.bankofai.io`. The old domain will continue to accept traffic until
> **[DATE]**. Please update your integrations accordingly.If the old domain is being kept as an alias indefinitely, document that. If it is being decommissioned, include the timeline. [MJ-02] GPT-5.4 Nano Output Pricing Inconsistency ($1.25 vs $1.20)
Description The Overview section (line 1) and the Key Features bullet state the output price as $1.25 per million tokens. However, the Credits and Pricing table at the bottom of the same file shows $1.2 (missing the trailing 5). Both the English and Chinese files share this inconsistency. Users relying on the pricing table — the most likely reference point — will see a lower figure than the one stated in the prose. Code # Overview (line 1):
"At just $0.20/$1.25 per MTok..."
# Key Features bullet:
"$0.20/1M input + $1.25/1M output"
# Credits and Pricing table:
| GPT-5.4 Nano | $0.20 | $1.2 | ← should be $1.25Recommendation Decide on the canonical price and apply it consistently. If the price is $1.25: | GPT-5.4 Nano | $0.20 | $1.25 |Also verify consistency against the central [MJ-03] Messages API Response Example Hardcodes Wrong Model Name
Description The Messages endpoint ( Code // Request:
{ "model": "claude-sonnet-4-6", ... }
// Response (non-stream):
{
"model": "gpt-5", ← WRONG — should match the requested model
...
}Recommendation Update the response example to reflect the model sent in the request: {
"id": "msg-xxx",
"type": "message",
"role": "assistant",
"model": "claude-sonnet-4-6",
...
}[MJ-04] GPT-5.4 Pro Not Listed in Pricing Table
Description Four new models are added (GPT-5.4, GPT-5.4 Mini, GPT-5.4 Nano, GPT-5.4 Pro) and the first three appear in the updated pricing table in Code # pricing-and-usage.md pricing table (excerpt):
| GPT-5.4 | 2.50 | 15.00 | 10,000 |
| GPT-5.2 | 1.75 | 14.00 | 10,000 |
| GPT-5.4-mini | 0.75 | 4.50 | 10,000 |
# ... GPT-5.4-Pro is missing entirelyRecommendation Add GPT-5.4 Pro to the pricing table: | GPT-5.4 Pro | 30.00 | 180.00 | 10,000 |Also confirm whether GPT-5.4 Pro supports web search (the model page does not mention it) and set the web search column appropriately. [MJ-05] Deposit Section Silently Removes BNB Chain Support
Description The previous documentation explicitly listed BNB Chain as a supported deposit network alongside TRON, and referenced BscScan as a blockchain explorer for verifying BNB Chain transactions. This PR rewrites the Deposit section to mention only the TRON ecosystem (TRX, USDT, USDD, USD1) and removes any reference to BNB Chain or BscScan. There is no deprecation notice, no user-facing announcement, and no alternative offered for users who deposited or planned to deposit via BNB Chain. If BNB Chain support has genuinely been removed, this is a significant breaking change for existing users with no communication. If it still exists but was accidentally omitted, this is a documentation error. Code -* **Supported Token Types:** The platform supports various mainstream tokens on
- supported networks (including TRON and BNB Chain).
-* ... You can click the transaction hash to verify details on the corresponding
- blockchain explorer (e.g., TRONSCAN or BscScan).
+**Supported Token Types:** The platform supports various mainstream tokens within
+ the TRON ecosystem, including TRX, USDT, USDD, and USD1.
+**Transaction Hash Query:** You can click the transaction hash to verify the
+ transaction details...Recommendation If BNB Chain is being deprecated:
If BNB Chain is still supported but accidentally omitted:
Minor[MN-01] Seven Model Pages and One Doc Page Missing H1 Title
Description The three renamed model files had their -# ChatGPT-5.2
+
## OverviewSimilarly, the four new model files ( Recommendation Add an appropriate H1 heading as the first line of each affected file: # GPT-5.2
## Overview
...
# GPT-5.4 Pro
## Overview
...
# Pricing and Usage
## Credits & Pricing
...[MN-02] GPT-5.4 Context Window Contradicts Itself
Description The Overview paragraph says GPT-5.4 supports "up to 1,050,000 tokens of context", but the Capabilities and Limitations table gives two contradictory values: # Overview (line 3):
"With up to 1,050,000 tokens of context..."
# Capabilities table:
| **Context Window** | Standard 272K tokens; expandable to 1,050,000 tokens (requires explicit configuration). |The Overview implies 1M+ is the default; the table says 272K is the standard and 1M+ requires configuration. These should be reconciled so users know the default context size and how to unlock the larger window. Recommendation Decide on the canonical description. If 272K is the default: # Overview: "... supports up to 272,000 tokens by default, expandable to 1,050,000 tokens."
# Table: unchanged (272K standard; 1,050K with explicit config)[MN-03] GPT-5.4 Pro Has a Duplicate "Limitations" Section
Description Limitations are documented twice in Code # In the Capabilities table:
| **Response Speed** | Slower — some complex requests may take several minutes... |
# Then separately at the bottom:
## Limitations
- **High latency**: Complex requests may take several minutes...
- **Cost**: It is one of the most expensive API models available.
- **No audio/video input**: ...Recommendation Remove the standalone [MN-04] API.md Removes Several Documented Response Fields
Description The old API.md contained detailed schema tables for Recommendation Either restore these fields in the inline response examples with a comment noting they are optional/informational: {
"id": "chatcmpl-xxx",
"service_tier": "default",
"system_fingerprint": null,
"obfuscation": "...",
...
}Or add a note such as: "Additional response fields ( [MN-05] API Key Docs Describe Messages Endpoint as "Only" then Change Scope
Description The Authentication section header says "API Key (Messages endpoint only)", implying Code ### API Key (Messages endpoint only) ← misleading — Bearer also works on Messages
...
### 3. Messages (Claude Compatible)
**Auth:** API Key (`x-api-key`) or Bearer Token ← both auth methods acceptedRecommendation Rename the auth section to clarify: ### API Key
- **Supported on:** `/v1/messages` endpoint
- **Type:** API Key
- **Header:** `x-api-key: <your-api-key>`Suggestions[S-01] "Zero-Hallucination Recall" Claim May OverpromiseFile: [S-02] No Changelog or Migration Notice for Model RenamesFile: [S-03] New Model Files Could Cross-Reference the Pricing PageFile: Positive Observations
Checklist Results
DisclaimerThis is an automated code review. It supplements but does not replace human review. The reviewer analyzed only the diff between the specified branches. Runtime behavior, integration testing, and deployment impact are not covered. Report generated by Code Review Skill v1.0.0 |
3 participants
No description provided.