Bindry
Sign in

Developers

Reach Bindry without a browser.

A script, a CI pipeline, another tool's plugin, or your own product — three ways in, none of them needing the web app.

The fastest way in

The bindry CLI

Search the Library, pull a Binder or a skill into local skill files, and check whether they've drifted — from a terminal, with no code of your own to write. Public Binders and skills need no login at all; your own private ones need a key from below.

terminal
# no install needed
npx bindry search "git flow" --kind Binder

# pull it into local skill files
npx bindry pull git-flow-command-center --out .claude/skills

Source and full command reference: github.com/bindryai/Plugins

Building your own tool

The public REST API

Everything published to the Library — Public visibility, not archived — is reachable with a plain HTTP request. No account, no key, no header. This is the same API the CLI itself calls.

Base URL

https://api.bindry.ai

Anonymous requests are rate-limited to 30 per 10 seconds, per IP. A single search, fetch, or export — what a normal CLI command or a one-off script does — stays well under that; a bulk job pulling many items in a tight loop should pace itself.

Endpoints

GET /api/public/catalog

Search the public Library. Every parameter above is optional — with none, it lists everything, paginated.

GET /api/public/catalog/binders/{slugOrId}

One Binder's listing and ordered skill composition, by Library slug or GUID.

GET /api/public/catalog/binders/{slugOrId}/export

The Binder compiled to a target format, as a JSON envelope ({ content, fileName, contentType, ... }). Add ?target=.

GET /api/public/catalog/skills/{slugOrId}

One standalone skill's listing, by slug or GUID.

GET /api/public/catalog/skills/{slugOrId}/export

Same compilation as the Binder export, for a single skill.

Search parameters (all optional)

q — Free-text search across title, summary, and tags.
kind — "Binder" or "Skill". Omit to search both.
category — Exact category match, e.g. "development".
target — Only items that support this export target.
tags — Repeat the parameter for more than one tag.
skip — Pagination offset. Default 0.
take — Page size. Default 50.

Export targets (?target=)

SkillBundle — Structured JSON — one object per skill, ready to compile into a skill file. What the CLI and the coding-agent plugins use.
Markdown — A single human-readable Markdown document.
AgentsMd — Formatted for an AGENTS.md file.
Copy — Plain text: title, summary, instructions, no formatting.

Try it now

curl
# search the Library
curl "https://api.bindry.ai/api/public/catalog?q=git+flow&kind=Binder"

# fetch one Binder's detail
curl "https://api.bindry.ai/api/public/catalog/binders/git-flow-command-center"

# compile it to Markdown
curl "https://api.bindry.ai/api/public/catalog/binders/git-flow-command-center/export?target=Markdown"

Need your own private Binders and skills?

Everything above works with no login for public items. For your own workspace's private ones, the same endpoints (under /api/binders and /api/skills) accept a Personal API Key — the same key the CLI's bindry login and the coding-agent plugins already use, and the same one the MCP server accepts for a live-connected agent.

Get an API key Browse the plugins