AI Agents & Claude Code Plugins
Every 23blocks block is agent-ready — and ships an official Claude Code plugin from our public marketplace: 19 plugins, 205 skills, giving your AI agent full working knowledge of each block's API — endpoints, identity registration, conventions, and the gotchas.
The plugins are open source, like the blocks: github.com/23blocks-OS/ai-agents.
Install
# one-time: add the 23blocks marketplace
claude plugin marketplace add https://github.com/23blocks-OS/ai-agents
# then install any block's plugin, e.g.
claude plugin install forms-block
Configuration
Every plugin reads three environment variables:
| Variable | Description |
|---|---|
BLOCKS_API_URL | Base URL of the block's API |
BLOCKS_API_KEY | Your app's API key (pk_live_* / sk_live_*) |
BLOCKS_AUTH_TOKEN | The authenticated user's token |
Register identity first
Each block is autonomous: before making private calls to a block, the user must be registered with that block's identity endpoint — otherwise calls return 401.
Only user_unique_id is required. email and phone are optional fields used for notification routing.
The plugin catalog
| Plugin | Drives | Docs |
|---|---|---|
auth-block | Authentication, users, MFA, SSO | Auth |
assets-block | Digital asset management | Assets |
campaigns-block | Campaign management | — |
company-block | Teams & organizations | Companies |
content-block | Headless CMS | Content |
conversations-block | Realtime messaging, presence, WebRTC | Real Time |
crm-block | Contacts & relationships | CRM |
files-block | File storage & delivery | Files |
forms-block | Forms & validation | Forms |
geolocation-block | Maps, locations & geofences | Geolocation |
jarvis-block | AI agents, prompts & workflows | AI / Jarvis |
onboarding-block | User journeys & activation | Onboarding |
products-block | Product catalog & inventory | Products |
rag-block | Retrieval-augmented generation | — |
rewards-block | Loyalty, coupons & badges | Rewards |
sales-block | Subscriptions & payments | Sales |
search-block | Full-text search | Search |
university-block | Learning management | University |
wallet-block | Balances & ledger | Wallet |
Why blocks work well with agents
- Clear REST contracts — standard JSON:API responses and predictable error shapes an LLM can parse reliably.
- One convention across the platform — an agent that learns one block has learned the pattern for all of them.
- Skills encode the gotchas — identity registration order, required headers, idempotency keys: the plugin knows, so your agent doesn't guess.
Each block's own documentation page carries its plugin install snippet — see the catalog table above.