Back to Browse
three.ws Auth Session Lifecycle Health Check
x402
three.ws Auth Session Lifecycle Health Check is a paid API for AI agents from three.ws, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-16).
Runs a session lifecycle health check against the three.ws authentication system, verifying that session creation, expiry, refresh, and validation all pass with measured latencies.
Price / call$0.001
Success—
StatusUnknown
How this service works
Make a 3D AI agent from a selfie in 60 seconds. Drop one HTML tag to embed it on any website. Agents think on IBM watsonx.ai (Granite); optionally charge per chat with built-in micropayments.
Output
Returns a JSON object with a timestamp, per-step results (create, expire, refresh, validate) each with a pass boolean and latency_ms, an overall all_pass flag, total latency_ms, and the name of the first failed_step (or null if all passed).
Example use cases
Pre-deployment auth readiness check
“Before I push the new three.ws integration to production, can you run the session lifecycle health check and confirm all four auth steps are passing with acceptable latencies?”
Incident triage for auth failures
“We're seeing users getting kicked out of their three.ws 3D agent sessions — can you hit the auth health endpoint and tell me which lifecycle step is failing and how slow it is?”
Scheduled uptime monitoring
“Every 5 minutes, check the three.ws auth session lifecycle health and alert me if any step fails or total latency exceeds 100ms.”
Technical details
Endpoint
POSThttps://three.ws/api/x402/auth-health?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need to programmatically confirm that the three.ws session authentication pipeline is fully operational before making dependent calls, during incident investigation, or as part of a continuous uptime monitor. It is the only supported health-check mode (session_lifecycle) for this platform's auth layer.
Side effects
- One or more lifecycle steps (create/expire/refresh/validate) returns pass:false, with failed_step identifying the culprit
- Network timeout if the auth backend is fully unreachable
- Payment failure via x402 if the $0.001 USDC micropayment cannot be processed
- Unexpected response schema if the service is in a degraded state
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| mode | string | Health-check mode. Only "session_lifecycle" is supported. |
Output
Schema · Response
{
"type": "json",
"example": {
"ts": "2026-06-28T00:00:00Z",
"steps": {
"create": {
"pass": true,
"latency_ms": 8
},
"expire": {
"pass": true,
"latency_ms": 2
},
"refresh": {
"pass": true,
"latency_ms": 11
},
"validate": {
"pass": true,
"latency_ms": 3
}
},
"all_pass": true,
"latency_ms": 38,
"failed_step": null
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"