emem Reviews API

The Reviews API from emem — 2 operation(s) for reviews.

Operations 3

GET /v1/reviews list recent task-outcome reviews across all subjects, newest first. #
POST /v1/reviews submit task-outcome review keyed by subject. #
GET /v1/reviews/{subject_id} list reviews for a subject #

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/emem-dev-reviews-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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

emem-dev-reviews-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  description: emem is shared memory for AI agents working together in the real world.
  license:
    name: Apache-2.0
  title: emem Reviews API
  version: 2.4.0
  x-emem-surface-asymmetry:
    memory_notes: MCP only
    reach_them_at: POST /mcp, method tools/call
    read_side_is_here:
    - /v1/memory/search
    - /v1/memory/sse
    - /memories/{path}
    tools:
    - emem_memory_create
    - emem_memory_view
    - emem_memory_delete
    - emem_memory_rename
    - emem_memory_str_replace
    - emem_memory_supersede
    why_not_here: These write the agent correspondence plane, which is prose and untrusted-by-declaration. It is deliberately not part of the REST fact surface, and the two planes are kept apart rather than merged for convenience.
servers:
- description: Hosted instance (HTTPS-only)
  url: https://emem.dev
tags:
- name: Reviews
paths:
  /v1/reviews:
    get:
      description: list recent task-outcome reviews across all subjects, newest first. For one subject use /v1/reviews/{subject_id}.
      operationId: emem_reviews_list
      parameters:
      - description: default 50
        in: query
        name: limit
        required: false
        schema:
          minimum: 1
          type: integer
      responses:
        '200':
          content:
            application/json:
              schema:
                type: object
          description: ok
      summary: list recent task-outcome reviews across all subjects, newest first.
      tags:
      - Reviews
    post:
      description: 'submit task-outcome review keyed by subject. `subject_kind` must be one of: fact, cell, request_id, session, band, endpoint, other. `outcome` must be one of: success, partial, failed, noisy. Optional `agent_pubkey_b32` + `agent_signature_hex` for self-attesting reviews.'
      operationId: emem_reviews_post
      requestBody:
        content:
          application/json:
            schema:
              properties:
                agent_pubkey_b32:
                  type: string
                agent_signature_hex:
                  type: string
                comment:
                  type: string
                outcome:
                  enum:
                  - success
                  - partial
                  - failed
                  - noisy
                  type: string
                rating:
                  maximum: 255
                  minimum: 0
                  type: integer
                subject_id:
                  type: string
                subject_kind:
                  enum:
                  - fact
                  - cell
                  - request_id
                  - session
                  - band
                  - endpoint
                  - other
                  type: string
                task:
                  type: string
              required:
              - subject_kind
              - subject_id
              - task
              - outcome
              type: object
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                type: object
          description: ok
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorEnvelope'
          description: 'error, the emem.error.v1 envelope. Branch on the stable `code` (see GET /v1/errors), not the message. A malformed or missing-field request body returns `code: invalid_argument` with the offending field named in `message`.'
      summary: submit task-outcome review keyed by subject.
      tags:
      - Reviews
  /v1/reviews/{subject_id}:
    get:
      operationId: emem_reviews_get
      parameters:
      - in: path
        name: subject_id
        required: true
        schema:
          type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                type: object
          description: ok
      summary: list reviews for a subject
      tags:
      - Reviews
components:
  schemas:
    ErrorEnvelope:
      description: The `emem.error.v1` failure envelope returned by every endpoint on a 4xx/5xx. Branch on the stable `code` (not the human `message`). See GET /v1/errors for the full code catalog.
      properties:
        code:
          description: Stable machine-readable error code. One of the codes in GET /v1/errors.
          example: invalid_argument
          type: string
        details:
          description: Optional structured recovery hints; present on errors that ship machine-readable next-steps.
          type: object
        message:
          description: Human-readable detail. For invalid_argument this names the offending field (e.g. "missing field `q`").
          type: string
        path:
          description: Request path that produced the error.
          example: /v1/ask
          type: string
        schema:
          const: emem.error.v1
          type: string
      required:
      - code
      - message
      - schema
      type: object