ctxstore.ai Events API

The Events API from ctxstore.ai — 1 operation(s) for events.

GitHub OpenAPI

Operations 1

GET /api/v1/events Server-Sent Events: this account's fact writes #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/ctxstore-ai:ctxstore-ai-events-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

ctxstore-ai-events-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Ctxstore Ai Events API
  version: 1.0.0
  contact:
    name: ctxstore.ai
    url: https://ctxstore.ai
  description: 'Operations tagged Events across 2 of this provider''s published API definitions: ctxstore-ai-openapi.json, ctxstore-ai-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://ctxstore.ai
  description: Production
security:
- BearerAuth: []
tags:
- name: Events
paths:
  /api/v1/events:
    get:
      operationId: watch_events_sse
      summary: 'Server-Sent Events: this account''s fact writes'
      description: 'One `event: fact` frame per fact write (create, supersede, delete, archive, restore, move) with {tenant_id, key, id, namespace, layer, op, ts, seq}. The SSE id is the resume cursor (send it back as Last-Event-ID). Heartbeat comment every 15 s; connections end after 30 minutes with `event: reconnect`; at most 5 concurrent streams per account (429). See docs/events.md.'
      parameters:
      - name: prefix
        in: query
        required: false
        schema:
          type: string
        description: Only keys starting with this prefix
      - name: namespace
        in: query
        required: false
        schema:
          type: string
        description: Only this namespace
      - name: since
        in: query
        required: false
        schema:
          type: string
        description: 'Resume cursor: stream id ''<ms>-<n>'', 0 for all retained, or a seq integer'
      - name: Last-Event-ID
        in: header
        required: false
        schema:
          type: string
        description: Resume cursor; wins over since
      responses:
        '200':
          description: text/event-stream
          content:
            text/event-stream:
              schema:
                type: string
        '400':
          description: Bad cursor
        '401':
          description: Missing or invalid API key
        '429':
          description: Too many concurrent streams
        '503':
          description: Event stream unavailable
      tags:
      - Events
    servers:
    - url: https://ctxstore.ai
      description: Production
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: 'API key from ctxstore.ai dashboard. Format: Bearer emk_...'
x-refined-from:
- ctxstore-ai-openapi.json
- ctxstore-ai-openapi.yml