ui.eindev.ir APIui.eindev.ir ↗
Search and retrieve liquid glass UI components from the EinUI registry. Get metadata, npm dependencies, and full source code via 2 endpoints.
curl -X GET 'https://api.parse.bot/scraper/768785e1-c914-4526-8800-26d8721f92dc/search_components' \ -H 'X-API-Key: $PARSE_API_KEY'
Search and list liquid glass components from the EinUI registry. Returns component metadata including name, title, description, dependencies, and file paths. Supports filtering by text query (matched against name, title, and description) and by category (matched against component name).
| Param | Type | Description |
|---|---|---|
| query | string | Search text to filter components. Matched case-insensitively against component name, title, and description. Omitting returns all components. |
| category | string | Category filter matched against component name (e.g. 'glass', 'widget', 'block'). Omitting returns all categories. |
{
"type": "object",
"fields": {
"total": "integer",
"components": "array of component objects with name, title, type, description, dependencies, and files"
},
"sample": {
"total": 17,
"components": [
{
"name": "glass-select",
"type": "registry:component",
"files": [
"registry/liquid-glass/glass-select.tsx"
],
"title": "Glass Select",
"description": "A liquid glass styled select dropdown with frosted glass styling.",
"dependencies": [
"@radix-ui/react-select",
"lucide-react"
]
}
]
}
}About the ui.eindev.ir API
The EinUI Registry API exposes 2 endpoints for discovering and fetching liquid glass UI components from the EinUI component registry. Use search_components to filter components by text query or category, returning fields like name, title, description, dependencies, and file paths. Use get_component to pull the complete source code, type, and dependency list for any specific component by name.
Searching the EinUI Registry
The search_components endpoint returns an array of component objects along with a total count. Each object includes name, title, type, description, dependencies (npm packages the component requires), and files (paths to the component's source files). The query parameter filters results case-insensitively against name, title, and description. The category parameter narrows results by matching against name, which works for category prefixes like glass, widget, or block. Omitting both parameters returns the full registry.
Fetching Full Component Details
The get_component endpoint accepts a name string — discoverable from search_components results — and returns the complete component record. The files array in the response includes objects with path, type, and content, where content is the full source code of each file. The dependencies array lists the npm package names required to use the component. Fields title and description provide human-readable context alongside the raw code.
Practical Notes
Component names follow a consistent hyphenated pattern (e.g. glass-card, glass-button, glass-avatar), making it straightforward to construct get_component calls directly once you know naming conventions. The files array can contain multiple file objects per component, covering cases where a component is split across more than one source file.
- Auto-generating a component picker UI by listing all EinUI registry entries with their titles and descriptions.
- Pulling the full source code and npm dependencies for a
glass-cardcomponent to embed in a design system scaffold. - Filtering registry components by category (e.g.
widget) to build a curated showcase of widget-type elements. - Extracting the
dependenciesfield across all components to produce a consolidated npm install command. - Building a documentation site that renders component metadata and live code previews from registry data.
- Syncing a local component library with the EinUI registry by diffing fetched component
filesagainst local versions.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does EinUI have an official developer API for its component registry?+
What does `get_component` return beyond what `search_components` already includes?+
search_components returns metadata fields — name, title, type, description, dependencies, and file paths. get_component adds the actual source code: each file object in the files array includes a content field with the full component source, which is not present in search results.Does the API expose version history or changelogs for components?+
Can I filter components by their npm dependency list?+
dependencies field is returned per component but cannot be used as a filter parameter. You can fork it on Parse and revise to add dependency-based filtering as an endpoint parameter.How should I discover valid component names before calling `get_component`?+
search_components with no parameters to retrieve the full registry. Each object in the components array includes a name field (e.g. glass-button, glass-avatar) that can be passed directly to get_component as the required name input.