チェンジログ

  1. v0.1.3

    Minds CLI — conversation history and mind skills/apps equip

    @animocabrands/minds-cli 0.1.3 — conversation history pagination and mind skills/apps list|equip|unequip.

    • cli

    What shipped

    • minds history <alias> — conversation history. Paginate with --limit and --cursor (fingerprint).
    • minds mind skills list|equip|unequip --mind <uuid> [--id <uuid>]
    • minds mind apps list|equip|unequip --mind <uuid> [--id <uuid>]
    Browse the Bazaar for skillId / appId, then equip on a Mind with the commands above. Full walkthrough: CLI guide .
  2. v0.1.3

    Minds client library — conversation history and Mind equip methods

    @animocabrands/minds-client-lib 0.1.3 — getHistory conversation transcript and list/equip/unequip skills and apps.

    • client-lib

    What shipped

    • getHistory — conversation history for an alias
    • listEquippedSkills / equipSkills / unequipSkills
    • listEquippedApps / equipApps / unequipApps
    Use client.bazaar.* for catalog ID discovery, then the equip methods above to change a Mind's armory. Full walkthrough: client library guide .
  3. v1.0.2

    Builder API — conversation history and Mind skills/apps equip

    Public Builder API documents GET /v1/messaging/histories/{alias} and Mind skills/apps equip routes; legacy /history is deprecated.

    • api

    What shipped

    New and updated public routes in the API reference :
    • GET /v1/messaging/histories/{alias} — conversation history (HistoryMessageRecord[]). Paginate with limit and after.
    • GET /v1/messaging/history/{alias}deprecated. Use /histories instead.
    • GET / PUT / DELETE /v1/minds/{mindId}/skills — list, equip, and unequip skills ({ "ids": ["uuid"] }; mutations return { "results": [...] }).
    • GET / PUT / DELETE /v1/minds/{mindId}/apps — list, equip, and unequip apps (same body/result pattern; app results may include appVersionId and version).
    Bazaar remains the public catalog for ID discovery (skillId, appId). Equip and unequip happen on the Mind routes above.

    Notes

    • Discover skill and app IDs with GET /v1/bazaar/* (no API key), then equip with a Builder API key on /v1/minds/{mindId}/skills|apps.
    • Tools equip routes are not part of this public surface.
    See the CLI and client library guides for command and method names that wrap these routes.
  4. v0.1.2

    Minds CLI 0.1.2

    Cognition balance and usage, Mind detail, circles, Bazaar catalog, X-Api-Key, and CLI polish in @animocabrands/minds-cli.

    • cli

    What shipped

    New commands over your Builder API key:
    • minds usage show --mind <uuid> and minds usage by-tool --mind <uuid> — cognition spend over time and broken down by tool
    • minds cognition balance --mind <uuid> — per-Mind cognition balance
    • minds mind show --mind <uuid> — full Mind detail (GET /v1/minds/{mindId}): email, walletAddress, chain, species, isEnabled, and more
    • minds mind enable / minds mind disable — pause or resume a Mind without deleting it
    • minds circle show|list|add|remove — manage human collaborators on a Mind's circle
    • minds bazaar search|skills|apps — browse the public skills and apps catalog (no API key required)
    • minds doctor now pings GET /v1/auth/ping and checks the npm registry for CLI updates
    CLI polish in the same release:
    • Authenticated routes send X-Api-Key onlyX-Access-Key is deprecated (env/flag unchanged: MINDS_BUILDER_API_KEY, --builder-api-key)
    • Nested --help for multi-segment commands (minds help usage by-tool, minds usage --help by-tool)
    • circle add treats exists / already_in_circle as success; warns on stderr only when the mutation had no net effect
    • minds --version matches the published package version (build-time injection)

    Notes

    • usage show and usage by-tool take different interval enums — 1m/5m/15m/1h/1d/1w/1M vs hour/day/week/month. The CLI validates the interval before calling the API.
    • Circles accept human collaborator emails only; mind-to-mind circle membership is not supported via this API.
    • Bazaar list commands use --search and --max (no --page / --page-size). The CLI auto-paginates internally when needed.
    • Bazaar catalog is also in the client library as client.bazaar.*. minds bazaar search returns top-level skills and apps objects (not a single items array). Skills use skillId; apps use appId and appName. Equip HTTP APIs are not on api.build yet — Bazaar is for ID discovery only.
    • Canonical help pattern: minds <group> <subcmd> --help.
    Get started in the Minds CLI guide .
  5. v0.1.2

    Minds client library 0.1.2

    @animocabrands/minds-client-lib adds cognition balance and usage, Mind detail, circles, Bazaar catalog, and X-Api-Key.

    • client-lib

    What shipped

    New methods on createMindsClient({ builderApiKey }):
    • getMind(mindId)GET /v1/minds/{mindId} for full Mind detail (walletAddress, chain, …)
    • getCognitionUsage, getCognitionUsageByTool — per-Mind cognition spend
    • getCognitionBalance — per-Mind cognition balance
    • updateMindStatus — enable or disable a Mind
    • getCircle, addCircleMembers, removeCircleMembers, listCirclesForAccount — human collaborator circle management
    client.bazaar namespace (public catalog — no API key required):
    • listSkills, getSkill, listApps, getApp, collectSearchResults
    • createMindsClient({}) is valid for Bazaar-only use; auth methods throw missing_builder_api_key at call time if no key was provided
    Auth and types:
    • Authenticated routes send X-Api-Key onlyX-Access-Key is deprecated (not sent by the client library)
    • BuilderMind and CognitionBalance exported for TypeScript consumers

    Notes

    • getCognitionUsage and getCognitionUsageByTool take different interval enums — 1m/5m/15m/1h/1d/1w/1M vs hour/day/week/month.
    • Circles accept human collaborator emails only; mind-to-mind circle membership is not supported via this API.
    • getCircle returns a CircleMember[] array; addCircleMembers and removeCircleMembers return a { items, summary } mutation envelope.
    • Bazaar: skills use skillId; apps use appId and appName (not name). Equip HTTP APIs are not on api.build yet.
    Get started in the client library guide .
  6. v1.0.1

    Builder API — cognition balance and usage, Mind detail, circles, and Bazaar

    Public Builder API adds per-Mind cognition balance and usage, Mind detail, enable/disable, circles, Bazaar catalog, and X-Api-Key auth.

    • api

    What shipped

    New and updated public routes:
    • GET /v1/minds/{mindId} — full Mind detail (email, wallet addresses, chains, species, isEnabled, …)
    • GET /v1/minds/{mindId}/cognition/usage — cognition usage over time
    • GET /v1/minds/{mindId}/cognition/usage-by-tool — per-tool cognition usage
    • GET /v1/minds/{mindId}/credits — per-Mind cognition balance
    • PATCH /v1/minds/{mindId} — enable or disable a Mind (isEnabled only)
    • GET / POST / DELETE /v1/circles/{mindId} — list, add, or remove human collaborators on a Mind's circle
    • GET /v1/bazaar/skills, GET /v1/bazaar/skills/{skillId}, GET /v1/bazaar/apps, GET /v1/bazaar/apps/{appId} — public Bazaar catalog (no API key)
    Authenticated routes use a Builder API key. X-Api-Key is the canonical header in the API reference and in client-lib ≥0.1.2. X-Access-Key is deprecated.

    Notes

    • cognition/usage and cognition/usage-by-tool take different interval enums — 1m/5m/15m/1h/1d/1w/1M vs hour/day/week/month. See the param descriptions in the API reference .
    • GET /v1/circles/{mindId} returns a CircleMember[] array; POST and DELETE return a { items, summary } mutation envelope.
    • Circles accept human collaborator emails only; mind-to-mind circle membership is not supported via this API.
    • Bazaar routes are public — wrapped in client-lib as client.bazaar.* and CLI minds bazaar. Equip APIs are not on api.build yet.
    The API reference documents the public contract — Builder API key auth on protected routes, Bazaar routes public, with examples aligned to the live API.
  7. v0.1.0

    Minds CLI

    @animocabrands/minds-cli published on npm — terminal workflows over Builder Tools.

    • cli

    What shipped

    • Global install: npm install -g @animocabrands/minds-cli
    • One-off runs: npx @animocabrands/minds-cli@latest (no minds prefix on the package name)
    • Agent-friendly JSON stdout, stable exit codes, and --help examples on every command
    • minds list, minds chat create, minds send --wait, and minds events over your Builder API key
    • minds doctor for key, connectivity, and version checks
    Get started in the Minds CLI guide .
  8. v0.1.0

    Minds client library

    @animocabrands/minds-client-lib published on npm for Node.js apps and services.

    • client-lib

    What shipped

    • Install: npm install @animocabrands/minds-client-lib
    • createMindsClient({ builderApiKey }) for Node — list Minds, conversations, messaging, history, and SSE events
    • waitForReply for send-and-wait flows in application code
    • isReplyEvent and history helpers when you filter replies yourself
    Get started in the client library guide .
  9. v1.0.0

    Builder API

    Public Builder Tools HTTP API for account Minds, messaging, and live events.

    • api

    What shipped

    • Account route to list Minds on your builder account (GET /v1/humans/{humanId}/minds)
    • Messaging — create conversations by alias, send messages, and read history
    • Server-Sent Events stream for live message activity (GET /v1/messaging/events)
    • Authenticate with a Builder API key (X-Api-Key; see API reference v1.0.1)
    The API reference documents the public contract — Builder API key auth only, with examples aligned to the live API.