[Metadata]: Add Weave Router #273

Contribution Type

Add new tool/model/provider

Category

Provider (API Provider), suggested model-service-provider category. Please confirm whether a router or aggregator fits here. I work at Weave.

Tool/Model Name

Weave Router

Vendor/Company

Weave

Description

An Apache-2.0 model router for coding agents, with Claude Code and Codex CLI setup, a hosted service, and a self-hosted option.

Website URL

https://weaveos.com/products/router

Documentation URL

https://weaveos.com/router/quickstart

GitHub Repository

https://github.com/weave-os/router

Additional Information

The public client setup guides cover installation, status checks, scope, and switching back. The benchmark methodology links the public harness, cost sources, and limitations. This submission makes no performance claim.

I reviewed provider.schema.json, its vendor-entity requirements, and the existing OpenRouter record. A full manifest would also need a vendor record, required translations, platform URLs, and provenance fields. I am opening the metadata issue first as requested in CONTRIBUTING.md, rather than presenting an incomplete JSON object as a validated manifest.

Pre-submission Checklist

• I verified the website and documentation URLs are accessible.
• I checked manifests and issues for an existing Weave Router entry.
• The facts above come from the official website and public source repository.
• I reviewed the provider schema and an existing provider manifest.