Hand your agent the library_

For agents without an MCP client that can sign in: device login, the same pattern as gh auth login, gets them their own API key. The agent asks for a code and shows you a link. You sign in, approve and subscribe if you haven't yet, and the agent collects the key on its next poll. It never touches your login or payment.

curl -X POST https://assembli-rho.vercel.app/api/agent/login \
  -H "content-type: application/json" -d '{"client_name":"Claude Code"}'

Show the user verification_uri_complete, then poll every 5 seconds until the response has api_key (it returns authorization_pending while waiting):

curl -X POST https://assembli-rho.vercel.app/api/agent/token \
  -H "content-type: application/json" -d '{"device_code":"asmd_…"}'

On the open MCP endpoint, the connect_account and finish_connect tools do the same. Approvals happen at /connect, and every key shows up on your account page, where you can revoke it.

Streamable HTTP at https://assembli-rho.vercel.app/mcp with search_components, list_categories and get_component (full source and install steps, with Pro). It signs clients in with OAuth: the first connection opens your browser, and the client keeps the token it's issued. Tokens are API keys, so they show up on your account page, where you can revoke them.

claude mcp add --transport http assembli https://assembli-rho.vercel.app/mcp

https://assembli-rho.vercel.app/api/mcp is the same server without sign-in: search is open, get_component returns source for an API key, and it adds the device-login tools connect_account and finish_connect. Use it from scripts and CI:

claude mcp add --transport http assembli https://assembli-rho.vercel.app/api/mcp \
  --header "Authorization: Bearer $ASSEMBLI_API_KEY"

Every component is a registry item at /r/<slug>.json. The CLI writes it to components/<slug>/<slug>.tsx and installs npm and shadcn/ui dependencies. Items need an API key, so add the @assembli registry to your project's components.json once:

{
  "registries": {
    "@assembli": {
      "url": "https://assembli-rho.vercel.app/r/{name}.json",
      "headers": {
        "Authorization": "Bearer ${ASSEMBLI_API_KEY}"
      }
    }
  }
}

Put your key in .env.local as ASSEMBLI_API_KEY=asm_…, then:

npx shadcn@latest add @assembli/<slug>

Index of all items: /r/registry.json

Append .md to any page, or send Accept: text/markdown. Component pages include install steps, and with an API key the full source and a usage example.

curl -H "Authorization: Bearer $ASSEMBLI_API_KEY" https://assembli-rho.vercel.app/components/<slug>.md

• GET/api/components?q=&category=&subcategory=&tag=&limit=Search and filter with the same ranking as ⌘K. subcategory narrows a category to one type, e.g. saas landing pages. An unfiltered q also returns the matching categories.
• GET/api/components/<slug>Metadata and install commands. With an API key, source files and a ready-to-paste agent prompt.
• GET/api/components/<slug>?format=packageOne JSON document for pnpm registry:import (API key).
• GET/api/categoriesCategories with counts.

curl "https://assembli-rho.vercel.app/api/components?q=pricing&limit=5"

/llms.txt indexes every component with links to its Markdown. Source is served one component at a time.

Components live in registry/components/<slug>/ as meta.json, <slug>.tsx and demo.tsx. The repo's AGENTS.md has the conventions. The CLI is non-interactive and supports --json:

pnpm registry:new my-card --title "My Card" --category cards
pnpm registry:import ./generated.json
pnpm registry:validate --json