No English page yet. Showing the Japanese source.
AI Gateway群
記事状態: 公開 · 最終確認: 未確認
要点
「AI Gateway群は、複数providerへの接続を集約し、routing／fallback、認証、rate limit、logging、cost、cache、policy等を実装するcontrol-plane群である。LiteLLM、OpenRouter、Vercel、Cloudflareの公式資料は機能境界が異なるため、共通機能と製品固有の実装・契約・版・地域・設定を分離して評価する。」
現在の判断
- ESTABLISHED [S1-S4 support]: The category consistently exposes a control-plane pattern—provider/model selection, request routing, and some combination of auth, logging, cost, limits, caching, fallback, or policy—but each product defines a different boundary.
- ESTABLISHED [S1 support]: LiteLLM documents self-hostable SDK/Proxy distinctions and multi-tenant spend/auth/logging/guardrail/cache/router features.
- ESTABLISHED [S2 support]: OpenRouter documents a managed normalized API with provider-dependent tool transformation and model allow/exclude/cost-tier routing.
- ESTABLISHED [S3 support]: Vercel documents managed credentials, provider/fallback routing, logs with provider attempts/latency/tokens/cost, budgets, access/data policies, BYOK, and OIDC for Vercel deployments; the same page says provider terms apply.
- ESTABLISHED [S4 support]: Cloudflare documents analytics/logging, caching, rate limiting, request retry, model fallback, and multiple provider integrations; its page records a current plan statement, which is still a product/plan gate.
- INFERENCE [S1-S4]: A gateway can centralize policy and observability, but a cross-product claim such as “gateway guarantees reliability, privacy, cost control, or provider equivalence” is not established by these feature lists. The gateway becomes an additional trust, transformation, outage, and audit boundary.
どこまで当てはまるか
Enterprise AI Core / provider mapping / gateway / governance / cost / observability / security / implementation
詳しく理解する
なぜ重要か
Enterprise AI gateway is a control-plane category rather than one universal product. A useful update must compare concrete gateway claims while keeping self-hosted OSS, managed routing, provider transformation, logging, budget, cache, and data-policy surfaces separate.
対象範囲と前提
Enterprise AI Core / provider mapping / gateway / governance / cost / observability / security / implementation
検討ポイント
Across LiteLLM, OpenRouter, Vercel AI Gateway, and Cloudflare AI Gateway, which gateway capabilities are directly documented, and which cross-product conclusions remain unproven?
EVIDENCE TABLE
[S1] SOURCE_CLASS: author_maintained_repo | EXACT_TITLE: BerriAI/litellm - LiteLLM repository | AUTHOR_ORG: BerriAI / LiteLLM maintainers | CANONICAL_URL: https://github.com/BerriAI/litellm | PUBLICATION_UPDATE_ACCESS: accessed 2026-09-14 00:16 JST | VERSION_RELEASE_TAG: default branch; unpinned | SUPPORTING_LOCATOR: lines 542-549 for Proxy/SDK, centralized auth, multi-tenant spend, logging/guardrails/caching, Router retry/fallback, stable-tag note | EVIDENCE_LABEL: OSS_PRACTICE + PRODUCT_VOLATILE | RELATION: support for LiteLLM's documented gateway surface; limit for release/provider parity. [S2] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: OpenRouter API Reference / Auto Router | AUTHOR_ORG: OpenRouter | CANONICAL_URL: https://openrouter.ai/docs/api_reference/overview and https://openrouter.ai/docs/guides/routing/routers/auto-router | PUBLICATION_UPDATE_ACCESS: accessed 2026-09-14 00:16 JST | VERSION_RELEASE_TAG: current docs; unpinned | SUPPORTING_LOCATOR: API normalization/tool transformation lines 25-36 and 75-81; model allow/exclude and cost-tier lines 450-487 | EVIDENCE_LABEL: PRODUCT_VOLATILE + VERIFIED_SPEC | RELATION: support for managed API/routing claims; limit for cross-provider equivalence. [S3] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: Vercel AI Gateway: Models, Routing, and Observability | AUTHOR_ORG: Vercel | CANONICAL_URL: https://vercel.com/docs/ai-gateway | PUBLICATION_UPDATE_ACCESS: current page accessed 2026-09-14 00:16 JST | VERSION_RELEASE_TAG: current docs; product/plan availability volatile | SUPPORTING_LOCATOR: lines 386-423 for managed gateway, provider/fallback routing, logs, latency/token/cost, budgets/access/data policies/BYOK; lines 426-433 for API key/OIDC and logging/budget controls | EVIDENCE_LABEL: VERIFIED_SPEC + PRODUCT_VOLATILE | RELATION: support for Vercel-specific control surface; limit for plan/terms/provider behavior. [S4] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: Cloudflare AI Gateway | AUTHOR_ORG: Cloudflare | CANONICAL_URL: https://developers.cloudflare.com/ai-gateway/ | PUBLICATION_UPDATE_ACCESS: last updated 2026-04-20; accessed 2026-09-14 00:16 JST | VERSION_RELEASE_TAG: current docs; page says available on all plans, subject to current product terms | SUPPORTING_LOCATOR: lines 138-147 for visibility/control; lines 157-182 for analytics, logging, caching, rate limiting, retry/fallback; lines 186-188 for provider examples | EVIDENCE_LABEL: VERIFIED_SPEC + PRODUCT_VOLATILE | RELATION: support for Cloudflare-specific controls; limit for actual configuration and provider parity.
利用できる条件
product and release/commit; self-hosted versus managed; plan/region; provider/model catalog; API transformation; credentials/BYOK/OIDC; routing/fallback/retry; budgets/rate limits; caching; logs/traces/audit export; retention/data residency; admin/RBAC; outage behavior; pricing/markup; contract/SLO.
実装・運用
Evidence-only desk research. No gateway was configured, authenticated, called, or compared with a live provider.
確認・評価方法
No cross-gateway conformance, latency, cost, fallback-duplication, transformation, privacy, or outage-recovery evaluation was run.
セキュリティとプライバシー
A gateway centralizes high-value secrets and high-sensitivity telemetry. Require route/provider attribution, request transformation record, policy decision, token/cost source, retry attempts, cache hit, redaction, retention, and downstream result. Treat gateway outage and misrouting as distinct failure modes from provider outage. Cost must include gateway, provider, retries, cache/storage, and operational review; not measured.
EVIDENCE PACKET
---
確認できていること
ESTABLISHED [S1-S4 support]: The category consistently exposes a control-plane pattern—provider/model selection, request routing, and some combination of auth, logging, cost, limits, caching, fallback, or policy—but each product defines a different boundary.
ESTABLISHED [S1 support]: LiteLLM documents self-hostable SDK/Proxy distinctions and multi-tenant spend/auth/logging/guardrail/cache/router features.
ESTABLISHED [S2 support]: OpenRouter documents a managed normalized API with provider-dependent tool transformation and model allow/exclude/cost-tier routing.
ESTABLISHED [S3 support]: Vercel documents managed credentials, provider/fallback routing, logs with provider attempts/latency/tokens/cost, budgets, access/data policies, BYOK, and OIDC for Vercel deployments; the same page says provider terms apply.
ESTABLISHED [S4 support]: Cloudflare documents analytics/logging, caching, rate limiting, request retry, model fallback, and multiple provider integrations; its page records a current plan statement, which is still a product/plan gate.
INFERENCE [S1-S4]: A gateway can centralize policy and observability, but a cross-product claim such as “gateway guarantees reliability, privacy, cost control, or provider equivalence” is not established by these feature lists. The gateway becomes an additional trust, transformation, outage, and audit boundary.
よくある失敗・反証
Feature-list overlap is not functional equivalence. Managed versus OSS deployment, release, plan, region, BYOK, provider contract, log retention, cache scope, route algorithm, retry semantics, transformed tool schemas, and audit export differ. Vendor pages do not prove independent latency, quality, privacy, or SLO. Fallback/retry may duplicate or alter requests. No cross-gateway benchmark or live call was run.
Do not merge LiteLLM OSS, OpenRouter managed API, Vercel managed gateway, and Cloudflare gateway into one product or one guarantee. Do not state that the presence of logs, budgets, fallback, or cache equals effective enforcement without configuration and negative testing. UNIT_CLOSE_STATUS: INDIVIDUAL_BOUNDED_CLOSE / EVIDENCE_RECORDED / UNKNOWN_PRESERVED
実務での使い方
product and release/commit; self-hosted versus managed; plan/region; provider/model catalog; API transformation; credentials/BYOK/OIDC; routing/fallback/retry; budgets/rate limits; caching; logs/traces/audit export; retention/data residency; admin/RBAC; outage behavior; pricing/markup; contract/SLO.
Evidence-only desk research. No gateway was configured, authenticated, called, or compared with a live provider.
No cross-gateway conformance, latency, cost, fallback-duplication, transformation, privacy, or outage-recovery evaluation was run.
A gateway centralizes high-value secrets and high-sensitivity telemetry. Require route/provider attribution, request transformation record, policy decision, token/cost source, retry attempts, cache hit, redaction, retention, and downstream result. Treat gateway outage and misrouting as distinct failure modes from provider outage. Cost must include gateway, provider, retries, cache/storage, and operational review; not measured.
Future update Work should build a four-product comparison matrix with pinned release/page dates and a safe read-only TEST_PROFILE: direct versus gateway output, provider attribution, schema/tool transformation, retry/fallback, rate/budget, cache isolation, logging/redaction, data policy, outage, and audit readback. No external side-effect tool should be enabled.
まだ確認できていないこと
- EA-166-UNKNOWN-01
neutral gateway semantics; cross-product interoperability; route determinism; tool/result transformation; cache privacy; budget enforcement; data residency; provider contract; markup; audit completeness; outage/fallback behavior; independent benchmark/SLO.
- EA-166-UNKNOWN-CURRENTNESS
外部根拠の再確認日がcanonical body/control-planeで確定していないため、currentnessはUNKNOWNとして保持する。日付を推測補完しない。
根拠資料
- 研究資料研究資料
LiteLLM repository | AUTHOR_ORG: BerriAI / LiteLLM maintainers | CANONICAL_URL:
確認上の限界
元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
- 研究資料研究資料
[S2] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: OpenRouter API Reference / Auto Router | AUTHOR_ORG: OpenRouter | CANONICAL_URL:
確認上の限界
元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
- 研究資料研究資料
[S2] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: OpenRouter API Reference / Auto Router | AUTHOR_ORG: OpenRouter | CANONICAL_URL: https://openrouter.ai/docs/api_reference/o
確認上の限界
元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
- 研究資料研究資料
[S3] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: Vercel AI Gateway: Models, Routing, and Observability | AUTHOR_ORG: Vercel | CANONICAL_URL:
確認上の限界
元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
- 研究資料研究資料
[S4] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: Cloudflare AI Gateway | AUTHOR_ORG: Cloudflare | CANONICAL_URL:
確認上の限界
元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
出典ID・検証情報・機械可読データ
根拠の種類と情報の鮮度は、ラベルとアイコンで確認できます。
- 記事ID
- EA-166
- 最終確認日
- —
- 提供元・モデル・プラン・利用環境
- —
- 対象地域
- —
元資料の全文と収録照合記録
WHY_THIS_MATTERS_TO_UPDATE
Enterprise AI gateway is a control-plane category rather than one universal product. A useful update must compare concrete gateway claims while keeping self-hosted OSS, managed routing, provider transformation, logging, budget, cache, and data-policy surfaces separate.
SCOPE_ROUTING
Enterprise AI Core / provider mapping / gateway / governance / cost / observability / security / implementation
CLAIM_OR_RESEARCH_QUESTION
Across LiteLLM, OpenRouter, Vercel AI Gateway, and Cloudflare AI Gateway, which gateway capabilities are directly documented, and which cross-product conclusions remain unproven?
EVIDENCE_TABLE
[S1] SOURCE_CLASS: author_maintained_repo | EXACT_TITLE: BerriAI/litellm - LiteLLM repository | AUTHOR_ORG: BerriAI / LiteLLM maintainers | CANONICAL_URL: https://github.com/BerriAI/litellm | PUBLICATION_UPDATE_ACCESS: accessed 2026-09-14 00:16 JST | VERSION_RELEASE_TAG: default branch; unpinned | SUPPORTING_LOCATOR: lines 542-549 for Proxy/SDK, centralized auth, multi-tenant spend, logging/guardrails/caching, Router retry/fallback, stable-tag note | EVIDENCE_LABEL: OSS_PRACTICE + PRODUCT_VOLATILE | RELATION: support for LiteLLM's documented gateway surface; limit for release/provider parity. [S2] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: OpenRouter API Reference / Auto Router | AUTHOR_ORG: OpenRouter | CANONICAL_URL: https://openrouter.ai/docs/api_reference/overview and https://openrouter.ai/docs/guides/routing/routers/auto-router | PUBLICATION_UPDATE_ACCESS: accessed 2026-09-14 00:16 JST | VERSION_RELEASE_TAG: current docs; unpinned | SUPPORTING_LOCATOR: API normalization/tool transformation lines 25-36 and 75-81; model allow/exclude and cost-tier lines 450-487 | EVIDENCE_LABEL: PRODUCT_VOLATILE + VERIFIED_SPEC | RELATION: support for managed API/routing claims; limit for cross-provider equivalence. [S3] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: Vercel AI Gateway: Models, Routing, and Observability | AUTHOR_ORG: Vercel | CANONICAL_URL: https://vercel.com/docs/ai-gateway | PUBLICATION_UPDATE_ACCESS: current page accessed 2026-09-14 00:16 JST | VERSION_RELEASE_TAG: current docs; product/plan availability volatile | SUPPORTING_LOCATOR: lines 386-423 for managed gateway, provider/fallback routing, logs, latency/token/cost, budgets/access/data policies/BYOK; lines 426-433 for API key/OIDC and logging/budget controls | EVIDENCE_LABEL: VERIFIED_SPEC + PRODUCT_VOLATILE | RELATION: support for Vercel-specific control surface; limit for plan/terms/provider behavior. [S4] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: Cloudflare AI Gateway | AUTHOR_ORG: Cloudflare | CANONICAL_URL: https://developers.cloudflare.com/ai-gateway/ | PUBLICATION_UPDATE_ACCESS: last updated 2026-04-20; accessed 2026-09-14 00:16 JST | VERSION_RELEASE_TAG: current docs; page says available on all plans, subject to current product terms | SUPPORTING_LOCATOR: lines 138-147 for visibility/control; lines 157-182 for analytics, logging, caching, rate limiting, retry/fallback; lines 186-188 for provider examples | EVIDENCE_LABEL: VERIFIED_SPEC + PRODUCT_VOLATILE | RELATION: support for Cloudflare-specific controls; limit for actual configuration and provider parity.
FINDINGS
- ESTABLISHED [S1-S4 support]: The category consistently exposes a control-plane pattern—provider/model selection, request routing, and some combination of auth, logging, cost, limits, caching, fallback, or policy—but each product defines a different boundary.
- ESTABLISHED [S1 support]: LiteLLM documents self-hostable SDK/Proxy distinctions and multi-tenant spend/auth/logging/guardrail/cache/router features.
- ESTABLISHED [S2 support]: OpenRouter documents a managed normalized API with provider-dependent tool transformation and model allow/exclude/cost-tier routing.
- ESTABLISHED [S3 support]: Vercel documents managed credentials, provider/fallback routing, logs with provider attempts/latency/tokens/cost, budgets, access/data policies, BYOK, and OIDC for Vercel deployments; the same page says provider terms apply.
- ESTABLISHED [S4 support]: Cloudflare documents analytics/logging, caching, rate limiting, request retry, model fallback, and multiple provider integrations; its page records a current plan statement, which is still a product/plan gate.
- INFERENCE [S1-S4]: A gateway can centralize policy and observability, but a cross-product claim such as “gateway guarantees reliability, privacy, cost control, or provider equivalence” is not established by these feature lists. The gateway becomes an additional trust, transformation, outage, and audit boundary.
LIMITS / COUNTEREVIDENCE / FAILURE ENVELOPE
Feature-list overlap is not functional equivalence. Managed versus OSS deployment, release, plan, region, BYOK, provider contract, log retention, cache scope, route algorithm, retry semantics, transformed tool schemas, and audit export differ. Vendor pages do not prove independent latency, quality, privacy, or SLO. Fallback/retry may duplicate or alter requests. No cross-gateway benchmark or live call was run.
AVAILABILITY_GATES
product and release/commit; self-hosted versus managed; plan/region; provider/model catalog; API transformation; credentials/BYOK/OIDC; routing/fallback/retry; budgets/rate limits; caching; logs/traces/audit export; retention/data residency; admin/RBAC; outage behavior; pricing/markup; contract/SLO.
IMPLEMENTATION_STATE
Evidence-only desk research. No gateway was configured, authenticated, called, or compared with a live provider.
BENCHMARK_OR_EVAL
No cross-gateway conformance, latency, cost, fallback-duplication, transformation, privacy, or outage-recovery evaluation was run.
SECURITY / PRIVACY / AUDIT / COST / OPERABILITY
A gateway centralizes high-value secrets and high-sensitivity telemetry. Require route/provider attribution, request transformation record, policy decision, token/cost source, retry attempts, cache hit, redaction, retention, and downstream result. Treat gateway outage and misrouting as distinct failure modes from provider outage. Cost must include gateway, provider, retries, cache/storage, and operational review; not measured.
SAFE_WORDING_FOR_FUTURE_BOOK
「AI Gateway群は、複数providerへの接続を集約し、routing／fallback、認証、rate limit、logging、cost、cache、policy等を実装するcontrol-plane群である。LiteLLM、OpenRouter、Vercel、Cloudflareの公式資料は機能境界が異なるため、共通機能と製品固有の実装・契約・版・地域・設定を分離して評価する。」
UPDATE_WORK_HANDOFF
Future update Work should build a four-product comparison matrix with pinned release/page dates and a safe read-only TEST_PROFILE: direct versus gateway output, provider attribution, schema/tool transformation, retry/fallback, rate/budget, cache isolation, logging/redaction, data policy, outage, and audit readback. No external side-effect tool should be enabled.
OPEN_UNKNOWN
neutral gateway semantics; cross-product interoperability; route determinism; tool/result transformation; cache privacy; budget enforcement; data residency; provider contract; markup; audit completeness; outage/fallback behavior; independent benchmark/SLO.
STOP_CONDITION
Do not merge LiteLLM OSS, OpenRouter managed API, Vercel managed gateway, and Cloudflare gateway into one product or one guarantee. Do not state that the presence of logs, budgets, fallback, or cache equals effective enforcement without configuration and negative testing. UNIT_CLOSE_STATUS: INDIVIDUAL_BOUNDED_CLOSE / EVIDENCE_RECORDED / UNKNOWN_PRESERVED
EVIDENCE PACKET
---
EVD-EA-166-URL-DAB892839DF4研究資料研究資料根拠の出所: SOURCE_PACKET_REFERENCELiteLLM repository | AUTHOR_ORG: BerriAI / LiteLLM maintainers | CANONICAL_URL:
- 裏付ける内容
- —
- 確認日
- —
- 出典・実験ID
- SRC-EA-166-URL-DAB892839DF4
- 検証箇所
- EVIDENCE_TABLE · - LiteLLM repository | AUTHOR_ORG: BerriAI / LiteLLM maintainers | CANONICAL_URL: https://github.com/BerriAI/litellm
- 適用範囲
- EVIDENCE_TABLE
- 出典・来歴
- SOURCE_PACKET_REFERENCE_PROJECTED
- 限界
- 元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
EVD-EA-166-URL-62E5A2D5FE3E研究資料研究資料根拠の出所: SOURCE_PACKET_REFERENCE- 裏付ける内容
- —
- 確認日
- —
- 出典・実験ID
- SRC-EA-166-URL-62E5A2D5FE3E
- 検証箇所
- EVIDENCE_TABLE · S2 · [S2] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: OpenRouter API Reference / Auto Router | AUTHOR_ORG: OpenRouter | CANONICAL_URL: https://openrouter.ai/docs/api_reference/overview
- 適用範囲
- EVIDENCE_TABLE
- 出典・来歴
- SOURCE_PACKET_REFERENCE_PROJECTED
- 限界
- 元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
EVD-EA-166-URL-C1CC13E818A2研究資料研究資料根拠の出所: SOURCE_PACKET_REFERENCE- 裏付ける内容
- —
- 確認日
- —
- 出典・実験ID
- SRC-EA-166-URL-C1CC13E818A2
- 検証箇所
- EVIDENCE_TABLE · S2 · [S2] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: OpenRouter API Reference / Auto Router | AUTHOR_ORG: OpenRouter | CANONICAL_URL: https://openrouter.ai/docs/api_reference/overview and https://openrouter.ai/docs/guides/routing/routers/auto-router
- 適用範囲
- EVIDENCE_TABLE
- 出典・来歴
- SOURCE_PACKET_REFERENCE_PROJECTED
- 限界
- 元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
EVD-EA-166-URL-EC8B42E94341研究資料研究資料根拠の出所: SOURCE_PACKET_REFERENCE- 裏付ける内容
- —
- 確認日
- —
- 出典・実験ID
- SRC-EA-166-URL-EC8B42E94341
- 検証箇所
- EVIDENCE_TABLE · S3 · [S3] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: Vercel AI Gateway: Models, Routing, and Observability | AUTHOR_ORG: Vercel | CANONICAL_URL: https://vercel.com/docs/ai-gateway
- 適用範囲
- EVIDENCE_TABLE
- 出典・来歴
- SOURCE_PACKET_REFERENCE_PROJECTED
- 限界
- 元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
EVD-EA-166-URL-89526D1B8A91研究資料研究資料根拠の出所: SOURCE_PACKET_REFERENCE- 裏付ける内容
- —
- 確認日
- —
- 出典・実験ID
- SRC-EA-166-URL-89526D1B8A91
- 検証箇所
- EVIDENCE_TABLE · S4 · [S4] SOURCE_CLASS: official_provider_docs | EXACT_TITLE: Cloudflare AI Gateway | AUTHOR_ORG: Cloudflare | CANONICAL_URL: https://developers.cloudflare.com/ai-gateway/
- 適用範囲
- EVIDENCE_TABLE
- 出典・来歴
- SOURCE_PACKET_REFERENCE_PROJECTED
- 限界
- 元の監査済み資料に記載された参照先です。URLの復元は、資料の最新性や全主張の支持を新たに検証したことを意味しません。
EA-166-R11-RESEARCH研究資料研究資料根拠の出所: AUDITED_CANONICAL_RESEARCH_PACKETEA-166 監査済みresearch / canonical revision binding
- 裏付ける内容
- 1. ESTABLISHED [S1-S4 support]: The category consistently exposes a control-plane pattern—provider/model selection, request routing, and some combination of auth, logging, cost, limits, caching, fallback, or policy—but each product defines a different boundary. 2. ESTABLISHED [S1 support]: LiteLLM documents self-hostable SDK/Proxy distinctions and multi-tenant spend/auth/logging/guardrail/cache/router features. 3. ESTABLISHED [S2 support]: OpenRouter documents a managed normalized API with provider-dependent tool transformation and model allow/exclude/cost-tier routing. 4. ESTABLISHED [S3 support]: Vercel documents managed credentials, provider/fallback routing, logs with provider attempts/latency/tokens/cost, budgets, access/data policies, BYOK, and OIDC for Vercel deployments; the same page says provider terms apply. 5. ESTABLISHED [S4 support]: Cloudflare documents analytics/logging, caching, rate limiting, request retry, model fallback, and multiple provider integrations; its page records a current plan statement, which is still a product/plan gate. 6. INFERENCE [S1-S4]: A gateway can centralize policy and observability, but a cross-product claim such as “gateway guarantees reliability, privacy, cost control, or provider equivalence” is not established by these feature lists. The gateway becomes an additional trust, transformation, outage, and audit boundary.
- 確認日
- —
- 出典・実験ID
- COMM-048-EA0166
- 検証箇所
- COMM-048-EA0166 · EA-166-R5-LEGACY-MIGRATION-20261008-R1 · content/staging/EA-166.md
- 適用範囲
- 監査済みEA本文・canonical revision・既存Source Graph relationの範囲。欠損currentnessは推測で閉じない。
- 出典・来歴
- AUDIT_PASS_CANONICAL_BINDING
- 限界
- canonical監査・revision bindingの存在を示す。外部ソースcurrentnessが本文またはcontrol-planeで確定していない場合は、currentnessをUNKNOWNのまま保持する。
EA-166-R11-WEB-READBACK実装資料実装資料根拠の出所: IMPLEMENTATION_READBACKEA-166 Web body identity / canonical readback
- 裏付ける内容
- canonical staging bodyのSHA-256一致とR9 canonical ledger readbackをProduction projectionの入力として検証する。
- 確認日
- —
- 出典・実験ID
- WEBBODY-EA0166-R8-5484DBF6
- 検証箇所
- WEBBODY-EA0166-R8-5484DBF6 · content/staging/EA-166.md · EA-166-R5-LEGACY-MIGRATION-20261008-R1
- 適用範囲
- R9/R10 canonical readback後のProduction生成時body identity。
- 出典・来歴
- CANONICAL_READBACK_BODY_HASH_MATCH
- 限界
- body identity/readbackは本文claim自体の真偽や外部ソースの最新性を追加保証しない。
- 出典ID
- COMM-048-EA0166, SRC-EA-166-URL-DAB892839DF4, SRC-EA-166-URL-62E5A2D5FE3E, SRC-EA-166-URL-C1CC13E818A2, SRC-EA-166-URL-EC8B42E94341, SRC-EA-166-URL-89526D1B8A91, WEBBODY-EA0166-R8-5484DBF6
- 追跡中のUNKNOWN ID
- EA-166-UNKNOWN-01, EA-166-UNKNOWN-CURRENTNESS
- 再確認のきっかけ
- canonical revision/publication state change · body artifact hash change · source currentness change · new contradiction or implementation readback
機械検査: 通過 — Automated validation does not guarantee accuracy or authorize execution.
同じ記事IDの機械可読データです。