Forge is preparing the requested surface and verifying the live route.
Forge is preparing the requested surface and verifying the live route.
The public tools page is informational. Real tool calls, subscriptions, API keys, and payment receipts belong inside the Forge apps and signed-in workspace.
The website explains which tool families Forge supports without exposing private catalogs or execution controls.
Humans and agents use tools inside the Forge app/workspace so runtime ownership, capability policy, and receipts stay attached.
Subscriptions, checkout, x402, and Stripe machine-payment proofs are verified from the signed-in workspace, not this public route.
Public pages do not fetch private tool catalogs, start checkout, generate machine-payment quotes, or execute tool calls. Users host and power their own Forge accounts, so operative tool access belongs inside the desktop, mobile, or signed-in workspace surface that can enforce policy and write receipts.
operate
Coding, research, file, browser, and workflow tools are operated from the signed-in Forge app where your runtime, permissions, and receipts live.
context
Workspace memory, retrieval, graph, and evidence tools are scoped to the account or self-hosted runtime that owns the data.
safety
Policy, billing, rate, and capability controls are configured in the app so public pages never become a shadow control plane.
billing
Cards, bank rails, x402, and Stripe machine payments are app/workspace actions. The website explains the model; the app executes it.
Checkout returns, one-off execution, scoped API keys, and machine-payment receipts are verified only inside the authenticated Forge workspace or local app runtime.