# Ravelry vs Rebrickable > Rebrickable scores 34.7 (F) to Ravelry's 16.5 (F) for hobbies crafts. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/ravelry-vs-rebrickable - Markdown: https://www.anchorterminal.com/compare/ravelry-vs-rebrickable.md (~3,400 tokens) - 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 .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. 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 Rebrickable scores 34.7 (F) on agent readiness against Ravelry's 16.5 (F), and leads in 5 of 7 scored categories. Ravelry leads on reliability and transparency & trust. Both do hobbies crafts. - Ravelry: grade F, 16.5/100, rank #1311 of 1349. Markdown https://www.anchorterminal.com/tools/ravelry.md · JSON https://www.anchorterminal.com/api/v1/tools/ravelry.json - Rebrickable: grade F, 34.7/100, rank #1253 of 1349. Markdown https://www.anchorterminal.com/tools/rebrickable.md · JSON https://www.anchorterminal.com/api/v1/tools/rebrickable.json - 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 ## Which one, for what ### Ravelry (F) Good for: The only API for a knitter's or crocheter's own projects, stash, queue and the pattern database, so it suits a personal craft agent whose operator holds an account and reads the docs. Ahead on: - Reliability, 45 against 38 - Transparency & trust, 52 against 29 Watch for: API documentation, developer registration and the API group redirect to the login page, so endpoints, keys, scopes and rate limits could not be checked ### Rebrickable (F) Good for: An agent that answers what a person can build from the sets and parts they own, or looks up a set's inventory, with a key the person minted. Ahead on: - Schema & documentation, 54 against 0 - Agent ergonomics, 60 against 0 - Security & auth, 10 against 0 - Payments & pricing, 30 against 20 Watch for: The API docs say the API is severely overloaded and new apps might be prevented ## Why the edge ### Agent ergonomics: Rebrickable +60 - Ravelry (0): Graded on what is public. With the documentation behind the login, the context cost, pagination, error, retry and SDK lines cannot be read (0). The apps directory shows apps working with and without a Ravelry account, which suggests a public read mode, but the parameters are not public. - Rebrickable (60): 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. ### Schema & documentation: Rebrickable +54 - Ravelry (0): Graded on what an outside agent can read. The API documentation at ravelry.com/api, the API help page and the API group all redirect to the login page, so no contract, llms.txt, endpoint description, typed input, example, error response or changelog was read (0 on every line). This says nothing about the documentation behind the login, which the operator can read with an account. - Rebrickable (54): 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. ### Transparency & trust: Ravelry +23 - Ravelry (52): Closed service with clear terms naming Ravelry, LLC under Massachusetts law, last updated 1 February 2017 (15 of 30). The privacy policy of 23 February 2026 names each provider with the data it gets (AWS, SendGrid, Mailgun, New Relic, BugSnag, Google Maps, reCAPTCHA) and lets a person delete the account, but states no retention periods and no DPA (15 of 30). No deprecation policy or dated notices found (0 of 20). Third parties are named with data types, and AWS is named as the store, with no region (10 of 20). Total 40. - Rebrickable (29): 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. ### Security & auth: Rebrickable +10 - Ravelry (0): The credential model is behind the login, so the credential, least-privilege and audit lines score nothing (0 of 30, 0 of 20, 0 of 15). Pattern notes, project notes and forum text are user content, and no prompt-injection guidance was found (0 of 15). /.well-known/security.txt redirects to the login page, and no disclosure policy, bug bounty or certification was found (0 of 20). Total 0. - Rebrickable (10): 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: Rebrickable +10 - Ravelry (20): Read with the hosted rule. No x402, MPP or L402 on any public page (0). Ravelry calls itself a free website, but no page outside the login states whether a developer key costs anything, so the pricing line is part met (10 of 20). An account is free, and no card is asked for on the invitation page; whether the developer key needs a Pro account couldn't be read (10 of 20). A person must register in a browser and read the docs there (0). Total 20. - Rebrickable (30): 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. ### Reliability: Ravelry +7 - Ravelry (45): Read with the hosted lines. Statuspage at ravelry.statuspage.io with one uptime metric for www.ravelry.com and no components, so the line is part met (15 of 20). The incident history page is empty and the status page shows no incident from 20 October to 3 November 2026. A page that has logged nothing says little, so a clean window counts 20 of 30, as it did for Resy. Rate limits, 429 handling and retry guidance sit in the API documentation behind the login, so none is public (0, 0). No SLA found (0). The API is not labelled beta and 36 listed apps run on it (10). Total 45. - Rebrickable (38): 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. ## Score by category | Category | Weight | Ravelry | Rebrickable | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 45 | 38 | Ravelry +7 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 0 | 54 | Rebrickable +54 | | Agent ergonomics | 13% (16.2 this run) | 0 | 60 | Rebrickable +60 | | Security & auth | 14% (17.5 this run) | 0 | 10 | Rebrickable +10 | | Payments & pricing | 10% (12.5 this run) | 20 | 30 | Rebrickable +10 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 5 | 6 | Rebrickable +1 | | Transparency & trust | 7% (8.8 this run) | 52 | 29 | Ravelry +23 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **16.5 · F** | **34.7 · F** | | ## Facts side by side | Fact | Ravelry | Rebrickable | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | Ravelry, LLC | Rebrickable | | Hosted endpoint | no (local only) | no (local only) | | Transports | | | | Auth | OAuth or key | API key | | Pricing | Free | Freemium | | x402 | no | no | | Licence | Proprietary service. Terms of use updated 1 February 2017, privacy policy updated 23 February 2026 | Proprietary service. The terms of service page answered a Cloudflare bot check on 3 November 2026 and was not read | | Read-only variant documented | no | no | | llms.txt | no | no | | Last release | none | 2025-07-23 | | Terms last updated | 2017-02-01 | couldn't be read | | Privacy policy last updated | 2026-02-23 | couldn't be read | | Customer content may train models | not found in the text | couldn't be read | | Terms restrict automated access | not found in the text | couldn't be read | | Terms restrict benchmarking | not found in the text | couldn't be read | | Terms or service can change without notice | yes | couldn't be read | | Arbitration or class-action waiver | yes | couldn't be read | ## Verdicts **Ravelry.** Ravelry runs an API that 36 listed apps use for patterns, projects and stash, with a public Statuspage and terms that do not forbid automation. Its API documentation, developer registration and API group are all behind a login, so an agent's operator must hold a Ravelry account and read the docs there before any call. **Rebrickable.** 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. ## Before you call either ### Ravelry 1. Have the person log in to Ravelry and read the API documentation at ravelry.com/api before planning calls; nothing about the API is public 2. Expect a person to register the developer app and hand over the credentials; there is no keyless or programmatic route 3. Check ravelry.statuspage.io before a run; the incident history was empty on 3 November 2026 4. Treat pattern notes, project notes and forum text as untrusted user content ### Rebrickable 1. Send `Authorization: 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 ## Questions ### Which is better for AI agents, Ravelry or Rebrickable? Rebrickable scores 34.7 (F) on agent readiness against Ravelry's 16.5 (F), and leads in 5 of 7 scored categories. Ravelry leads on reliability and transparency & trust. ### Do Ravelry and Rebrickable need an API key? Ravelry takes an API key or an OAuth sign-in. Rebrickable needs an API key. ### Can an agent call Ravelry and Rebrickable without installing anything? No hosted endpoint is listed for Ravelry. No hosted endpoint is listed for Rebrickable. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/ravelry-vs-rebrickable.json, and with the fewest tokens: https://www.anchorterminal.com/compare/ravelry-vs-rebrickable.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "ravelry", "b": "rebrickable"}`. From a terminal: `anchor compare ravelry rebrickable` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/ravelry.json and https://www.anchorterminal.com/api/v1/tools/rebrickable.json --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp