> ## Documentation Index
> Fetch the complete documentation index at: https://docs.abloatai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Release presence claim



## OpenAPI

````yaml /openapi.json delete /v1/models/presence/{id}/claim
openapi: 3.1.0
info:
  title: Ablo Sync Engine HTTP API
  version: 0.16.1
  description: >-
    The HTTP surface of the Ablo sync engine. Most production traffic flows over
    WebSocket via `@abloatai/ablo`; this HTTP API is the Vercel-safe transport
    for environments that cannot hold long-lived sockets, plus the control plane
    for capabilities and usage.


    The per-model resource routes (`/v1/models/{model}`) are **generated from
    your own pushed schema** — they are documented here generically over
    `{model}`, with `tasks` as the running example. Authenticate every request
    with a `Bearer` API key or scoped token.
servers:
  - url: https://api.abloatai.com/api
    description: Production
  - url: http://localhost:8787/api
    description: Local development
security:
  - bearerAuth: []
tags:
  - name: Records
    description: Typed CRUD over any model in your schema.
  - name: Coordination
    description: Claims — pessimistic row reservation for human+agent coordination.
  - name: State
    description: Atomic multi-model commits.
  - name: Control plane
    description: Capabilities and usage.
paths:
  /v1/models/presence/{id}/claim:
    parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
        description: Record id.
    delete:
      tags:
        - Models
      summary: Release presence claim
      operationId: release_presence
      responses:
        '200':
          description: Released (or nothing to release).
          content:
            application/json:
              schema:
                type: object
                properties:
                  ok:
                    type: boolean
                  released:
                    type: boolean
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        API key (`sk_live_…`) or a scoped capability/ephemeral token. The same
        header carries both — the server discriminates by token shape.

````