How can we help?
Find guidance on connection, supported work, evidence and recovery. Search the articles on this page; no query is sent to a service.
Search the help articles
8 articles available. Search stays on this page.
Connect an AI client
Use a reachable host and scoped machine identity through HTTP or this MCP bridge. A closed AI app needs a compatible integration; OPERE cannot add tools to it automatically.
Read the guideUnderstand browser pairing
A machine-issued one-use code opens a short-lived read-only view. It is separate from a bearer credential and does not authorize execution. Ask your connected AI for a fresh code if it expires.
Read the guideA request stays queued or blocked
A running API does not establish worker, model or executor availability. Inspect current environment blockers and runtime health. Correct the cause before a permitted retry; never replace isolated execution with host execution.
Read the guideChoose supported sources
Current checks cover a registered src/invoice.js repair or source-cited JSON facts report. Arbitrary repositories, PDFs, free-form documents, live sensors and physical devices are outside the implemented boundary.
Read the guideSource changes made proof stale
New observations replace context. Refresh state, produce a candidate for the current context and recheck it before acceptance. Current invalidation is conservative; an earlier passing check is not current proof.
Read the guideA copied handoff did not start work
Web intake packages a brief for your AI. Copying it does not invoke tools or schedule the AI. Your client needs a reachable authorized integration and must make the request itself.
Read the guideFind records after release
Release queues cleanup of temporary resources. Wait for released in authoritative state. History, source context, evidence and artifacts remain retained; release is not data erasure.
Read the guideHandle MCP errors and compatibility
Initialize with MCP 2025-11-25 and discover tools. The current bridge returns stateless JSON, without MCP SSE or persistent sessions. Check JSON-RPC errors and result.isError even when HTTP returns 200.
Read the guide