SelectAgentCheck what happened after the action.
Your agent tried to create an engineering issue. The request timed out. Before it creates another issue or reports completion, it needs evidence from the receiving system.
SelectAgent Verify compares observed state with an outcome contract. The first connector checks GitHub issue creation: the expected title, required labels, open or closed state, and a correlation marker. It returns a timestamped result and a bounded recovery instruction.
Request free access ↗Requesting early access is free and requires no card. The hosted preview uses operator-issued keys; self-service accounts are not yet available. A recurring free quota and optional usage credits are planned. Quota metering and credit purchases are not live, and there is no automatic upgrade or default charge.
One contract, then a receiving-system check.
- Register the intended effect. Set the authorized repository, expected fields and correlation key. Include the returned marker in the original issue body before the agent writes.
- Ask for an observation. Verify after an uncertain response or before reporting completion. SelectAgent performs read-only GitHub requests within configured limits.
- Use the evidence. Inspect the verdict, resource reference, field checks, observation time and read coverage. Follow the recovery instruction within your workflow's authority.
Three results with explicit limits.
Verified: the specified resource fields satisfy the contract within the reported observation scope. Reuse the observed resource. This does not guarantee the state will remain unchanged.
Contradicted: the evidence conflicts with the contract, such as mismatched fields or multiple matching issues. Reconcile the existing state before continuing.
Indeterminate: the evidence is missing, incomplete or unavailable. A bounded scan can miss records. Wait and reverify, or restore access as indicated; absence is not permission to repeat the original write.
A known issue reference checks that resource; it does not establish repository-wide uniqueness. A correlation marker locates a record; it does not prove who created it. SelectAgent never automatically creates, edits, deletes, retries or reverses a GitHub issue.
Use it from your existing agent.
Operator-issued keys can call the REST API at https://selectagent.ai/verify-api. The supplied MCP adapter runs locally over stdio and calls that API. There is no hosted remote MCP endpoint. Your organization authorizes the connection and repository scope during onboarding.
Reusing an observation's idempotency key returns its original timestamped result. Use a new key when you need a fresh read. The browser workbench is a synthetic demonstration and does not connect to your customer systems.
Start with a measurable handoff.
The initial preview suits agent developers and integration teams with repeated support-to-engineering handoff problems. Checking issue creation does not establish that engineering accepted the escalation, a customer received a notification, or the support problem was resolved. Other providers and cross-system outcomes need additional contracts and are not part of the current connector.
Bring a sanitized failure example and the check you use today. We agree a bounded workflow and evaluate whether independent verification makes your workflow more reliable.