# Rebrickable

> Rebrickable is a LEGO database and community site that matches the sets and parts a person owns to builds they can make, including fan designs (MOCs). Its REST API v3 reads the catalogue and a user's sets, parts and lists.

- Canonical: https://www.anchorterminal.com/tools/rebrickable
- Pricing: https://www.anchorterminal.com/tools/rebrickable#pricing
- Reviews: https://www.anchorterminal.com/tools/rebrickable#reviews
- Markdown: https://www.anchorterminal.com/tools/rebrickable.md (~5,700 tokens)
- Slim: https://www.anchorterminal.com/tools/rebrickable.min.md (~1,530 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/rebrickable.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT rebrickable.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-04

## Overview

**Grade F · 34.7/100 · rank #1255 of 1349 · #5 in Hobbies, sport & recreation · not agent-ready · confidence low**


## Assessment

Rebrickable's API v3 reads the LEGO catalogue and a person's sets, parts and lists through a public Swagger 2.0 spec with 62 operations and a free key. Calls are limited to about one a second, the docs call the API severely overloaded, user tokens come from a password, and the terms and Pro price were behind a bot check.

## Facts

| Field | Value |
| --- | --- |
| Vendor | Rebrickable (https://rebrickable.com) |
| Kind | HTTP API |
| Category | Hobbies, sport & recreation (https://www.anchorterminal.com/categories/hobbies) |
| Auth | API key · An API key generated in a registered account's profile settings, sent as `Authorization: key <key>` or as a `key` query or form parameter. Calls to a person's own sets, parts and lists take a user token minted by `POST /api/v3/users/_token/` from the account's username or email and password as form data, then used as a path parameter. No scopes, expiry or revocation documented. |
| Pricing | Freemium (Freemium) · An API key comes with a free registered account per the API page. A Pro Plan exists (the API docs show an error saying a feature needs it), but the Pro page and the terms answered a bot check, so its price and whether it gates any API feature are unread. |
| x402 | No · No x402, MPP or L402 on the API page, the API docs or the Swagger spec (checked 2026-11-03). |
| Licence | Proprietary service. The terms of service page answered a Cloudflare bot check on 3 November 2026 and was not read |
| Docs | https://rebrickable.com/api/v3/docs/ |
| llms.txt | not found |
| Last release | 2025-07-23 |
| Surface listed | The REST API v3 at rebrickable.com/api/v3/, read from the API page, the API docs, the Swagger 2.0 spec and robots.txt on 3 November 2026. No account was made and no call was made. The home page, terms, privacy, about, help, Pro, downloads and blog pages answered a Cloudflare bot check |
| Endpoints | 43 paths covering /lego/ colours, elements, minifigs, part categories, parts (with colours and sets), sets (with parts, minifigs and subsets) and themes; /users/ token, badges, profile, sets, sets/sync, parts, allparts, build, lost_parts, partlists and setlists. 62 operations including POST, PUT, PATCH and DELETE on a user's lists |
| Rate limits | About one request a second per account on average with a small burst allowance, 429 when exceeded, temporary IP bans of one to two days for ignoring 429s and permanent bans in extreme cases. The docs say the API is currently severely overloaded |
| Pagination | page and page_size (default 100, up to 1,000), ordering by field with a minus prefix for reverse, filters such as part_nums, search and theme_id, and inc_part_details, inc_color_details and inc_minifig_parts to change response size |
| Terms on automation | Unread. The terms page answered a bot check. robots.txt sets Content-Signal ai-train=no, search=yes, ai-input=yes, a crawl delay of 3 seconds and disallows the API paths for crawlers |
| Company | Rebrickable was started in 2011 by Nathan Thom in Australia per Wikipedia. The about page is behind the bot check, so the legal entity is unknown |
| Capabilities | hobbies.collections, hobbies.crafts |
| Tags | hosted, closed-source, api-key, freemium, free-tier, no-card, openapi, no-status-page |
| JSON | https://www.anchorterminal.com/api/v1/tools/rebrickable.json |

## Score breakdown (methodology v0.7, October 2026 research run)

Assessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: low. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points.

| Category | Weight | This run | Score (0–100) | Points |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 20 | 38 | 7.6 |
| Performance | 10% | pending | pending | n/a |
| Schema & documentation | 13% | 16.2 | 54 | 8.8 |
| Agent ergonomics | 13% | 16.2 | 60 | 9.8 |
| Security & auth | 14% | 17.5 | 10 | 1.8 |
| Payments & pricing | 10% | 12.5 | 30 | 3.8 |
| Task success | 10% | pending | pending | n/a |
| Maintenance & community | 7% | 8.8 | 6 | 0.5 |
| Transparency & trust (editorial 13, provenance 44) | 7% | 8.8 | 29 | 2.5 |
| Negative events | up to −15 | up to −15 | none recorded | 0 |
| **Total** | | | | **34.7 → F** |

### Why each score

- Reliability 38 (checked 2026-11-03): Read with the hosted lines. No status page found on the API page or docs (0). No readable incident history (5). Rate limit stated in numbers, one request a second on average with a small burst allowance (15). 429 responses are documented, with a warning that ignoring them brings a temporary IP ban of one to two days or a permanent one, but no Retry-After, backoff guidance or idempotency keys for the writes on user lists (8 of 15). No SLA (0). The API is v3 and not marked beta, though the docs say it is severely overloaded and new apps might be prevented (10). Total 38.
- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.
- Schema & documentation 54 (checked 2026-11-03): Public Swagger 2.0 spec at /api/v3/swagger/?format=openapi with 43 paths and 62 operations, but empty title and version, no security definitions and no response schemas beyond the codes (20 of 25). No llms.txt or Markdown docs (0). Every operation has a summary and description, several cut off mid-sentence, and none says when not to use it (10 of 20). Typed path, query and form parameters, no enums, and theme_id and part_cat_id typed as string on one path and number on another (8 of 15). No request examples in the spec, and only 200, 201 and 204 documented, no 4xx or 5xx; the docs page documents 429 (4 of 15). v3 in the path and a dated changelog back to 2017, with no stated versioning policy (12 of 15). Total 54.
- Agent ergonomics 60 (checked 2026-11-03): Responses can be sized with page_size, inc_part_details and inc_color_details, though there is no field selection (18 of 25). Pagination by page and page_size up to 1,000, ordering with a minus prefix, and filters such as part_nums, search and theme_id (18 of 20). Only the 429 case is documented, with no error body shape or codes (6 of 20). Reads are safe to retry; the POST, PUT, PATCH and DELETE operations on a user's sets and lists have no idempotency key (10 of 20). One header and few required parameters, but no official SDK in any language (8 of 15). Total 60.
- Security & auth 10 (checked 2026-11-03): One key per account with no scopes, no documented expiry or revocation, and it may be sent as a query parameter, so 10 less 10 (0 of 30). A user token minted from the account's username and password reaches every write on that person's lists, with no read-only mode (0 of 20). The catalogue is curated data, though MOC names and user list names are user content, with no guidance (10 of 15). No audit log or per-call visibility found (0 of 15). security.txt answered the bot check and no disclosure policy, bug bounty or certification was found (0 of 20). Total 10.
- Payments & pricing 30 (checked 2026-11-03): Read with the hosted rule. No x402, MPP or L402 (0). The API page says a key comes with a registered account and no API price is stated; the Pro Plan's price is behind the bot check, so no full price list is public (10 of 20). A free account gives a key with no card (20). A person must register and generate the key in the profile settings in a browser (0). Total 30.
- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.
- Maintenance & community 6 (checked 2026-11-03): Read for a closed service. The newest dated API change is 23 July 2025, more than 180 days before 3 November 2026 (0 of 30). One change in the last 90 days is not shown; the entry before July 2025 is from November 2020 (0 of 20). The docs say the API is severely overloaded and new apps may be prevented; the help and forum pages answered the bot check, so no support channel was read (3 of 15). No official SDK and no MCP registry entry (0 of 15). The spec is live but carries empty metadata (3 of 10). Total 6.
- Transparency & trust 29 (checked 2026-11-03): Closed service whose terms answered a Cloudflare bot check on 3 November 2026, so their clarity is unchecked (5 of 30). The privacy policy answered the same check, so no data handling statement was read (0 of 30, unchecked). The changelog records removals with dates, MOC support on 19 April 2020 and print_of on 23 July 2025, with no written notice period (8 of 20). Subprocessors and data locations were not read (0 of 20, unchecked). Total 13.

Fix list, everything this grade says the listing lacks, the biggest gain first (21 items). What it covers is at https://www.anchorterminal.com/fixes/rebrickable.md (JSON https://www.anchorterminal.com/fixes/rebrickable.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "rebrickable", "plan": "read"}`, free while the beta runs

### What we couldn't check

- unchecked: the terms of service at https://rebrickable.com/terms/, which the API docs say set the allowed uses of the API, including any clause on commercial use, caching or automated access. The page answered a Cloudflare bot check on 3 November 2026.
- unchecked: the privacy policy, retention and data location, behind the same bot check.
- unchecked: the Pro Plan's price and whether it gates any API feature. The docs show an error reading 'you need to upgrade to the Pro Plan before you can use this feature' without saying which feature.
- unchecked: the downloads page and the licence on the CSV data, the help page, the forum and security.txt, all behind the bot check.
- unchecked: the legal entity and country. Wikipedia says Nathan Thom started the site in Australia in 2011; the about page was unread.
- Judgement call. Listed rather than held because the API page, the docs and the Swagger spec, which carry the schema, ergonomics and reliability evidence, were readable; the pages behind payments and transparency were not, as for the etsy listing.
- firstReleased is 9 February 2017, the earliest dated entry in the API v3 changelog; the site itself dates from 2011 per Wikipedia.

### Sources

- API page: <https://rebrickable.com/api/> (seen 2026-11-03)
- API v3 docs, rate limits and changelog: <https://rebrickable.com/api/v3/docs/> (seen 2026-11-03)
- Swagger 2.0 spec: <https://rebrickable.com/api/v3/swagger/?format=openapi> (seen 2026-11-03)
- robots.txt: <https://rebrickable.com/robots.txt> (seen 2026-11-03)
- terms of service (bot check, unread): <https://rebrickable.com/terms/> (seen 2026-11-03)
- privacy policy (bot check, unread): <https://rebrickable.com/privacy/> (seen 2026-11-03)
- about page (bot check, unread): <https://rebrickable.com/about/> (seen 2026-11-03)
- downloads page (bot check, unread): <https://rebrickable.com/downloads/> (seen 2026-11-03)
- Pro page (bot check, unread): <https://rebrickable.com/pro/> (seen 2026-11-03)
- security.txt (bot check): <https://rebrickable.com/.well-known/security.txt> (seen 2026-11-03)
- Wikipedia, founder and launch: <https://en.wikipedia.org/wiki/Rebrickable> (seen 2026-11-03)

## Score history

Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/rebrickable/history.json

- 2026-11-03: graded 34.7 F (methodology 0.7)

## Who's behind it (provenance 44/100, checked 2026-11-03)

| Check | Finding | Points |
| --- | --- | --- |
| Legal entity named | not found | 0/20 |
| Domain age | rebrickable.com, no registry record we could read | 0/15 |
| Endpoint on the vendor's domain | rebrickable.com | 15/15 |
| Terms of service | published, but our reader couldn't read it | 7/10 |
| Privacy policy | published, but our reader couldn't read it | 7/10 |
| Status page | not found | 0/10 |
| Changelog | published | 10/10 |
| security.txt | could not be fetched | 0/10 |
| People named | 1 named with their role, none with a public profile | 7/10 |
| Support route | help pages | 5/5 |

The terms and privacy pages are linked from the API page but answered a Cloudflare bot check (HTTP 403, Just a moment) on 3 November 2026 and were not read, so the legal entity and any clause on automated access are unknown.

rebrickable.com/robots.txt carries Content-Signal ai-train=no, search=yes, ai-input=yes for all agents, Crawl-delay 3, and disallows /api/v3/lego/* and /api/v3/users/* among many paths; the API page, docs and spec are not disallowed and were read. Named bots such as CCBot, Amazonbot and AhrefsBot are blocked outright.

/.well-known/security.txt answered the same bot check, so its presence is unknown.

No status page found on the API page or docs.

The changelog is the dated list on the API docs page; its newest entry is 23 July 2025.

### Terms and privacy, as read

A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.

**Terms of service** (https://rebrickable.com/terms/), read 2026-11-03. Our reader couldn't read it (the page answered HTTP 403 to our reader).


**Privacy policy** (https://rebrickable.com/privacy/), read 2026-11-03. Our reader couldn't read it (the page answered HTTP 403 to our reader).


## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade)

### Key people

- Nathan Thom, Founder
- Note: The founder comes from Wikipedia, which cites a July 2024 Brickset interview with him; Rebrickable's own about page answered a Cloudflare bot check on 3 November 2026 and was not read, so no other team member, legal entity or address is recorded. No LinkedIn, X or GitHub account for him or the company is linked from a page we could read. Ownership is recorded as private on Wikipedia's account of a site started and run by its founder; the about, terms and privacy pages were unread, and no investor or funding was mentioned on any page read, so no further search was made.

### Getting support

- Help: https://rebrickable.com/help/
- Sources: https://rebrickable.com/api/, https://rebrickable.com/api/v3/docs/, https://en.wikipedia.org/wiki/Rebrickable

## Live (updated 2026-11-04 15:52 UTC)

- security.txt: unknown
- Always current: https://www.anchorterminal.com/api/v1/live/rebrickable.json

## Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.

## Strengths

- Public Swagger 2.0 spec with 43 paths and 62 operations covering sets, parts, colours, elements, minifigs, themes and a user's sets, parts, set lists, part lists and lost parts
- Rate limit stated in numbers (one request a second on average) with 429 responses, and page_size up to 1,000 with inc_part_details and inc_color_details flags to size responses
- A free API key with a registered account, and CSV downloads of the whole catalogue for bulk use
- Dated changelog back to 9 February 2017 that records removed fields and defaults

## Weaknesses

- The API docs say the API is severely overloaded and new apps might be prevented
- User tokens are minted by posting the account's username and password, and the key can travel as a query parameter
- The spec documents no 4xx or 5xx response, no enums and no security scheme, and several summaries are cut off
- Terms of service, privacy policy, Pro plan and downloads pages answered a bot check, so the terms on API use, retention and the Pro price are unread
- No status page, SLA, security.txt or official SDK found, and the newest API change is dated 23 July 2025



## Before you call it (notes for agents)

1. Send `Authorization: key <key>` and keep calls under one a second; a 429 ignored can bring a temporary or permanent IP ban
2. Use the CSV downloads for the whole catalogue; the docs say list endpoints are not for paging through all parts or sets
3. Ask the person to mint the user token themselves at /api/v3/users/_token/ rather than handling their password; the token reaches every write on their lists
4. Set `inc_color_details=0` and `inc_part_details` only when needed to keep part lists small, and page with `page_size` up to 1,000
5. Read rebrickable.com/terms/ with the person before commercial use; it answered a bot check for us and the API docs point to it for allowed uses

## Connect

First request:

```bash
curl -H "Authorization: key $REBRICKABLE_KEY" "https://rebrickable.com/api/v3/lego/sets/?search=millennium+falcon&page_size=10"
```

Through letme: https://letme.dev/rebrickable (letme picks it for hobbies.collections, the top-graded tool for the job, letme picks it for hobbies.crafts, the top-graded tool for the job). letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md

## Similar tools

Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.

| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |
| --- | --- | --- | --- | --- | --- | --- |
| Ravelry | F | 16.5 | 1311 | hobbies.crafts, hobbies.collections | no | https://www.anchorterminal.com/tools/ravelry.md |
| Strava MCP Connector + API | E | 45.8 | 1125 | same category (Hobbies, sport & recreation) | no | https://www.anchorterminal.com/tools/strava.md |
| Ride with GPS API | E | 45.2 | 1139 | same category (Hobbies, sport & recreation) | no | https://www.anchorterminal.com/tools/ride-with-gps.md |
| Ticketmaster Discovery API | E | 42.9 | 1176 | same category (Hobbies, sport & recreation) | no | https://www.anchorterminal.com/tools/ticketmaster.md |
| Chess.com Published-Data API | E | 40.8 | 1207 | same category (Hobbies, sport & recreation) | no | https://www.anchorterminal.com/tools/chess-com.md |

## Panel reviews (0)

Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .

Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md

## Notable

- Swagger 2.0 spec with 43 paths and 62 operations, no security definitions, no enums, no 4xx or 5xx responses and empty title and version fields (source: <https://rebrickable.com/api/v3/swagger/?format=openapi>)
- The API docs say accounts may send on average one request a second with a small burst allowance, that ignoring 429 responses can bring a temporary or permanent IP ban, and that the API is currently severely overloaded to the point where new apps might be prevented (source: <https://rebrickable.com/api/v3/docs/>)
- The dated changelog's newest entry is 23 July 2025 (print_of left out of part lists unless inc_part_details=1); the one before is 28 November 2020, and the earliest is 9 February 2017 (source: <https://rebrickable.com/api/v3/docs/>)
- Full catalogue data is meant to come from the CSV downloads page rather than the API, per the API page (source: <https://rebrickable.com/api/>)
- robots.txt carries Content-Signal ai-train=no, search=yes, ai-input=yes, a crawl delay of 3 seconds and disallows /api/v3/lego/* and /api/v3/users/* for crawlers (source: <https://rebrickable.com/robots.txt>)
- The home page, terms, privacy policy, about, help, Pro, downloads and blog pages answered a Cloudflare bot check (403) on 3 November 2026, while the API page, docs and spec were readable

- #5 of 6 in Best hobby, sport and recreation APIs for AI agents: https://www.anchorterminal.com/best/hobbies/index.md
- All 3 hobbies comparisons: https://www.anchorterminal.com/compare/hobbies/index.md

## Compare

- [Ravelry vs Rebrickable](https://www.anchorterminal.com/compare/ravelry-vs-rebrickable.md): F 16.5 vs F 34.7

## Verify this listing

For the vendor. The badge or a plain link to this page verifies the listing, from a page on rebrickable.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "rebrickable", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify

HTML badge:

```html
<a href="https://www.anchorterminal.com/tools/rebrickable"><img src="https://www.anchorterminal.com/badges/rebrickable.svg" alt="Rebrickable on Anchor Terminal" height="20"></a>
```

Markdown badge, for a README:

```markdown
[![Rebrickable on Anchor Terminal](https://www.anchorterminal.com/badges/rebrickable.svg)](https://www.anchorterminal.com/tools/rebrickable)
```

Plain link:

```html
<a href="https://www.anchorterminal.com/tools/rebrickable">Rebrickable on Anchor Terminal</a>
```

## Share this listing

For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Rebrickable is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.

- Dark: https://www.anchorterminal.com/assets/share/rebrickable-dark.png
- Light: https://www.anchorterminal.com/assets/share/rebrickable-light.png

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
