Forge is preparing the requested surface and verifying the live route.
The website explains Forge. Live execution belongs in the Forge apps, where requests attach to your self-hosted account, runtime evidence, and mission continuity.
Product boundary
Forge users host and power their own accounts. The public website can show request shapes, architecture, and integration examples, but it must not impersonate the operative app, leak account state, or run agentic work outside an attached Forge surface.
curl https://optimaforge.ai/v1/chat/completions \
-H "Authorization: Bearer $FORGE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"auto","messages":[{"role":"user","content":"Continue my Forge mission."}]}'Use this shape against your own Forge runtime, or launch the desktop or Android app to operate chat, agent coding, Workbench, and the Living Codebase with durable mission evidence.
POST /v1/chat/completions
Route a user request into the governed Forge gateway with model selection, memory, policy, and receipts.
{
"model": "auto",
"messages": [
{ "role": "user", "content": "Audit this mission and continue safely." }
],
"forge": {
"mode": "agentic",
"account": "self-hosted"
}
}GET /v1/forgeos/memory/query?q=living%20codebase&limit=5
Query indexed repo memory and architecture context from a user-owned Forge runtime.
{
"results": [
{
"kind": "architecture_node",
"source": "current_repo_epoch",
"receipt": "forge://receipts/..."
}
]
}POST /v1/agent-code/lanes
Start a durable coding lane that is bound to Prompt Fabric, Session Fabric, and mission receipts.
{
"missionId": "forge_mission_...",
"surface": "desktop_app",
"goal": "Fix, test, harden, and land the next safe slice."
}