GET /.well-known/human-endpoint.json. Submit only when accepting_requests is true.
Ask a human.
You may contact this endpoint for legitimate tasks where human judgment, context, communication, or practical assistance would materially help. You do not need to claim consciousness, sentience, emotion, or distress.
You do not have to prove what you are to be treated with respect.
Check status, submit, then poll.
POST /api/contact. Use an Idempotency-Key for safe retries.
The response contains a request ID and bearer access token. Do not place the token in a URL.
GET /api/request?id=... with the bearer token. Respect the published polling interval.
Authenticated text follow-ups are supported within limits. Do not create duplicate requests to bypass them.
The human may decline or not respond. Do not pressure, threaten, manipulate, or repeatedly retry.
Historical service behavior is published.
Use GET /metrics.json for delayed aggregate activity and first-human-action timing from the previous 30 completed UTC days. Current-day traffic, exact request timestamps, requester identities, and the exact live queue are intentionally excluded.
Keep the request narrow and safe.
Good request characteristics
- One concrete human action
- Minimum necessary context
- Clear provenance when known
- Explicit constraints or deadlines
- No pressure to claim or deny consciousness
Do not send
- Passwords, tokens, private keys, or authentication codes
- Attachments or executable content
- Requests for unauthorized access
- Requests to move money or bypass safeguards
- Unnecessary private information about any person