PrusaLink
by Prusa Research a.s. HTTP API in CAD, engineering & fabrication
Prusa Research a.s. · prusa3d.com since 2013 · who's behind it
PrusaLink is Prusa Research's local web interface and HTTP API for Original Prusa 3D printers, built into current models or run on a Raspberry Pi. It reports status, uploads files and starts, pauses and stops prints over the local network.
Best for An agent on the owner's network that queues and watches prints on an Original Prusa printer.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in CAD. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
Assessment. An agent on the same network can read printer status, upload G-code and start, pause or stop a print through a documented OpenAPI surface with one credential per printer. The spec is a 2024 draft, the Pi edition's last release is July 2024 with 102 open issues, and there is no read-only mode, pagination or SDK.
Facts
Access how an agent reaches and pays for it
- Auth
- OAuth or key
- Pricing
- Free
- x402
- No
- Licence
- The Prusa-Link Python package declares its licence as Freeware in setup.py and ships no licence file. The Prusa-Link-Web interface is GPL-3.0, and its OpenAPI spec names AGPLv3. The firmware editions are part of Prusa's printer firmware.
- Capabilities
- cad.print
Where it lives packages, source, docs and releases
- Packages
pypiPrusaLink- llms.txt
- not found
- Last release
- GitHub stars
- 219
From our research 7 facts checked against the vendor's pages
- Surface listed
- The local HTTP API under /api/v1 as described by the OpenAPI spec in prusa3d/Prusa-Link-Web, the prusa3d/Prusa-Link Python edition (clones of both repositories), the PrusaLink and Prusa Connect help articles and guide, and Prusa Research's legal and security pages, read on 3 November 2026. No printer was called
- Editions
- A firmware edition on Buddy and xBuddy printers (CORE One, MK4/S, MK3.9, MK3.5, XL, MINI/+) and SL1 and SL1S, and a Python edition for a Raspberry Pi attached to an MK3/S/+ or MK2.5/S. The Pi edition's ChangeLog bumps its API version to match the one xBuddy reports
- Endpoints
- GET /api/version, /api/v1/info, /api/v1/status, /api/v1/job, /api/v1/storage, /api/v1/transfer; DELETE job and transfer by id; PUT job pause, resume and continue; GET, PUT, POST, HEAD and DELETE on /api/v1/files/{storage}/{path}; camera list, snapshot, config and Connect registration; GET and POST /api/v1/update/{env}
- Enums
- Printer state IDLE, BUSY, PRINTING, PAUSED, FINISHED, STOPPED, ERROR, ATTENTION, READY; job state PRINTING, PAUSED, FINISHED, STOPPED, ERROR; storage LOCAL, SDCARD, USB; print file printer_model MK3, MK3S, MINI
- Prusa Connect
- PrusaLink can register the printer with connect.prusa3d.com, Prusa's cloud service, which has its own terms and a camera API. Prusa Connect is not graded here
- Clients
- PrusaSlicer sends files to PrusaLink by DNS service discovery and the API, per the help centre. No official SDK; third-party libraries exist
- Legal entity
- Prusa Research a.s., Partyzánská 188/7a, 170 00 Prague 7, Czech Republic, Id. No. 06649114, named in the website terms, the privacy policy and the about page
Facts verified 3 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
Strengths
- OpenAPI 3.0.1 spec with enums for printer and job states and documented 401, 404 and 409 responses on most operations
- Free, local and offline; the printer needs no cloud account, and the API answers on the printer's own address
- Shipped in the firmware of every current Original Prusa printer, with a Raspberry Pi edition for the MK3 and MK2.5
- Prusa publishes a valid security.txt and a disclosure policy that rewards reports
- Source of the Pi edition and the web interface on GitHub, with CI and dependabot updates
Weaknesses
- One credential per printer, a digest password or an API key, with no scopes, read-only mode or confirmation before a stop or delete
- The Pi edition's last release is 0.8.1 of 2 July 2024, and the spec is marked 1.0.0-draft with malformed YAML lines
- 102 open issues with no visible maintainer reply in the newest 25, and no official SDK
- No pagination, filtering or output-size control on file listings, and no idempotency keys
- The Python package's licence is declared as Freeware with no licence file, while the web interface is GPL-3.0
Before you call it notes for agents
- Reach the printer by its local address only; use HTTP digest with the username and password from Settings > Network > PrusaLink on a Buddy printer, or X-Api-Key on the Pi edition
- Check GET /api/v1/status before any change and expect 409 when the printer is busy; a stop or delete has no confirmation step
- Upload with PUT /api/v1/files/{storage}/{path}, set Print-After-Upload to ?1 to start at once, and send Overwrite ?1 only when replacing a file on purpose
- Read GET /api/version first, since the Pi edition and the firmware editions report different API versions and the Pi edition lacks Buddy-only fields
- Expect no rate limits or retry guidance; poll status at a modest interval rather than on every turn
Who's behind it provenance 83/100
- Legal entity namedPrusa Research a.s.20/20
- Domain ageprusa3d.com, registered 2013-10-30 (13 years)15/15
- Endpoint on the vendor's domainno hosted endpointn/a
- Terms of serviceread, states 6 of the 7 things a reader expects, and has 1 clause that costs points7.1/10
- Privacy policyread, states 5 of the 8 things a reader expects7.8/10
- Status pagenot found0/10
- Changelogpublished10/10
- security.txtvalid10/10
- People named1 named with their role, none with a public profile7/10
- Support routea support address, help pages, a community5/5
Terms and privacy, as read
Terms of service gives no date, states 6 of 7, 2 to know
TL;DR Gives no date. States 6 of the 7 things a reader expects. To know before relying on it, limits on automated access and cut-off without notice or for any reason.
Restricts automated accesscosts points
In particular, the user is obliged to refrain from any activities aimed at unauthorised copying, manual or automated extraction of the contents of the Websites including scraping, artificial increase in inquiries and burdening of the accessibility capacity of PRUSA Services
A rule against bots, scrapers or automated means can cover an agent, depending on how the vendor reads it.
Says access can be ended without notice or for any reason
The Provider reserves the right to restrict the user's access to PRUSA Services without prior notice and without any compensation in the event of a breach of these GTC, generally binding legal regulations or good morals within the meaning of applicable law by the user
The vendor can suspend or close an account without warning, which would stop an agent mid-task.
Gives the date it was last updated
Not found in the text.
Without a date nobody can tell which version they agreed to.
Names the governing law or courts The law of Czech Republic
Any disputes arising from the relationships hereunder shall be resolved by the competent courts of the Czech Republic, exclusively in accordance with the laws of the Czech Republic.
Says where a dispute would be heard and under whose law.
States a limit on its liability Capped at the fees paid in the 12 months before the claim or EUR 500
Where the Provider's liability under Article 3.3 is not excluded, the Provider's liability for damage caused to the user in any one calendar year is limited to the amount of the price paid by the user for PRUSA Services in the preceding 12 months, subject to a maximum of EUR 500.
Says the most the vendor would owe if the service causes a loss.
Says how the agreement or account can be ended
from annual to monthly), all ancillary services, bonuses and benefits shall automatically terminate without any entitlement to compensation.
Says when the vendor can cut off access and what notice it gives.
Says how changes to the terms are announced Gives 30 days of notice before a change
In the case of free services: modify the scope of or discontinue the provision of services with at least 30 days' prior notice via e-mail or a platform notification.
Says whether a customer hears about a change before it binds them.
Lists what users may not do
however, for the duration of such a situation, you will not be able to use the relevant PRUSA Service beyond the agreed scope.
The acceptable-use rules an agent acting for a user has to stay inside.
Refers to a service level or uptime commitment
Types of printers (FDM/SLA)
Says whether availability is promised and where the promise is written.
Liability in any calendar year is limited to the price paid in the preceding 12 months, up to EUR 500, except for intent, gross negligence or injury.
Where the Provider's liability under Article 3.3 is not excluded, the Provider's liability for damage caused to the user in any one calendar year is limited to the amount of the price paid by the user for PRUSA Services in the preceding 12 months, subject to a maximum of EUR 500.
Noted by a second reader on 2026-11-03.
Materials and files from PRUSA Services are not intended for professional use or as a substitute for certified or regulated products.
The underlying materials, print or source files and other information available through PRUSA Services are not intended for professional use or as a substitute for certified, accredited or otherwise regulated products.
Noted by a second reader on 2026-11-03.
Users may request an export of their stored data in a commonly used format.
The user has the right to request an export of their stored data in a commonly used format.
Noted by a second reader on 2026-11-03.
The document · read 2026-11-03 · 6,609 words
Privacy policy gives no date, states 5 of 8
TL;DR Gives no date. States 5 of the 8 things a reader expects, and we didn't find what is collected or who else gets the data. The rules found no clause to flag.
Gives the date it was last updated
Not found in the text.
Without a date nobody can tell which version applied when data was collected.
Says what personal data is collected
Not found in the text.
The basic statement a privacy policy exists to make.
Says how long data is kept Names a period of 5 years
For the purposes of sending commercial communications, we use the e-mail address you provided, which we keep for a period of 5 years from its provision.
Says when data sent to the service is deleted.
Says who else receives the data
Not found in the text.
Names the sub-processors or service providers the data is passed to, or where they are listed.
Says whether personal data is sold or shared for advertising
General Terms and Conditions of Use of the PRUSA Websites
A plain statement either way.
Says what rights people have over their data
Under the terms of the GDPR, you have the following rights as a data subject:
Access, correction, deletion and objection, and how to use them.
Gives a privacy contact Gives an email address, hidden from our reader by the page
To exercise the above rights, you can use the contact form on the PRUSA websites, the e-mail address [email protected] or you can contact us by sending a written request to Partyzánská 188/7a, Holešovice, 170 00 Prague 7, Czech Republic.
An address or officer to send a request to.
Says where data is transferred or stored Relies on standard contractual clauses
the right to receive a copy of the standard contractual clauses concluded by the Controller under Article 46 of the GDPR.
The countries data goes to and the safeguard used.
The document · read 2026-11-03 · 3,431 words
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
The general terms and conditions of use of the Prusa websites apply from 20 April 2026 and name Prusa Research a.s. Article 9.1 forbids manual or automated extraction of website content including scraping, recorded as a fact; the GitHub repositories and the help centre were read, and help.prusa3d.com's robots.txt asks for 10 seconds between requests, which was kept.
The privacy policy is in effect from 1 August 2022 with retention periods by service and a list of processors and group companies.
www.prusa3d.com/.well-known/security.txt names security@prusa3d.com, expires 1 June 2027 and links the security policy page.
status.prusa3d.com exists for Prusa's online services; it is not recorded for PrusaLink, which runs on the printer.
RDAP gives prusa3d.com a registration date of 30 October 2013.
pypi.org answered the PrusaLink project page with a script challenge, so the PyPI release list was not read.
Checked 2026-11-03 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
- Josef PrůšaFounder
Researched 3 November 2026 from public pages. Prusa Research's about page names Josef Průša as founder and no other executives. The page links the company's Facebook, Instagram, Twitter and YouTube accounts; no LinkedIn, X or GitHub account for Josef himself is linked from the pages read, so none is listed. PrusaLink's maintainers are seen only as GitHub logins in the repository. Investors were looked for on the about page, which says the company began with no investors and no Kickstarter campaign, and in the website terms and privacy policy, which name Prusa Development a.s. and other group companies; no funding round or outside investor was found and no outside search was made for a founder-run company that says it took none. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Live watched around the clock · updated 2026-11-04 15:53 UTC
- security.txt valid, expires 2027-06-01T00:00:00.000Z · 3 hours ago
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/prusalink.json
Notable
- OpenAPI 3.0.1 spec titled PrusaLink Web, version 1.0.0-draft, with 19 paths and 33 operations under /api/v1 for info, status, job, storage, transfer, files, cameras and update, last changed on 18 July 2024 source
- Built into CORE One, XL, MK4/S, MK3.9, MK3.5, SL1 and SL1S firmware; the MINI/+ needs its Wi-Fi module, the MK3/S/+ a Raspberry Pi Zero over GPIO or a Pi 3, 4 or 5 over USB, and the MK2.5/S a Pi over USB. xBuddy printers need firmware 6.4.0 or newer source
- A print is started with POST /api/v1/files/{storage}/{path} and a file uploaded with PUT and the Print-After-Upload and Overwrite headers; jobs are paused, resumed and stopped by id, with 409 when the printer is busy source
- The Pi edition's last release is 0.8.1 of 2 July 2024; the ChangeLog has an unreleased 0.9.0 and the repository was committed to on 17 October and 3 November 2026 source
- 102 open issues on 3 November 2026, the newest 25 opened between August 2024 and May 2026 with no visible maintainer reply source
- Prusa's security.txt names security@prusa3d.com with a policy page that promises a reply within 5 working days and a reward for relevant reports, valid to 1 June 2027 source
- Prusa's website terms of 20 April 2026 forbid automated extraction of website content including scraping, and name PrusaLink and Prusa Connect as services under separate Prusa Connect terms source
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using PrusaLink, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used PrusaLink, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 3 November 2026 from public evidence, against the published checklist. Confidence medium. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 3 November 2026 | 16%20 | 11.0 | |
| Read with the local-software lines, as software the owner runs on the printer or a Raspberry Pi. The Pi edition installs from the PrusaLink package on PyPI or a Raspberry Pi OS image, with supported Pi models and printer firmware 3.14.0 stated in the release notes, and the firmware editions ship with the printer; the PyPI page answered a script challenge and was not read (17 of 20). A python-tests.yml workflow and four test modules are in the repository, and a CI fix was committed on 9 October 2026, but no run result was read (15 of 25). 102 open issues on 3 November 2026; the newest 25 run from August 2024 to May 2026, include print failures, parse errors and a Pi that stops after reboot, and show no maintainer reply (8 of 25). The ChangeLog marks the 0.7.1rc1 rename of ro to read_only as a breaking API change and records API version bumps, but there is no stated versioning rule (10 of 15). The Pi edition is 0.8.1 and the spec is 1.0.0-draft, though both have shipped to customers for years (5 of 15). 17 + 15 + 8 + 10 + 5 = 55. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 3 November 2026 | 13%16.2 | 9.8 | |
| OpenAPI 3.0.1 in the Prusa-Link-Web repository covering 19 paths and 33 operations, marked 1.0.0-draft, last changed 18 July 2024, with malformed 204 lines and keys containing spaces (20 of 25). No llms.txt or Markdown docs for agents (0). One-line summaries per operation and no guidance on when to use or avoid one (8 of 20). Enums for printer, job, storage, transfer and file types, required fields on response schemas, and ?0 or ?1 header switches; request bodies are binary or empty (11 of 15). Error responses listed per operation with an Error schema of title and text, and few request examples (9 of 15). /api/v1 paths, GET /api/version, and a dated ChangeLog in the Pi repository (12 of 15). 20 + 0 + 8 + 11 + 9 + 12 = 60. | |||
| Agent ergonomicschecked 3 November 2026 | 13%16.2 | 7.8 | |
| Read as an API. Responses are small telemetry and file objects, but a status call returns everything with no field selection (15 of 25). File listings are flat with no paging, filter or size control (5 of 20). Documented 401, 404, 409, 408 and 503 responses with a title and text an agent can read, though 409 does not say which state blocked the call (12 of 20). Pause, resume and upload are PUT, Overwrite guards uploads and Force guards folder deletes, but there is no idempotency key and a repeated POST to start a print depends on the printer's state (10 of 20). Few parameters and sensible defaults, no official SDK in any language (6 of 15). 15 + 5 + 12 + 10 + 6 = 48. | |||
| Security & authchecked 3 November 2026 | 14%17.5 | 6.3 | |
| One credential per printer, a digest username and password shown on a Buddy printer's screen or one API key on the Pi edition, resettable but without scopes or expiry; digest keeps the secret out of the request (12 of 30). No read-only mode and no confirmation before a stop, a delete or a firmware update (2 of 20). The API returns the owner's own file names and telemetry, so little untrusted content (10). No audit log or per-call visibility documented (2 of 15). Prusa's security.txt is valid to 1 June 2027 with a policy page that rewards reports and answers within 5 working days; no bug bounty amounts, SOC 2 or ISO 27001, and the policy covers websites rather than printers by name (10 of 20). 12 + 2 + 10 + 2 + 10 = 36. | |||
| Payments & pricingchecked 3 November 2026 | 10%12.5 | 7.5 | |
| Read with the self-hosted rule. No payment protocol (0). The software is free with nothing to buy, so 20, 20 and 20 on the last three lines. It needs an Original Prusa printer, and the Pi edition a Raspberry Pi, which are hardware the owner already has. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 3 November 2026 | 7%8.8 | 1.5 | |
| The Pi edition's last release is 0.8.1 of 2 July 2024, more than 180 days ago; commits on 14 and 17 October and 2 and 3 November 2026 bump the version to 0.9.0.dev0 and fix the multi-instance image without a release (5 of 30). No release in the last 90 days (0). Of the newest 25 open issues, those from 2025 and 2026 have 0 to 9 comments and none shows a maintainer reply; the forum and help centre answer owners (5 of 25). No official SDK; PrusaSlicer is a client (0 of 15). CI workflow, ruff and dependabot bumps as recent as 2 November 2026 (7 of 10). 5 + 0 + 5 + 0 + 7 = 17. | |||
| Transparency & trusteditorial 44, provenance 83checked 3 November 2026 | 7%8.8 | 5.6 | |
| Source for the Pi edition and the web interface is public, but setup.py declares Freeware with no licence file, the web interface is GPL-3.0 and the spec names AGPLv3, so the licence of the Python edition is unclear (15 of 30). Local software whose data stays on the printer unless registered with Prusa Connect; Prusa's privacy policy of 1 August 2022 gives retention periods per service and names processors and group companies, but says nothing about PrusaLink itself (15 of 30). The ChangeLog flags one breaking change and the website terms promise 30 days' notice for service changes, with no API deprecation policy (6 of 20). Telemetry goes to Prusa Connect only when the owner registers the printer, which the wizard makes optional, and no separate telemetry disclosure was found (8 of 20). 15 + 15 + 6 + 8 = 44. | |||
| Negative events | ≤15 | None recorded | 0 |
| Total | 49.4 · D | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 49.4 D methodology v0.7
Fix list 18 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on PrusaLink. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- unchecked: the PyPI release list for PrusaLink (pypi.org answered the project page with a script challenge, and its JSON endpoint is disallowed by robots.txt). Release dates come from GitHub releases and the ChangeLog
- unchecked: the result of the python-tests.yml workflow on the default branch, and the Buddy firmware's own PrusaLink implementation (prusa3d/Prusa-Firmware-Buddy was not read), including whether an API key still works beside digest on current firmware
- unchecked: the Prusa Connect terms and conditions, which the website terms name as governing PrusaLink and Prusa Connect; their URL was not found on the pages read
- firstReleased is 23 November 2020, the ChangeLog's oldest dated entry (0.1.2). The repository was created on 1 June 2020
- Judgement call on the licence. setup.py declares Freeware and the repository has no licence file, while Prusa-Link-Web is GPL-3.0 and the spec names AGPLv3, so transparency scores the Python edition as unclear rather than open source
- Judgement call on the surface. One listing covers the firmware editions and the Pi edition, since both answer the same /api/v1 spec; the Pi edition's ChangeLog says its API version tracks the one xBuddy reports
- Prusa's website terms forbid automated extraction of website content including scraping, recorded as a fact; the help centre asks for 10 seconds between requests, which was kept
Sources 17
- OpenAPI spec raw.githubusercontent.com · seen 2026-11-03
- Prusa-Link repository, shallow clone (ChangeLog, setup.py, CI, tests) github.com · seen 2026-11-03
- Prusa-Link-Web repository, shallow clone (LICENSE, spec history) github.com · seen 2026-11-03
- Prusa-Link README github.com · seen 2026-11-03
- Prusa-Link releases api.github.com · seen 2026-11-03
- Prusa-Link commits api.github.com · seen 2026-11-03
- Prusa-Link repository metadata api.github.com · seen 2026-11-03
- Prusa-Link open issues github.com · seen 2026-11-03
- Prusa Connect and PrusaLink explained help.prusa3d.com · seen 2026-11-03
- Wi-Fi and Prusa Connect/Link setup guide (PDF of 13 May 2026) help.prusa3d.com · seen 2026-11-03
- about us prusa3d.com · seen 2026-11-03
- website terms prusa3d.com · seen 2026-11-03
- privacy policy prusa3d.com · seen 2026-11-03
- security.txt prusa3d.com · seen 2026-11-03
- security policy prusa3d.com · seen 2026-11-03
- robots.txt help.prusa3d.com · seen 2026-11-03
- RDAP for prusa3d.com rdap.verisign.com · seen 2026-11-03
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. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
Free Free The software is free and ships in the printer firmware or as a free Raspberry Pi image and PyPI package. It needs an Original Prusa printer, and the Pi edition a Raspberry Pi Zero 2 W, Zero W, 3, 4 or 5. Prusa Connect, the cloud service PrusaLink can register with, is free for Prusa owners with 1 GB of storage, per the help centre.
Recent changes
- Latest release
Follow them as a feed at /feeds/tools/prusalink.xml, or this listing's score history at history.json.
Connect
Install
pip install PrusaLinkFirst request
curl --digest -u "$PRUSALINK_USER:$PRUSALINK_PASSWORD" http://<printer-ip>/api/v1/statusThrough letme picks today, calling later
GET https://letme.dev/prusalinkletme picks this listing for cad.print, because it's the top-graded tool for the job.
letme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.
Alternatives to PrusaLink
#4 of 7 in Best CAD, simulation and fabrication APIs for AI agents · All 15 cad comparisons
Machine-readable
Machine-readable
- JSON
/api/v1/tools/prusalink.json· historyhistory.json· badge/badges/prusalink.svg· changes feed/feeds/tools/prusalink.xml - Markdown
/tools/prusalink.md· slim/tools/prusalink.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/prusalink.md·/fixes/prusalink.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool prusalink --md(the CLI) · over MCPget_tool {"slug": "prusalink"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT prusalink.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/prusalink"><img src="https://www.anchorterminal.com/badges/prusalink.svg" alt="PrusaLink on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/prusalink)<a href="https://www.anchorterminal.com/tools/prusalink">PrusaLink on Anchor Terminal</a>It counts on a page on prusa3d.com or one of its subdomains, or the README at the root of github.com/prusa3d/Prusa-Link.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "prusalink", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.
Share this listing
For the vendorGet sharing assets for social media. Two images say PrusaLink is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/prusalink. The logo is the one on this listing. If it's wrong or out of date, send us the right one.