Community warning
Community is non-verified: visible with warning, selectable manually and eligible for automatic routing only after explicit API-key opt-in.
The default balanced profile excludes Community.
Marketplace tiers
Sandbox
Provider-only visibility, synthetic tests, no paid client traffic and no payout.
Community
Public with warning after minimum checks; manual selection is possible, automatic routing requires opt-in.
Observed
Quality observed automatically from measured success, latency, throughput and incidents; not a privacy audit.
Verified
Dimension-specific manual or documentary verification. It is not a blanket badge.
Enterprise
Contracts, support, capacity commitments and professional operating expectations.
Datacenter
Contractual datacenter-grade capacity and stronger operational requirements where available.
Trust dimensions
A single global trust badge is insufficient. ForgeRouter keeps dimensions distinct so a deployment can be measured for availability without being verified for identity or data handling.
- Identity
- Localization
- Infrastructure control
- Model and quantization
- Data policy
- Availability
- Performance
- Security
- Contractual commitment
Proof labels
- declared by provider: provider claim, such as country, hardware, no-log policy or capacity.
- measured by ForgeRouter: success rate, TTFT, throughput, timeout rate or incident data measured from requests and probes.
- verified by ForgeRouter: dimension-specific documentary or manual check, such as legal identity.
- reported by ForgeNode: agent heartbeat, runtime and inventory data reported from provider infrastructure.
Routing profiles
- balanced: default profile; allows observed, verified and enterprise, excludes Community.
- economy-community: explicit activation; price is strongly weighted and Community is allowed with warning and key-level consent.
- private-eu: verified and enterprise, EEA only, no fallback outside constraints. The beta currently enforces tier and EEA filters; retention compatibility is not yet modeled or enforced and is not a no-retention guarantee.
- agent-safe: Community excluded by default; tool calling and structured outputs must be tested.
- exact: one target deployment, no fallback unless the client explicitly asks for one.
Routing starts with hard filters, then scoring. Price, speed or availability never compensate for a failed trust tier, country, data policy, exact deployment, quantization or feature constraint.
Community consent
Community automatic routing consent is stored per API key with the consent version, consent date and revocation state. Revocation stops future automatic Community selection for that key without deleting historical request snapshots.
Configure this from API keys and verify routed calls in request history.
Request audit
Billable requests keep an immutable routing snapshot without storing prompt or response content by default. Audit fields include:
- provider
- deployment
- trust tier
- country
- pricing version
- request policy
Marketplace pages such as Models and Deployments expose comparable public data before selection.