hunta-ai Candidates API

The Candidates API from hunta-ai — 3 operation(s) for candidates.

Operations 3

GET /v1/candidates The curation queue (memory:curate|write) #
POST /v1/candidates/{cid}/promote Promote a candidate into canon via the full curated write pipeline… #
POST /v1/candidates/{cid}/reject Reject a pending candidate (memory:curate|write) #

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/hunta-ai:hunta-ai-candidates-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

hunta-ai-candidates-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: hunta.ai Memory Candidates API
  version: 0.17.0
  description: 'Attestable per-tenant agent memory. Tenant = the Bearer JWT''s `tid`; no endpoint takes a tenant argument. Scopes: memory:read|write|capture|curate|admin (legacy `memory` = read+write+capture+curate, not admin). Staging: capture → candidates (never recalled) → promote = the curated write into canon; promote/reject are provenance-stamped server-side (curated_by = token sub, lane = auto|human). Reconciliation (R0): facts listing + surgical supersede/invalidate (bi-temporal, curate-scope) + fact-granular forget (write-scope only).'
servers:
- url: https://mcp.hunta.ai
security:
- bearer: []
tags:
- name: Candidates
paths:
  /v1/candidates:
    get:
      summary: The curation queue (memory:curate|write)
      parameters:
      - name: status
        in: query
        schema:
          type: string
          enum:
          - pending
          - promoted
          - rejected
          - expired
      - name: limit
        in: query
        schema:
          type: integer
      responses:
        '200':
          description: decrypted candidates
      tags:
      - Candidates
      operationId: getV1Candidates
      x-operation-id-source: derived
  /v1/candidates/{cid}/promote:
    post:
      summary: Promote a candidate into canon via the full curated write pipeline…
      parameters:
      - name: cid
        in: path
        required: true
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                text:
                  type: string
                agent:
                  type: string
      responses:
        '201':
          description: promoted — memory_id returned
        '404':
          description: not_found
        '409':
          description: not pending
      tags:
      - Candidates
      operationId: postV1CandidatesByCidPromote
      x-operation-id-source: derived
  /v1/candidates/{cid}/reject:
    post:
      summary: Reject a pending candidate (memory:curate|write)
      parameters:
      - name: cid
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: rejected
        '404':
          description: not found/not pending
      tags:
      - Candidates
      operationId: postV1CandidatesByCidReject
      x-operation-id-source: derived
components:
  securitySchemes:
    bearer:
      type: http
      scheme: bearer
      bearerFormat: JWT