Ai Openrouter Gateway Laravel Package

Product Decisions This Supports

• Developer-facing documentation experience (DX) as a product surface. v1.3.2 adds dark-mode rendering for the Scalar-based API reference, both on the standalone {prefix}/docs page and inside the panel-embedded "API docs" iframe. This is a UI/UX polish item, but it affects a surface your internal teams and integrating partners actually look at — theme-consistent docs reduce friction in demos, support, and onboarding.
• Configuration-over-code customization. The toggle is exposed via config('ai-gateway.api.docs.dark_mode') and the AI_GATEWAY_API_DOCS_DARK env var, defaulting to true. That supports a real PM decision: ship a sensible default for most deployments while letting brand-sensitive or light-theme-only products opt out without a fork. Low-cost knobs like this are cheap to support and reduce "can you change this for us" requests.
• Platform/framework lifecycle planning. The release explicitly states this is the Filament 3 line, and directs Filament 4/5 users to ^2.0 (v2.0.2). This is a first-class roadmap input: which Filament major version your admin panel runs determines which package line you adopt, and it implies parallel maintenance tracks rather than a single upgrade path.
• Build vs. buy for AI gateway plumbing. A package that bundles an AI gateway with auto-generated, browsable API reference reduces the need to hand-roll request routing plus an OpenAPI/Scalar docs pipeline. The dark-mode change is evidence of ongoing maintenance on the reference-docs layer specifically — a component teams routinely underestimate when building in-house.
• Use cases it enables: exposing an internal AI gateway to product teams with self-serve docs, publishing an API surface to partner integrators, embedding reference docs inside an existing Filament admin panel so engineers and stakeholders share one authenticated surface, and demoing AI capabilities without a separate docs site.
• Low blast radius for adoption. A visual/config-only change with a documented default means no migration work, no data model impact, and no behavior change to gateway routing — easy to slot into an in-flight release.

When to Consider This Package

Consider adopting when:

• You run a Filament 3 admin panel and want AI gateway capabilities with API documentation surfaced inside (or alongside) that panel rather than as a separate docs product.
• You need generated, browsable API reference (Scalar) with minimal bespoke work, and you want it themeable to match your product's light/dark UI.
• Your team values env/config-driven customization — the dark-mode toggle fits deployments that promote config through environment rather than code.
• You want a maintained dependency: the 1.3.x line is still receiving UX-level attention, which is a reasonable signal short of a formal support policy.

Look elsewhere or pause when:

• You are on Filament 4 or 5 — you must target ^2.0, so evaluate the v2 line separately; this release note tells you nothing about v2's feature parity.
• You need a framework-agnostic or non-Filament docs surface — the value here is partly the panel embedding, and a standalone docs generator may serve you better.
• Dark mode is your deciding factor. It is a cosmetic toggle, not a capability. If your evaluation hinges on this release, the package probably isn't the constraint you think it is.
• You require explicit stability/SLA guarantees. The release notes describe features and version lines but not deprecation policy, support windows, or breaking-change commitments — get those in writing before a production dependency.
• Your docs must be fully custom-branded or deeply interactive beyond Scalar's rendering model; expect to wrap or replace the docs layer.

How to Pitch It (Stakeholders)

For executives: This is a maintenance release on an existing Laravel/Filament package that provides an AI gateway with built-in, auto-generated API documentation. The change is small and low-risk — dark-mode styling for the documentation pages, controllable by a config flag with a safe default. The strategic point is not the toggle; it's that the package continues to be actively maintained on the Filament 3 line, and that a separate, current line (^2.0) exists for teams on Filament 4/5. Read this as a healthy maintenance signal, not a reason to re-platform.

For engineering: v1.3.2 is cosmetic and additive. Dark mode for the Scalar reference is on by default and can be disabled via config('ai-gateway.api.docs.dark_mode') or AI_GATEWAY_API_DOCS_DARK=false; it applies to both the standalone {prefix}/docs route and the panel-embedded iframe, so theming stays consistent. No migrations, no API contract changes, no action required to stay current. The one thing to record in your dependency notes: this is the Filament 3 track, and Filament 4/5 requires ^2.0 (currently v2.0.2) — pin accordingly and budget a line upgrade if a Filament major upgrade is on your roadmap.

Framing for the decision: adopt/keep on the Filament 3 line for its documentation DX and maintained status; treat the Filament 4/5 line split as an explicit roadmap item to validate (feature parity and support expectations) rather than an assumption.