Community is publication, not verification
Community deployments are public with warnings and can be selected consciously. They are not recommended by default and are used automatically only when a client key has explicit Community opt-in.
Provider onboarding
- Use a provider or both account type, then open the Provider workspace.
- Complete the provider profile: public name, private legal identity, billing country, terms and payout status.
- Create an endpoint with a base URL, declared country, declared capacity and encrypted upstream secret.
- Create deployments that map a canonical model to an upstream model id, quantization and capabilities.
- Run checks, add a pricing version and publish to Community when the minimum controls pass.
Endpoints
- Base URL: the public OpenAI-compatible endpoint called by ForgeRouter after SSRF and egress checks.
- Secret: stored encrypted, used only for upstream calls and never shown again after save. Rotate by replacing it.
- Country: displayed as declared by provider unless a stronger evidence level is attached.
- Capacity: RPM, TPM and concurrency are declared capacity controls, then compared with measured by ForgeRouter metrics.
- Maintenance and suspension: pause traffic at endpoint level without deleting historical request snapshots.
Deployments and pricing
A deployment is provider + endpoint + canonical model + quantization + configuration. Pricing versions are append-only records used in request snapshots.
- Canonical model identifies what clients request; upstream model id stays provider-facing when needed.
- Capabilities such as streaming, tool calling and structured outputs must match checks before they are used for routing.
- Provider prices are public inference prices per million tokens. ForgeRouter platform fees are separate client charges, not hidden provider commission.
- Provider payables are accumulated from valid usage and shown through provider statements, not as a client wallet.
Publication controls
- Sandbox deployments are visible only to the provider and do not receive paid client traffic.
- Community publication currently requires an active provider identity and terms, an active endpoint, a mapped model, a current price and passing network/OpenAI compatibility checks. Streaming is checked when the deployment declares streaming support.
- Data policy and abuse screening are not currently automated publication gates in the beta. Any provider data-handling claim remains declared by provider until a matching proof is independently verified.
- Observed status comes from measured by ForgeRouter quality over time. It is not a legal identity or no-log verification.
- Verified and Enterprise tiers require dimension-specific checks or contracts; they are not granted by Community publication.
ForgeNode
ForgeNode helps enrollment, heartbeat, inventory, runtime instances and status reporting from provider infrastructure. Data from ForgeNode is always reported by ForgeNode, not independently audited by default.
- Enrollment tokens are created from Provider nodes and can be revoked.
- ForgeNode must not collect prompts or responses.
- ForgeNode must not accept arbitrary shell commands from ForgeRouter.
- Billing authority remains the ForgeRouter gateway and request ledger, never ForgeNode alone.
Provider operations
Metrics and incidents
Follow request volume, success rate, measured latency, incidents and active kill switches.
Endpoints
Manage endpoint health, declared country, capacity and maintenance state.
Deployments and pricing
Run checks, publish Community and add append-only pricing versions.
Statements
Review gross payable, reserve, refunds, adjustments, net payable and paid status.