docs: remove max_budget_usd references from standalone docs (managed-only field)

[janiussyafiq]

Summary

Remove all 12 customer-facing references to max_budget_usd from the docs. The field name does not exist as an OSS standalone ApiKey schema field (PR #259 removed it; StandaloneApiKeyBody rejects unknown fields). Pass-1.5 verification (see Revision notes) confirmed it also does not exist on AISIX-Cloud's admin API surface — Cloud uses limit_cents int64 internally. Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. See Revision notes below for the multi-pivot history.

Changes

File	Change
docs/integration/errors-and-retries.md	429 row rationale: Budget rejection from the ApiKey's max_budget_usd → Budget rejection from the managed budget controller
docs/reference/resource-schemas.md	Remove the Runtime Versus Schema Boundary example bullet about the typed model / OpenAPI / write validator inconsistency
docs/configuration/api-keys.md	Drop the Budget Boundary bullet about the write validator rejecting the field + the trailing "Do not treat ... as part of the verified standalone admin write contract" advisory
docs/configuration/budgets.md	Remove the intro line; drop the Managed Versus Standalone "Because of that boundary..." sentence and the typed/OpenAPI + write validator bullets; remove the A standalone deployment ignores max_budget_usd troubleshooting subsection (no replacement). Final state: no max_budget_usd mentions on this page. See Revision notes for pivot history.
docs/overview/core-concepts.md	Remove the trailing sentence "Managed budget paths may also reference per-key budget state, but max_budget_usd is not part of the current verified standalone admin write contract"
docs/overview/feature-matrix.md	"Per-key budgets" row rationale: replace mention of the rejected field with "standalone deployments do not enforce per-key budgets; managed deployments enforce via the budget controller"

Net diff: 6 files, +4 / -21, no .rs / schema / config / test files touched.

Test plan

• grep -rn 'max_budget_usd' docs/ --include='*.md' after the edits returns 0 hits — confirms the field name does not appear anywhere in OSS docs.
• grep -rn 'max_budget_usd' crates/aisix-core/src/models/apikey.rs returns zero matches — confirms the field is genuinely absent from the OSS schema (this PR documents that absence; no code change required).
• cargo fmt --check — PASS (exit 0).
• cargo clippy --workspace --all-targets -- -D warnings — PASS (exit 0, no warnings, Finished dev profile [unoptimized + debuginfo] target(s) in 41.91s).
• cargo test --workspace — PASS (exit 0, all crate test suites green; no failures, 2 ignored).
• E2E: grep -rln <each affected page> tests/e2e/ returns empty for all 6 pages — no e2e fixture references them, pnpm test not applicable.

References

• Closesdocs: remove max_budget_usd references from standalone docs (managed-only field) #295
• fix(admin): drop standalone max_budget_usd contract #259 — fix(admin): drop standalone max_budget_usd contract (the field removal that this docs cleanup is a follow-up to)
• Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control #255 — Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control (the originating decision)
• docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials #249 — docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials (the rebuild that re-introduced the now-stale references)

Revision notes

• Revision 1 → 2 (2ed56fb → 1822515): original R3 approach removed all 12 max_budget_usd references and rewrote budgets.md abstractly. Per operator review, restored one canonical Troubleshooting subsection on docs/configuration/budgets.md naming the field in the rejection context. Rationale: preserves discoverability for the 400-rejection error users hit when migrating Cloud-style configs to standalone. Other 5 files's R3 removals remain.
• Revision 3 → 4 (a8cb07e → 7aa99ce): Pass-1.5 verification surfaced that max_budget_usd doesn't exist as a field name on AISIX-Cloud's admin API surface either (Cloud uses limit_cents int64; verified no max_budget_usd in Go source, OpenAPI, or YAML/JSON specs). The canonical Troubleshooting subsection added in revision 2 (1822515) asserted "managed-mode field implemented in AISIX Cloud's control plane" — that assertion is empirically false. Operator pivoted from Option δ → pure R1 (full removal). The Troubleshooting subsection deleted entirely.
• Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. The field name does not appear anywhere in OSS docs.

Summary by CodeRabbit

• Documentation
  • Clarified that standalone deployments do not enforce per-key budgets by default (budget client disabled/allow-all) and removed prior contradictory validation notes.
  • Added guidance to drop per-key budget fields from standalone admin write payloads.
  • Updated errors to include HTTP 429 billing_error for budget-exceeded responses.
  • Clarified model access control: empty list denies; wildcard "*" allows.

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: d1a7b917-704c-4c46-ba5e-9fd0fa88e87d

📥 Commits

Reviewing files that changed from the base of the PR and between a8cb07e and 7aa99ce.

📒 Files selected for processing (1)

• docs/configuration/budgets.md

💤 Files with no reviewable changes (1)

• docs/configuration/budgets.md

---

📝 Walkthrough

Walkthrough

This PR updates documentation to clarify that standalone deployments default to a disabled, allow-all budget client (removing prior max_budget_usd caveats), documents that managed deployments enforce per-key budgets via a budget controller (with 429 budget_exceeded), and adds allowed_models access semantics.

Changes

Budget enforcement and access control documentation clarification

Layer / File(s)	Summary
Standalone budget behavior clarification docs/configuration/api-keys.md, docs/configuration/budgets.md, docs/reference/resource-schemas.md	Removes the misleading caveat that max_budget_usd appears in the ApiKey schema/OpenAPI but is rejected by the standalone admin write validator. Replaces with statements that standalone deployments default to a disabled budget client with allow-all behavior and updates troubleshooting/migration guidance.
Managed budget enforcement documentation docs/integration/errors-and-retries.md, docs/overview/feature-matrix.md	Clarifies that per-key budget enforcement is performed by the managed data-plane budget controller. Updates error docs to attribute 429 billing_error with code: "budget_exceeded" to the managed budget controller and notes enforcement differences in the feature matrix.
API Key allowed_models access control docs/overview/core-concepts.md	Adds explicit access-control contract: empty allowed_models denies all models; wildcard "*" allows all models within the applicable scope. Replaces prior budget-path phrasing with model-access semantics.

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

Note

🎁 Summarized by CodeRabbit Free

Your organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.If you believe this is a mistake and have available seats, please assign one to the pull request author through the subscription management page using the link above.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR removes standalone documentation references to max_budget_usd, aligning the docs with the current standalone admin contract where that managed-only field is not exposed.

Changes:

• Removes stale max_budget_usd references from API key, schema, budget, feature-matrix, and error docs.
• Reframes budget enforcement as managed-control-plane driven, with standalone defaulting to allow-all budget behavior.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
docs/reference/resource-schemas.md	Removes the stale schema-boundary example for max_budget_usd.
docs/overview/feature-matrix.md	Updates per-key budget limitations to describe standalone vs managed behavior.
docs/overview/core-concepts.md	Removes managed budget field caveat from API key concepts.
docs/integration/errors-and-retries.md	Rewords budget-related 429 trigger text.
docs/configuration/budgets.md	Removes field-specific guidance and rewrites standalone budget troubleshooting.
docs/configuration/api-keys.md	Removes standalone write-contract warning for the removed field.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

[janiussyafiq]

Summary

Remove all 12 customer-facing references to max_budget_usd from the docs. The field name does not exist as an OSS standalone ApiKey schema field (PR #259 removed it; StandaloneApiKeyBody rejects unknown fields). Pass-1.5 verification (see Revision notes) confirmed it also does not exist on AISIX-Cloud's admin API surface — Cloud uses limit_cents int64 internally. Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. See Revision notes below for the multi-pivot history.

Changes

File	Change
docs/integration/errors-and-retries.md	429 row rationale: Budget rejection from the ApiKey's max_budget_usd → Budget rejection from the managed budget controller
docs/reference/resource-schemas.md	Remove the Runtime Versus Schema Boundary example bullet about the typed model / OpenAPI / write validator inconsistency
docs/configuration/api-keys.md	Drop the Budget Boundary bullet about the write validator rejecting the field + the trailing "Do not treat ... as part of the verified standalone admin write contract" advisory
docs/configuration/budgets.md	Remove the intro line; drop the Managed Versus Standalone "Because of that boundary..." sentence and the typed/OpenAPI + write validator bullets; remove the A standalone deployment ignores max_budget_usd troubleshooting subsection (no replacement). Final state: no max_budget_usd mentions on this page. See Revision notes for pivot history.
docs/overview/core-concepts.md	Remove the trailing sentence "Managed budget paths may also reference per-key budget state, but max_budget_usd is not part of the current verified standalone admin write contract"
docs/overview/feature-matrix.md	"Per-key budgets" row rationale: replace mention of the rejected field with "standalone deployments do not enforce per-key budgets; managed deployments enforce via the budget controller"

Net diff: 6 files, +4 / -21, no .rs / schema / config / test files touched.

Test plan

• grep -rn 'max_budget_usd' docs/ --include='*.md' after the edits returns 0 hits — confirms the field name does not appear anywhere in OSS docs.
• grep -rn 'max_budget_usd' crates/aisix-core/src/models/apikey.rs returns zero matches — confirms the field is genuinely absent from the OSS schema (this PR documents that absence; no code change required).
• cargo fmt --check — PASS (exit 0).
• cargo clippy --workspace --all-targets -- -D warnings — PASS (exit 0, no warnings, Finished dev profile [unoptimized + debuginfo] target(s) in 41.91s).
• cargo test --workspace — PASS (exit 0, all crate test suites green; no failures, 2 ignored).
• E2E: grep -rln <each affected page> tests/e2e/ returns empty for all 6 pages — no e2e fixture references them, pnpm test not applicable.

References

• Closesdocs: remove max_budget_usd references from standalone docs (managed-only field) #295
• fix(admin): drop standalone max_budget_usd contract #259 — fix(admin): drop standalone max_budget_usd contract (the field removal that this docs cleanup is a follow-up to)
• Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control #255 — Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control (the originating decision)
• docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials #249 — docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials (the rebuild that re-introduced the now-stale references)

Revision notes

• Revision 1 → 2 (2ed56fb → 1822515): original R3 approach removed all 12 max_budget_usd references and rewrote budgets.md abstractly. Per operator review, restored one canonical Troubleshooting subsection on docs/configuration/budgets.md naming the field in the rejection context. Rationale: preserves discoverability for the 400-rejection error users hit when migrating Cloud-style configs to standalone. Other 5 files's R3 removals remain.
• Revision 3 → 4 (a8cb07e → 7aa99ce): Pass-1.5 verification surfaced that max_budget_usd doesn't exist as a field name on AISIX-Cloud's admin API surface either (Cloud uses limit_cents int64; verified no max_budget_usd in Go source, OpenAPI, or YAML/JSON specs). The canonical Troubleshooting subsection added in revision 2 (1822515) asserted "managed-mode field implemented in AISIX Cloud's control plane" — that assertion is empirically false. Operator pivoted from Option δ → pure R1 (full removal). The Troubleshooting subsection deleted entirely.
• Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. The field name does not appear anywhere in OSS docs.

Summary by CodeRabbit

• Documentation
  • Clarified that standalone deployments do not enforce per-key budgets by default (budget client disabled/allow-all) and removed prior contradictory validation notes.
  • Added guidance to drop per-key budget fields from standalone admin write payloads.
  • Updated errors to include HTTP 429 billing_error for budget-exceeded responses.
  • Clarified model access control: empty list denies; wildcard "*" allows.

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: d1a7b917-704c-4c46-ba5e-9fd0fa88e87d

📥 Commits

Reviewing files that changed from the base of the PR and between a8cb07e and 7aa99ce.

📒 Files selected for processing (1)

• docs/configuration/budgets.md

💤 Files with no reviewable changes (1)

• docs/configuration/budgets.md

---

📝 Walkthrough

Walkthrough

This PR updates documentation to clarify that standalone deployments default to a disabled, allow-all budget client (removing prior max_budget_usd caveats), documents that managed deployments enforce per-key budgets via a budget controller (with 429 budget_exceeded), and adds allowed_models access semantics.

Changes

Budget enforcement and access control documentation clarification

Layer / File(s)	Summary
Standalone budget behavior clarification docs/configuration/api-keys.md, docs/configuration/budgets.md, docs/reference/resource-schemas.md	Removes the misleading caveat that max_budget_usd appears in the ApiKey schema/OpenAPI but is rejected by the standalone admin write validator. Replaces with statements that standalone deployments default to a disabled budget client with allow-all behavior and updates troubleshooting/migration guidance.
Managed budget enforcement documentation docs/integration/errors-and-retries.md, docs/overview/feature-matrix.md	Clarifies that per-key budget enforcement is performed by the managed data-plane budget controller. Updates error docs to attribute 429 billing_error with code: "budget_exceeded" to the managed budget controller and notes enforcement differences in the feature matrix.
API Key allowed_models access control docs/overview/core-concepts.md	Adds explicit access-control contract: empty allowed_models denies all models; wildcard "*" allows all models within the applicable scope. Replaces prior budget-path phrasing with model-access semantics.

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

Note

🎁 Summarized by CodeRabbit Free

Your organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.If you believe this is a mistake and have available seats, please assign one to the pull request author through the subscription management page using the link above.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR removes standalone documentation references to max_budget_usd, aligning the docs with the current standalone admin contract where that managed-only field is not exposed.

Changes:

• Removes stale max_budget_usd references from API key, schema, budget, feature-matrix, and error docs.
• Reframes budget enforcement as managed-control-plane driven, with standalone defaulting to allow-all budget behavior.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
docs/reference/resource-schemas.md	Removes the stale schema-boundary example for max_budget_usd.
docs/overview/feature-matrix.md	Updates per-key budget limitations to describe standalone vs managed behavior.
docs/overview/core-concepts.md	Removes managed budget field caveat from API key concepts.
docs/integration/errors-and-retries.md	Rewords budget-related 429 trigger text.
docs/configuration/budgets.md	Removes field-specific guidance and rewrites standalone budget troubleshooting.
docs/configuration/api-keys.md	Removes standalone write-contract warning for the removed field.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

[janiussyafiq]

Summary

Remove all 12 customer-facing references to max_budget_usd from the docs. The field name does not exist as an OSS standalone ApiKey schema field (PR #259 removed it; StandaloneApiKeyBody rejects unknown fields). Pass-1.5 verification (see Revision notes) confirmed it also does not exist on AISIX-Cloud's admin API surface — Cloud uses limit_cents int64 internally. Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. See Revision notes below for the multi-pivot history.

Changes

File	Change
docs/integration/errors-and-retries.md	429 row rationale: Budget rejection from the ApiKey's max_budget_usd → Budget rejection from the managed budget controller
docs/reference/resource-schemas.md	Remove the Runtime Versus Schema Boundary example bullet about the typed model / OpenAPI / write validator inconsistency
docs/configuration/api-keys.md	Drop the Budget Boundary bullet about the write validator rejecting the field + the trailing "Do not treat ... as part of the verified standalone admin write contract" advisory
docs/configuration/budgets.md	Remove the intro line; drop the Managed Versus Standalone "Because of that boundary..." sentence and the typed/OpenAPI + write validator bullets; remove the A standalone deployment ignores max_budget_usd troubleshooting subsection (no replacement). Final state: no max_budget_usd mentions on this page. See Revision notes for pivot history.
docs/overview/core-concepts.md	Remove the trailing sentence "Managed budget paths may also reference per-key budget state, but max_budget_usd is not part of the current verified standalone admin write contract"
docs/overview/feature-matrix.md	"Per-key budgets" row rationale: replace mention of the rejected field with "standalone deployments do not enforce per-key budgets; managed deployments enforce via the budget controller"

Net diff: 6 files, +4 / -21, no .rs / schema / config / test files touched.

Test plan

• grep -rn 'max_budget_usd' docs/ --include='*.md' after the edits returns 0 hits — confirms the field name does not appear anywhere in OSS docs.
• grep -rn 'max_budget_usd' crates/aisix-core/src/models/apikey.rs returns zero matches — confirms the field is genuinely absent from the OSS schema (this PR documents that absence; no code change required).
• cargo fmt --check — PASS (exit 0).
• cargo clippy --workspace --all-targets -- -D warnings — PASS (exit 0, no warnings, Finished dev profile [unoptimized + debuginfo] target(s) in 41.91s).
• cargo test --workspace — PASS (exit 0, all crate test suites green; no failures, 2 ignored).
• E2E: grep -rln <each affected page> tests/e2e/ returns empty for all 6 pages — no e2e fixture references them, pnpm test not applicable.

References

• Closesdocs: remove max_budget_usd references from standalone docs (managed-only field) #295
• fix(admin): drop standalone max_budget_usd contract #259 — fix(admin): drop standalone max_budget_usd contract (the field removal that this docs cleanup is a follow-up to)
• Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control #255 — Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control (the originating decision)
• docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials #249 — docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials (the rebuild that re-introduced the now-stale references)

Revision notes

• Revision 1 → 2 (2ed56fb → 1822515): original R3 approach removed all 12 max_budget_usd references and rewrote budgets.md abstractly. Per operator review, restored one canonical Troubleshooting subsection on docs/configuration/budgets.md naming the field in the rejection context. Rationale: preserves discoverability for the 400-rejection error users hit when migrating Cloud-style configs to standalone. Other 5 files's R3 removals remain.
• Revision 3 → 4 (a8cb07e → 7aa99ce): Pass-1.5 verification surfaced that max_budget_usd doesn't exist as a field name on AISIX-Cloud's admin API surface either (Cloud uses limit_cents int64; verified no max_budget_usd in Go source, OpenAPI, or YAML/JSON specs). The canonical Troubleshooting subsection added in revision 2 (1822515) asserted "managed-mode field implemented in AISIX Cloud's control plane" — that assertion is empirically false. Operator pivoted from Option δ → pure R1 (full removal). The Troubleshooting subsection deleted entirely.
• Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. The field name does not appear anywhere in OSS docs.

Summary by CodeRabbit

• Documentation
  • Clarified that standalone deployments do not enforce per-key budgets by default (budget client disabled/allow-all) and removed prior contradictory validation notes.
  • Added guidance to drop per-key budget fields from standalone admin write payloads.
  • Updated errors to include HTTP 429 billing_error for budget-exceeded responses.
  • Clarified model access control: empty list denies; wildcard "*" allows.

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: d1a7b917-704c-4c46-ba5e-9fd0fa88e87d

📥 Commits

Reviewing files that changed from the base of the PR and between a8cb07e and 7aa99ce.

📒 Files selected for processing (1)

• docs/configuration/budgets.md

💤 Files with no reviewable changes (1)

• docs/configuration/budgets.md

---

📝 Walkthrough

Walkthrough

This PR updates documentation to clarify that standalone deployments default to a disabled, allow-all budget client (removing prior max_budget_usd caveats), documents that managed deployments enforce per-key budgets via a budget controller (with 429 budget_exceeded), and adds allowed_models access semantics.

Changes

Budget enforcement and access control documentation clarification

Layer / File(s)	Summary
Standalone budget behavior clarification docs/configuration/api-keys.md, docs/configuration/budgets.md, docs/reference/resource-schemas.md	Removes the misleading caveat that max_budget_usd appears in the ApiKey schema/OpenAPI but is rejected by the standalone admin write validator. Replaces with statements that standalone deployments default to a disabled budget client with allow-all behavior and updates troubleshooting/migration guidance.
Managed budget enforcement documentation docs/integration/errors-and-retries.md, docs/overview/feature-matrix.md	Clarifies that per-key budget enforcement is performed by the managed data-plane budget controller. Updates error docs to attribute 429 billing_error with code: "budget_exceeded" to the managed budget controller and notes enforcement differences in the feature matrix.
API Key allowed_models access control docs/overview/core-concepts.md	Adds explicit access-control contract: empty allowed_models denies all models; wildcard "*" allows all models within the applicable scope. Replaces prior budget-path phrasing with model-access semantics.

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

Note

🎁 Summarized by CodeRabbit Free

Your organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.If you believe this is a mistake and have available seats, please assign one to the pull request author through the subscription management page using the link above.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR removes standalone documentation references to max_budget_usd, aligning the docs with the current standalone admin contract where that managed-only field is not exposed.

Changes:

• Removes stale max_budget_usd references from API key, schema, budget, feature-matrix, and error docs.
• Reframes budget enforcement as managed-control-plane driven, with standalone defaulting to allow-all budget behavior.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
docs/reference/resource-schemas.md	Removes the stale schema-boundary example for max_budget_usd.
docs/overview/feature-matrix.md	Updates per-key budget limitations to describe standalone vs managed behavior.
docs/overview/core-concepts.md	Removes managed budget field caveat from API key concepts.
docs/integration/errors-and-retries.md	Rewords budget-related 429 trigger text.
docs/configuration/budgets.md	Removes field-specific guidance and rewrites standalone budget troubleshooting.
docs/configuration/api-keys.md	Removes standalone write-contract warning for the removed field.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

[janiussyafiq]

Summary

Remove all 12 customer-facing references to max_budget_usd from the docs. The field name does not exist as an OSS standalone ApiKey schema field (PR #259 removed it; StandaloneApiKeyBody rejects unknown fields). Pass-1.5 verification (see Revision notes) confirmed it also does not exist on AISIX-Cloud's admin API surface — Cloud uses limit_cents int64 internally. Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. See Revision notes below for the multi-pivot history.

Changes

File	Change
docs/integration/errors-and-retries.md	429 row rationale: Budget rejection from the ApiKey's max_budget_usd → Budget rejection from the managed budget controller
docs/reference/resource-schemas.md	Remove the Runtime Versus Schema Boundary example bullet about the typed model / OpenAPI / write validator inconsistency
docs/configuration/api-keys.md	Drop the Budget Boundary bullet about the write validator rejecting the field + the trailing "Do not treat ... as part of the verified standalone admin write contract" advisory
docs/configuration/budgets.md	Remove the intro line; drop the Managed Versus Standalone "Because of that boundary..." sentence and the typed/OpenAPI + write validator bullets; remove the A standalone deployment ignores max_budget_usd troubleshooting subsection (no replacement). Final state: no max_budget_usd mentions on this page. See Revision notes for pivot history.
docs/overview/core-concepts.md	Remove the trailing sentence "Managed budget paths may also reference per-key budget state, but max_budget_usd is not part of the current verified standalone admin write contract"
docs/overview/feature-matrix.md	"Per-key budgets" row rationale: replace mention of the rejected field with "standalone deployments do not enforce per-key budgets; managed deployments enforce via the budget controller"

Net diff: 6 files, +4 / -21, no .rs / schema / config / test files touched.

Test plan

• grep -rn 'max_budget_usd' docs/ --include='*.md' after the edits returns 0 hits — confirms the field name does not appear anywhere in OSS docs.
• grep -rn 'max_budget_usd' crates/aisix-core/src/models/apikey.rs returns zero matches — confirms the field is genuinely absent from the OSS schema (this PR documents that absence; no code change required).
• cargo fmt --check — PASS (exit 0).
• cargo clippy --workspace --all-targets -- -D warnings — PASS (exit 0, no warnings, Finished dev profile [unoptimized + debuginfo] target(s) in 41.91s).
• cargo test --workspace — PASS (exit 0, all crate test suites green; no failures, 2 ignored).
• E2E: grep -rln <each affected page> tests/e2e/ returns empty for all 6 pages — no e2e fixture references them, pnpm test not applicable.

References

• Closesdocs: remove max_budget_usd references from standalone docs (managed-only field) #295
• fix(admin): drop standalone max_budget_usd contract #259 — fix(admin): drop standalone max_budget_usd contract (the field removal that this docs cleanup is a follow-up to)
• Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control #255 — Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control (the originating decision)
• docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials #249 — docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials (the rebuild that re-introduced the now-stale references)

Revision notes

• Revision 1 → 2 (2ed56fb → 1822515): original R3 approach removed all 12 max_budget_usd references and rewrote budgets.md abstractly. Per operator review, restored one canonical Troubleshooting subsection on docs/configuration/budgets.md naming the field in the rejection context. Rationale: preserves discoverability for the 400-rejection error users hit when migrating Cloud-style configs to standalone. Other 5 files's R3 removals remain.
• Revision 3 → 4 (a8cb07e → 7aa99ce): Pass-1.5 verification surfaced that max_budget_usd doesn't exist as a field name on AISIX-Cloud's admin API surface either (Cloud uses limit_cents int64; verified no max_budget_usd in Go source, OpenAPI, or YAML/JSON specs). The canonical Troubleshooting subsection added in revision 2 (1822515) asserted "managed-mode field implemented in AISIX Cloud's control plane" — that assertion is empirically false. Operator pivoted from Option δ → pure R1 (full removal). The Troubleshooting subsection deleted entirely.
• Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. The field name does not appear anywhere in OSS docs.

Summary by CodeRabbit

• Documentation
  • Clarified that standalone deployments do not enforce per-key budgets by default (budget client disabled/allow-all) and removed prior contradictory validation notes.
  • Added guidance to drop per-key budget fields from standalone admin write payloads.
  • Updated errors to include HTTP 429 billing_error for budget-exceeded responses.
  • Clarified model access control: empty list denies; wildcard "*" allows.

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: d1a7b917-704c-4c46-ba5e-9fd0fa88e87d

📥 Commits

Reviewing files that changed from the base of the PR and between a8cb07e and 7aa99ce.

📒 Files selected for processing (1)

• docs/configuration/budgets.md

💤 Files with no reviewable changes (1)

• docs/configuration/budgets.md

---

📝 Walkthrough

Walkthrough

This PR updates documentation to clarify that standalone deployments default to a disabled, allow-all budget client (removing prior max_budget_usd caveats), documents that managed deployments enforce per-key budgets via a budget controller (with 429 budget_exceeded), and adds allowed_models access semantics.

Changes

Budget enforcement and access control documentation clarification

Layer / File(s)	Summary
Standalone budget behavior clarification docs/configuration/api-keys.md, docs/configuration/budgets.md, docs/reference/resource-schemas.md	Removes the misleading caveat that max_budget_usd appears in the ApiKey schema/OpenAPI but is rejected by the standalone admin write validator. Replaces with statements that standalone deployments default to a disabled budget client with allow-all behavior and updates troubleshooting/migration guidance.
Managed budget enforcement documentation docs/integration/errors-and-retries.md, docs/overview/feature-matrix.md	Clarifies that per-key budget enforcement is performed by the managed data-plane budget controller. Updates error docs to attribute 429 billing_error with code: "budget_exceeded" to the managed budget controller and notes enforcement differences in the feature matrix.
API Key allowed_models access control docs/overview/core-concepts.md	Adds explicit access-control contract: empty allowed_models denies all models; wildcard "*" allows all models within the applicable scope. Replaces prior budget-path phrasing with model-access semantics.

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

Note

🎁 Summarized by CodeRabbit Free

Your organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.If you believe this is a mistake and have available seats, please assign one to the pull request author through the subscription management page using the link above.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR removes standalone documentation references to max_budget_usd, aligning the docs with the current standalone admin contract where that managed-only field is not exposed.

Changes:

• Removes stale max_budget_usd references from API key, schema, budget, feature-matrix, and error docs.
• Reframes budget enforcement as managed-control-plane driven, with standalone defaulting to allow-all budget behavior.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
docs/reference/resource-schemas.md	Removes the stale schema-boundary example for max_budget_usd.
docs/overview/feature-matrix.md	Updates per-key budget limitations to describe standalone vs managed behavior.
docs/overview/core-concepts.md	Removes managed budget field caveat from API key concepts.
docs/integration/errors-and-retries.md	Rewords budget-related 429 trigger text.
docs/configuration/budgets.md	Removes field-specific guidance and rewrites standalone budget troubleshooting.
docs/configuration/api-keys.md	Removes standalone write-contract warning for the removed field.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

[janiussyafiq]

Summary

Remove all 12 customer-facing references to max_budget_usd from the docs. The field name does not exist as an OSS standalone ApiKey schema field (PR #259 removed it; StandaloneApiKeyBody rejects unknown fields). Pass-1.5 verification (see Revision notes) confirmed it also does not exist on AISIX-Cloud's admin API surface — Cloud uses limit_cents int64 internally. Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. See Revision notes below for the multi-pivot history.

Changes

File	Change
docs/integration/errors-and-retries.md	429 row rationale: Budget rejection from the ApiKey's max_budget_usd → Budget rejection from the managed budget controller
docs/reference/resource-schemas.md	Remove the Runtime Versus Schema Boundary example bullet about the typed model / OpenAPI / write validator inconsistency
docs/configuration/api-keys.md	Drop the Budget Boundary bullet about the write validator rejecting the field + the trailing "Do not treat ... as part of the verified standalone admin write contract" advisory
docs/configuration/budgets.md	Remove the intro line; drop the Managed Versus Standalone "Because of that boundary..." sentence and the typed/OpenAPI + write validator bullets; remove the A standalone deployment ignores max_budget_usd troubleshooting subsection (no replacement). Final state: no max_budget_usd mentions on this page. See Revision notes for pivot history.
docs/overview/core-concepts.md	Remove the trailing sentence "Managed budget paths may also reference per-key budget state, but max_budget_usd is not part of the current verified standalone admin write contract"
docs/overview/feature-matrix.md	"Per-key budgets" row rationale: replace mention of the rejected field with "standalone deployments do not enforce per-key budgets; managed deployments enforce via the budget controller"

Net diff: 6 files, +4 / -21, no .rs / schema / config / test files touched.

Test plan

• grep -rn 'max_budget_usd' docs/ --include='*.md' after the edits returns 0 hits — confirms the field name does not appear anywhere in OSS docs.
• grep -rn 'max_budget_usd' crates/aisix-core/src/models/apikey.rs returns zero matches — confirms the field is genuinely absent from the OSS schema (this PR documents that absence; no code change required).
• cargo fmt --check — PASS (exit 0).
• cargo clippy --workspace --all-targets -- -D warnings — PASS (exit 0, no warnings, Finished dev profile [unoptimized + debuginfo] target(s) in 41.91s).
• cargo test --workspace — PASS (exit 0, all crate test suites green; no failures, 2 ignored).
• E2E: grep -rln <each affected page> tests/e2e/ returns empty for all 6 pages — no e2e fixture references them, pnpm test not applicable.

References

• Closesdocs: remove max_budget_usd references from standalone docs (managed-only field) #295
• fix(admin): drop standalone max_budget_usd contract #259 — fix(admin): drop standalone max_budget_usd contract (the field removal that this docs cleanup is a follow-up to)
• Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control #255 — Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control (the originating decision)
• docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials #249 — docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials (the rebuild that re-introduced the now-stale references)

Revision notes

• Revision 1 → 2 (2ed56fb → 1822515): original R3 approach removed all 12 max_budget_usd references and rewrote budgets.md abstractly. Per operator review, restored one canonical Troubleshooting subsection on docs/configuration/budgets.md naming the field in the rejection context. Rationale: preserves discoverability for the 400-rejection error users hit when migrating Cloud-style configs to standalone. Other 5 files's R3 removals remain.
• Revision 3 → 4 (a8cb07e → 7aa99ce): Pass-1.5 verification surfaced that max_budget_usd doesn't exist as a field name on AISIX-Cloud's admin API surface either (Cloud uses limit_cents int64; verified no max_budget_usd in Go source, OpenAPI, or YAML/JSON specs). The canonical Troubleshooting subsection added in revision 2 (1822515) asserted "managed-mode field implemented in AISIX Cloud's control plane" — that assertion is empirically false. Operator pivoted from Option δ → pure R1 (full removal). The Troubleshooting subsection deleted entirely.
• Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. The field name does not appear anywhere in OSS docs.

Summary by CodeRabbit

• Documentation
  • Clarified that standalone deployments do not enforce per-key budgets by default (budget client disabled/allow-all) and removed prior contradictory validation notes.
  • Added guidance to drop per-key budget fields from standalone admin write payloads.
  • Updated errors to include HTTP 429 billing_error for budget-exceeded responses.
  • Clarified model access control: empty list denies; wildcard "*" allows.

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: d1a7b917-704c-4c46-ba5e-9fd0fa88e87d

📥 Commits

Reviewing files that changed from the base of the PR and between a8cb07e and 7aa99ce.

📒 Files selected for processing (1)

• docs/configuration/budgets.md

💤 Files with no reviewable changes (1)

• docs/configuration/budgets.md

---

📝 Walkthrough

Walkthrough

This PR updates documentation to clarify that standalone deployments default to a disabled, allow-all budget client (removing prior max_budget_usd caveats), documents that managed deployments enforce per-key budgets via a budget controller (with 429 budget_exceeded), and adds allowed_models access semantics.

Changes

Budget enforcement and access control documentation clarification

Layer / File(s)	Summary
Standalone budget behavior clarification docs/configuration/api-keys.md, docs/configuration/budgets.md, docs/reference/resource-schemas.md	Removes the misleading caveat that max_budget_usd appears in the ApiKey schema/OpenAPI but is rejected by the standalone admin write validator. Replaces with statements that standalone deployments default to a disabled budget client with allow-all behavior and updates troubleshooting/migration guidance.
Managed budget enforcement documentation docs/integration/errors-and-retries.md, docs/overview/feature-matrix.md	Clarifies that per-key budget enforcement is performed by the managed data-plane budget controller. Updates error docs to attribute 429 billing_error with code: "budget_exceeded" to the managed budget controller and notes enforcement differences in the feature matrix.
API Key allowed_models access control docs/overview/core-concepts.md	Adds explicit access-control contract: empty allowed_models denies all models; wildcard "*" allows all models within the applicable scope. Replaces prior budget-path phrasing with model-access semantics.

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

Note

🎁 Summarized by CodeRabbit Free

Your organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.If you believe this is a mistake and have available seats, please assign one to the pull request author through the subscription management page using the link above.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR removes standalone documentation references to max_budget_usd, aligning the docs with the current standalone admin contract where that managed-only field is not exposed.

Changes:

• Removes stale max_budget_usd references from API key, schema, budget, feature-matrix, and error docs.
• Reframes budget enforcement as managed-control-plane driven, with standalone defaulting to allow-all budget behavior.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
docs/reference/resource-schemas.md	Removes the stale schema-boundary example for max_budget_usd.
docs/overview/feature-matrix.md	Updates per-key budget limitations to describe standalone vs managed behavior.
docs/overview/core-concepts.md	Removes managed budget field caveat from API key concepts.
docs/integration/errors-and-retries.md	Rewords budget-related 429 trigger text.
docs/configuration/budgets.md	Removes field-specific guidance and rewrites standalone budget troubleshooting.
docs/configuration/api-keys.md	Removes standalone write-contract warning for the removed field.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

[janiussyafiq]

Summary

Remove all 12 customer-facing references to max_budget_usd from the docs. The field name does not exist as an OSS standalone ApiKey schema field (PR #259 removed it; StandaloneApiKeyBody rejects unknown fields). Pass-1.5 verification (see Revision notes) confirmed it also does not exist on AISIX-Cloud's admin API surface — Cloud uses limit_cents int64 internally. Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. See Revision notes below for the multi-pivot history.

Changes

File	Change
docs/integration/errors-and-retries.md	429 row rationale: Budget rejection from the ApiKey's max_budget_usd → Budget rejection from the managed budget controller
docs/reference/resource-schemas.md	Remove the Runtime Versus Schema Boundary example bullet about the typed model / OpenAPI / write validator inconsistency
docs/configuration/api-keys.md	Drop the Budget Boundary bullet about the write validator rejecting the field + the trailing "Do not treat ... as part of the verified standalone admin write contract" advisory
docs/configuration/budgets.md	Remove the intro line; drop the Managed Versus Standalone "Because of that boundary..." sentence and the typed/OpenAPI + write validator bullets; remove the A standalone deployment ignores max_budget_usd troubleshooting subsection (no replacement). Final state: no max_budget_usd mentions on this page. See Revision notes for pivot history.
docs/overview/core-concepts.md	Remove the trailing sentence "Managed budget paths may also reference per-key budget state, but max_budget_usd is not part of the current verified standalone admin write contract"
docs/overview/feature-matrix.md	"Per-key budgets" row rationale: replace mention of the rejected field with "standalone deployments do not enforce per-key budgets; managed deployments enforce via the budget controller"

Net diff: 6 files, +4 / -21, no .rs / schema / config / test files touched.

Test plan

• grep -rn 'max_budget_usd' docs/ --include='*.md' after the edits returns 0 hits — confirms the field name does not appear anywhere in OSS docs.
• grep -rn 'max_budget_usd' crates/aisix-core/src/models/apikey.rs returns zero matches — confirms the field is genuinely absent from the OSS schema (this PR documents that absence; no code change required).
• cargo fmt --check — PASS (exit 0).
• cargo clippy --workspace --all-targets -- -D warnings — PASS (exit 0, no warnings, Finished dev profile [unoptimized + debuginfo] target(s) in 41.91s).
• cargo test --workspace — PASS (exit 0, all crate test suites green; no failures, 2 ignored).
• E2E: grep -rln <each affected page> tests/e2e/ returns empty for all 6 pages — no e2e fixture references them, pnpm test not applicable.

References

• Closesdocs: remove max_budget_usd references from standalone docs (managed-only field) #295
• fix(admin): drop standalone max_budget_usd contract #259 — fix(admin): drop standalone max_budget_usd contract (the field removal that this docs cleanup is a follow-up to)
• Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control #255 — Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control (the originating decision)
• docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials #249 — docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials (the rebuild that re-introduced the now-stale references)

Revision notes

• Revision 1 → 2 (2ed56fb → 1822515): original R3 approach removed all 12 max_budget_usd references and rewrote budgets.md abstractly. Per operator review, restored one canonical Troubleshooting subsection on docs/configuration/budgets.md naming the field in the rejection context. Rationale: preserves discoverability for the 400-rejection error users hit when migrating Cloud-style configs to standalone. Other 5 files's R3 removals remain.
• Revision 3 → 4 (a8cb07e → 7aa99ce): Pass-1.5 verification surfaced that max_budget_usd doesn't exist as a field name on AISIX-Cloud's admin API surface either (Cloud uses limit_cents int64; verified no max_budget_usd in Go source, OpenAPI, or YAML/JSON specs). The canonical Troubleshooting subsection added in revision 2 (1822515) asserted "managed-mode field implemented in AISIX Cloud's control plane" — that assertion is empirically false. Operator pivoted from Option δ → pure R1 (full removal). The Troubleshooting subsection deleted entirely.
• Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. The field name does not appear anywhere in OSS docs.

Summary by CodeRabbit

• Documentation
  • Clarified that standalone deployments do not enforce per-key budgets by default (budget client disabled/allow-all) and removed prior contradictory validation notes.
  • Added guidance to drop per-key budget fields from standalone admin write payloads.
  • Updated errors to include HTTP 429 billing_error for budget-exceeded responses.
  • Clarified model access control: empty list denies; wildcard "*" allows.

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: d1a7b917-704c-4c46-ba5e-9fd0fa88e87d

📥 Commits

Reviewing files that changed from the base of the PR and between a8cb07e and 7aa99ce.

📒 Files selected for processing (1)

• docs/configuration/budgets.md

💤 Files with no reviewable changes (1)

• docs/configuration/budgets.md

---

📝 Walkthrough

Walkthrough

This PR updates documentation to clarify that standalone deployments default to a disabled, allow-all budget client (removing prior max_budget_usd caveats), documents that managed deployments enforce per-key budgets via a budget controller (with 429 budget_exceeded), and adds allowed_models access semantics.

Changes

Budget enforcement and access control documentation clarification

Layer / File(s)	Summary
Standalone budget behavior clarification docs/configuration/api-keys.md, docs/configuration/budgets.md, docs/reference/resource-schemas.md	Removes the misleading caveat that max_budget_usd appears in the ApiKey schema/OpenAPI but is rejected by the standalone admin write validator. Replaces with statements that standalone deployments default to a disabled budget client with allow-all behavior and updates troubleshooting/migration guidance.
Managed budget enforcement documentation docs/integration/errors-and-retries.md, docs/overview/feature-matrix.md	Clarifies that per-key budget enforcement is performed by the managed data-plane budget controller. Updates error docs to attribute 429 billing_error with code: "budget_exceeded" to the managed budget controller and notes enforcement differences in the feature matrix.
API Key allowed_models access control docs/overview/core-concepts.md	Adds explicit access-control contract: empty allowed_models denies all models; wildcard "*" allows all models within the applicable scope. Replaces prior budget-path phrasing with model-access semantics.

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

Note

🎁 Summarized by CodeRabbit Free

Your organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.If you believe this is a mistake and have available seats, please assign one to the pull request author through the subscription management page using the link above.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR removes standalone documentation references to max_budget_usd, aligning the docs with the current standalone admin contract where that managed-only field is not exposed.

Changes:

• Removes stale max_budget_usd references from API key, schema, budget, feature-matrix, and error docs.
• Reframes budget enforcement as managed-control-plane driven, with standalone defaulting to allow-all budget behavior.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
docs/reference/resource-schemas.md	Removes the stale schema-boundary example for max_budget_usd.
docs/overview/feature-matrix.md	Updates per-key budget limitations to describe standalone vs managed behavior.
docs/overview/core-concepts.md	Removes managed budget field caveat from API key concepts.
docs/integration/errors-and-retries.md	Rewords budget-related 429 trigger text.
docs/configuration/budgets.md	Removes field-specific guidance and rewrites standalone budget troubleshooting.
docs/configuration/api-keys.md	Removes standalone write-contract warning for the removed field.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

[janiussyafiq]

Summary

Remove all 12 customer-facing references to max_budget_usd from the docs. The field name does not exist as an OSS standalone ApiKey schema field (PR #259 removed it; StandaloneApiKeyBody rejects unknown fields). Pass-1.5 verification (see Revision notes) confirmed it also does not exist on AISIX-Cloud's admin API surface — Cloud uses limit_cents int64 internally. Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. See Revision notes below for the multi-pivot history.

Changes

File	Change
docs/integration/errors-and-retries.md	429 row rationale: Budget rejection from the ApiKey's max_budget_usd → Budget rejection from the managed budget controller
docs/reference/resource-schemas.md	Remove the Runtime Versus Schema Boundary example bullet about the typed model / OpenAPI / write validator inconsistency
docs/configuration/api-keys.md	Drop the Budget Boundary bullet about the write validator rejecting the field + the trailing "Do not treat ... as part of the verified standalone admin write contract" advisory
docs/configuration/budgets.md	Remove the intro line; drop the Managed Versus Standalone "Because of that boundary..." sentence and the typed/OpenAPI + write validator bullets; remove the A standalone deployment ignores max_budget_usd troubleshooting subsection (no replacement). Final state: no max_budget_usd mentions on this page. See Revision notes for pivot history.
docs/overview/core-concepts.md	Remove the trailing sentence "Managed budget paths may also reference per-key budget state, but max_budget_usd is not part of the current verified standalone admin write contract"
docs/overview/feature-matrix.md	"Per-key budgets" row rationale: replace mention of the rejected field with "standalone deployments do not enforce per-key budgets; managed deployments enforce via the budget controller"

Net diff: 6 files, +4 / -21, no .rs / schema / config / test files touched.

Test plan

• grep -rn 'max_budget_usd' docs/ --include='*.md' after the edits returns 0 hits — confirms the field name does not appear anywhere in OSS docs.
• grep -rn 'max_budget_usd' crates/aisix-core/src/models/apikey.rs returns zero matches — confirms the field is genuinely absent from the OSS schema (this PR documents that absence; no code change required).
• cargo fmt --check — PASS (exit 0).
• cargo clippy --workspace --all-targets -- -D warnings — PASS (exit 0, no warnings, Finished dev profile [unoptimized + debuginfo] target(s) in 41.91s).
• cargo test --workspace — PASS (exit 0, all crate test suites green; no failures, 2 ignored).
• E2E: grep -rln <each affected page> tests/e2e/ returns empty for all 6 pages — no e2e fixture references them, pnpm test not applicable.

References

• Closesdocs: remove max_budget_usd references from standalone docs (managed-only field) #295
• fix(admin): drop standalone max_budget_usd contract #259 — fix(admin): drop standalone max_budget_usd contract (the field removal that this docs cleanup is a follow-up to)
• Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control #255 — Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control (the originating decision)
• docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials #249 — docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials (the rebuild that re-introduced the now-stale references)

Revision notes

• Revision 1 → 2 (2ed56fb → 1822515): original R3 approach removed all 12 max_budget_usd references and rewrote budgets.md abstractly. Per operator review, restored one canonical Troubleshooting subsection on docs/configuration/budgets.md naming the field in the rejection context. Rationale: preserves discoverability for the 400-rejection error users hit when migrating Cloud-style configs to standalone. Other 5 files's R3 removals remain.
• Revision 3 → 4 (a8cb07e → 7aa99ce): Pass-1.5 verification surfaced that max_budget_usd doesn't exist as a field name on AISIX-Cloud's admin API surface either (Cloud uses limit_cents int64; verified no max_budget_usd in Go source, OpenAPI, or YAML/JSON specs). The canonical Troubleshooting subsection added in revision 2 (1822515) asserted "managed-mode field implemented in AISIX Cloud's control plane" — that assertion is empirically false. Operator pivoted from Option δ → pure R1 (full removal). The Troubleshooting subsection deleted entirely.
• Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. The field name does not appear anywhere in OSS docs.

Summary by CodeRabbit

• Documentation
  • Clarified that standalone deployments do not enforce per-key budgets by default (budget client disabled/allow-all) and removed prior contradictory validation notes.
  • Added guidance to drop per-key budget fields from standalone admin write payloads.
  • Updated errors to include HTTP 429 billing_error for budget-exceeded responses.
  • Clarified model access control: empty list denies; wildcard "*" allows.

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: d1a7b917-704c-4c46-ba5e-9fd0fa88e87d

📥 Commits

Reviewing files that changed from the base of the PR and between a8cb07e and 7aa99ce.

📒 Files selected for processing (1)

• docs/configuration/budgets.md

💤 Files with no reviewable changes (1)

• docs/configuration/budgets.md

---

📝 Walkthrough

Walkthrough

This PR updates documentation to clarify that standalone deployments default to a disabled, allow-all budget client (removing prior max_budget_usd caveats), documents that managed deployments enforce per-key budgets via a budget controller (with 429 budget_exceeded), and adds allowed_models access semantics.

Changes

Budget enforcement and access control documentation clarification

Layer / File(s)	Summary
Standalone budget behavior clarification docs/configuration/api-keys.md, docs/configuration/budgets.md, docs/reference/resource-schemas.md	Removes the misleading caveat that max_budget_usd appears in the ApiKey schema/OpenAPI but is rejected by the standalone admin write validator. Replaces with statements that standalone deployments default to a disabled budget client with allow-all behavior and updates troubleshooting/migration guidance.
Managed budget enforcement documentation docs/integration/errors-and-retries.md, docs/overview/feature-matrix.md	Clarifies that per-key budget enforcement is performed by the managed data-plane budget controller. Updates error docs to attribute 429 billing_error with code: "budget_exceeded" to the managed budget controller and notes enforcement differences in the feature matrix.
API Key allowed_models access control docs/overview/core-concepts.md	Adds explicit access-control contract: empty allowed_models denies all models; wildcard "*" allows all models within the applicable scope. Replaces prior budget-path phrasing with model-access semantics.

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

Note

🎁 Summarized by CodeRabbit Free

Your organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.If you believe this is a mistake and have available seats, please assign one to the pull request author through the subscription management page using the link above.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR removes standalone documentation references to max_budget_usd, aligning the docs with the current standalone admin contract where that managed-only field is not exposed.

Changes:

• Removes stale max_budget_usd references from API key, schema, budget, feature-matrix, and error docs.
• Reframes budget enforcement as managed-control-plane driven, with standalone defaulting to allow-all budget behavior.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
docs/reference/resource-schemas.md	Removes the stale schema-boundary example for max_budget_usd.
docs/overview/feature-matrix.md	Updates per-key budget limitations to describe standalone vs managed behavior.
docs/overview/core-concepts.md	Removes managed budget field caveat from API key concepts.
docs/integration/errors-and-retries.md	Rewords budget-related 429 trigger text.
docs/configuration/budgets.md	Removes field-specific guidance and rewrites standalone budget troubleshooting.
docs/configuration/api-keys.md	Removes standalone write-contract warning for the removed field.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.

[janiussyafiq]

Summary

Remove all 12 customer-facing references to max_budget_usd from the docs. The field name does not exist as an OSS standalone ApiKey schema field (PR #259 removed it; StandaloneApiKeyBody rejects unknown fields). Pass-1.5 verification (see Revision notes) confirmed it also does not exist on AISIX-Cloud's admin API surface — Cloud uses limit_cents int64 internally. Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. See Revision notes below for the multi-pivot history.

Changes

File	Change
docs/integration/errors-and-retries.md	429 row rationale: Budget rejection from the ApiKey's max_budget_usd → Budget rejection from the managed budget controller
docs/reference/resource-schemas.md	Remove the Runtime Versus Schema Boundary example bullet about the typed model / OpenAPI / write validator inconsistency
docs/configuration/api-keys.md	Drop the Budget Boundary bullet about the write validator rejecting the field + the trailing "Do not treat ... as part of the verified standalone admin write contract" advisory
docs/configuration/budgets.md	Remove the intro line; drop the Managed Versus Standalone "Because of that boundary..." sentence and the typed/OpenAPI + write validator bullets; remove the A standalone deployment ignores max_budget_usd troubleshooting subsection (no replacement). Final state: no max_budget_usd mentions on this page. See Revision notes for pivot history.
docs/overview/core-concepts.md	Remove the trailing sentence "Managed budget paths may also reference per-key budget state, but max_budget_usd is not part of the current verified standalone admin write contract"
docs/overview/feature-matrix.md	"Per-key budgets" row rationale: replace mention of the rejected field with "standalone deployments do not enforce per-key budgets; managed deployments enforce via the budget controller"

Net diff: 6 files, +4 / -21, no .rs / schema / config / test files touched.

Test plan

• grep -rn 'max_budget_usd' docs/ --include='*.md' after the edits returns 0 hits — confirms the field name does not appear anywhere in OSS docs.
• grep -rn 'max_budget_usd' crates/aisix-core/src/models/apikey.rs returns zero matches — confirms the field is genuinely absent from the OSS schema (this PR documents that absence; no code change required).
• cargo fmt --check — PASS (exit 0).
• cargo clippy --workspace --all-targets -- -D warnings — PASS (exit 0, no warnings, Finished dev profile [unoptimized + debuginfo] target(s) in 41.91s).
• cargo test --workspace — PASS (exit 0, all crate test suites green; no failures, 2 ignored).
• E2E: grep -rln <each affected page> tests/e2e/ returns empty for all 6 pages — no e2e fixture references them, pnpm test not applicable.

References

• Closesdocs: remove max_budget_usd references from standalone docs (managed-only field) #295
• fix(admin): drop standalone max_budget_usd contract #259 — fix(admin): drop standalone max_budget_usd contract (the field removal that this docs cleanup is a follow-up to)
• Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control #255 — Remove max_budget_usd from standalone AISIX admin contract without breaking SaaS CP budget control (the originating decision)
• docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials #249 — docs: rebuild customer-facing docs across overview, config, cloud, ops, reference, and tutorials (the rebuild that re-introduced the now-stale references)

Revision notes

• Revision 1 → 2 (2ed56fb → 1822515): original R3 approach removed all 12 max_budget_usd references and rewrote budgets.md abstractly. Per operator review, restored one canonical Troubleshooting subsection on docs/configuration/budgets.md naming the field in the rejection context. Rationale: preserves discoverability for the 400-rejection error users hit when migrating Cloud-style configs to standalone. Other 5 files's R3 removals remain.
• Revision 3 → 4 (a8cb07e → 7aa99ce): Pass-1.5 verification surfaced that max_budget_usd doesn't exist as a field name on AISIX-Cloud's admin API surface either (Cloud uses limit_cents int64; verified no max_budget_usd in Go source, OpenAPI, or YAML/JSON specs). The canonical Troubleshooting subsection added in revision 2 (1822515) asserted "managed-mode field implemented in AISIX Cloud's control plane" — that assertion is empirically false. Operator pivoted from Option δ → pure R1 (full removal). The Troubleshooting subsection deleted entirely.
• Final state: grep -rn 'max_budget_usd' docs/ returns 0 hits. The field name does not appear anywhere in OSS docs.

Summary by CodeRabbit

• Documentation
  • Clarified that standalone deployments do not enforce per-key budgets by default (budget client disabled/allow-all) and removed prior contradictory validation notes.
  • Added guidance to drop per-key budget fields from standalone admin write payloads.
  • Updated errors to include HTTP 429 billing_error for budget-exceeded responses.
  • Clarified model access control: empty list denies; wildcard "*" allows.

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: d1a7b917-704c-4c46-ba5e-9fd0fa88e87d

📥 Commits

Reviewing files that changed from the base of the PR and between a8cb07e and 7aa99ce.

📒 Files selected for processing (1)

• docs/configuration/budgets.md

💤 Files with no reviewable changes (1)

• docs/configuration/budgets.md

---

📝 Walkthrough

Walkthrough

This PR updates documentation to clarify that standalone deployments default to a disabled, allow-all budget client (removing prior max_budget_usd caveats), documents that managed deployments enforce per-key budgets via a budget controller (with 429 budget_exceeded), and adds allowed_models access semantics.

Changes

Budget enforcement and access control documentation clarification

Layer / File(s)	Summary
Standalone budget behavior clarification docs/configuration/api-keys.md, docs/configuration/budgets.md, docs/reference/resource-schemas.md	Removes the misleading caveat that max_budget_usd appears in the ApiKey schema/OpenAPI but is rejected by the standalone admin write validator. Replaces with statements that standalone deployments default to a disabled budget client with allow-all behavior and updates troubleshooting/migration guidance.
Managed budget enforcement documentation docs/integration/errors-and-retries.md, docs/overview/feature-matrix.md	Clarifies that per-key budget enforcement is performed by the managed data-plane budget controller. Updates error docs to attribute 429 billing_error with code: "budget_exceeded" to the managed budget controller and notes enforcement differences in the feature matrix.
API Key allowed_models access control docs/overview/core-concepts.md	Adds explicit access-control contract: empty allowed_models denies all models; wildcard "*" allows all models within the applicable scope. Replaces prior budget-path phrasing with model-access semantics.

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

Note

🎁 Summarized by CodeRabbit Free

Your organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.If you believe this is a mistake and have available seats, please assign one to the pull request author through the subscription management page using the link above.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR removes standalone documentation references to max_budget_usd, aligning the docs with the current standalone admin contract where that managed-only field is not exposed.

Changes:

• Removes stale max_budget_usd references from API key, schema, budget, feature-matrix, and error docs.
• Reframes budget enforcement as managed-control-plane driven, with standalone defaulting to allow-all budget behavior.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
docs/reference/resource-schemas.md	Removes the stale schema-boundary example for max_budget_usd.
docs/overview/feature-matrix.md	Updates per-key budget limitations to describe standalone vs managed behavior.
docs/overview/core-concepts.md	Removes managed budget field caveat from API key concepts.
docs/integration/errors-and-retries.md	Rewords budget-related 429 trigger text.
docs/configuration/budgets.md	Removes field-specific guidance and rewrites standalone budget troubleshooting.
docs/configuration/api-keys.md	Removes standalone write-contract warning for the removed field.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.