Claim Guest data onto a Registered User
Browser transition that moves Guest Transcripts and Chats onto the Clerk Registered User. Requires both a Clerk Bearer token and the Guest session cookie. Agents should not call this route.
POST /api/v1/auth/guest-sessions/claim
OpenAPI operation claimGuestSession. This browser transition requires both a Clerk session JWT (Authorization: Bearer {jwt}) and the verbafy_guest_session cookie. The browser sends the HttpOnly cookie automatically. Agents should not call this route. Machine-readable contract: OpenAPI.
Request example
curl -X POST 'https://verbafy.io/api/v1/auth/guest-sessions/claim' \
-H 'Authorization: Bearer {jwt}' \
-H 'Cookie: verbafy_guest_session={guest_token}'Responses
| Status | Description |
|---|---|
200 | Claim result |
401 | Missing or invalid Clerk Bearer token or guest session |
409 | Conflict with current resource state |
Remote MCP at /api/v1/mcp is a companion wrap of this REST contract.
Revoke API key
Revoke one API Key owned by the current Registered User. DELETE /api/v1/me/api-keys/{id} on the Verbafy REST API.
Create or reuse a Guest session
Creates a seven-day Guest session cookie when none is valid. Production may require turnstileToken. New creates are limited to 3 per client IP per 3600 seconds.