{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-octoeverywhere-for-3d-printing","slug":"octoeverywhere-for-3d-printing","name":"OctoEverywhere For 3D Printing","type":"mcp","url":"https://octoeverywhere.com/mcp","page_url":"https://unfragile.ai/octoeverywhere-for-3d-printing","categories":["mcp-servers"],"tags":[],"pricing":{"model":"unknown","free":false,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-octoeverywhere-for-3d-printing__cap_0","uri":"capability://tool.use.integration.live.printer.state.querying","name":"live-printer-state-querying","description":"Queries real-time 3D printer operational state including job progress, temperature, nozzle position, and print status via token-authenticated HTTP API calls to OctoEverywhere's centralized cloud endpoint. The capability abstracts firmware-specific state representations (OctoPrint, Klipper, Bambu Lab, Elegoo) into a unified JSON response schema, enabling consistent state monitoring across heterogeneous printer hardware without direct network access to individual printers.","intents":["I want to check if my 3D printer is currently printing and what percentage complete the job is","I need to monitor printer temperature, bed temperature, and nozzle position in real-time from an LLM agent","I want to query multiple printers' states simultaneously to build a dashboard of all active print jobs"],"best_for":["developers building LLM-powered 3D printing monitoring agents","teams creating multi-printer management dashboards","makers integrating printer state into home automation workflows"],"limitations":["Read-only capability — cannot modify printer settings or parameters, only observe state","State freshness depends on OctoEverywhere cloud sync latency (not specified in documentation)","Offline or disconnected printers may return stale state or error responses (behavior undefined)","No historical state data or time-series queries — only current snapshot available","Printer firmware differences may result in inconsistent or missing fields across OctoPrint vs Klipper vs Bambu Lab responses"],"requires":["OctoEverywhere account with active printer connection","Private Access Token generated from OctoEverywhere dashboard","Printer running compatible firmware (OctoPrint, Klipper, Bambu Lab, or Elegoo Centauri Carbon)","Network connectivity from MCP client to https://octoeverywhere.com/api/mcp endpoint"],"input_types":["printer_id or printer_name (string identifier for target printer)"],"output_types":["JSON object containing printer state (fields: job_progress, temperatures, nozzle_position, print_status, estimated_time_remaining)"],"categories":["tool-use-integration","iot-monitoring"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-octoeverywhere-for-3d-printing__cap_1","uri":"capability://tool.use.integration.webcam.snapshot.retrieval","name":"webcam-snapshot-retrieval","description":"Captures and returns live webcam snapshots from 3D printers connected to OctoEverywhere via a single API call, with the server handling image encoding, compression, and delivery. The implementation streams image data (format unspecified in documentation) from the printer's attached camera through OctoEverywhere's cloud infrastructure, enabling remote visual monitoring without direct camera access or IP camera configuration.","intents":["I want to get a live photo of my 3D printer to see the current print quality and layer adhesion","I need to include printer camera feeds in an LLM-powered visual inspection agent that analyzes print defects","I want to retrieve snapshots from multiple printers to build a visual dashboard of all active prints"],"best_for":["developers building visual monitoring agents for 3D printing","teams creating multi-printer dashboards with live camera feeds","makers implementing print quality inspection via computer vision"],"limitations":["Image format, resolution, and quality not documented — cannot guarantee compatibility with specific vision models or image processing pipelines","Snapshot refresh rate unknown — may be cached or delayed, unsuitable for real-time video streaming use cases","No image metadata provided (timestamp, camera settings, exposure) — difficult to correlate snapshots with printer state","Requires printer to have compatible webcam attached; behavior undefined if camera is disconnected or unavailable","No image manipulation options (cropping, rotation, filtering) — must be handled client-side"],"requires":["OctoEverywhere account with active printer connection","Private Access Token for authentication","Printer with attached USB or network webcam compatible with OctoPrint/Klipper/Bambu Lab","Network connectivity to https://octoeverywhere.com/api/mcp endpoint"],"input_types":["printer_id or printer_name (string identifier for target printer)"],"output_types":["binary image data (format unknown — likely JPEG or PNG based on web standards)"],"categories":["tool-use-integration","image-visual"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-octoeverywhere-for-3d-printing__cap_10","uri":"capability://tool.use.integration.mcp.server.setup.and.configuration","name":"mcp-server-setup-and-configuration","description":"Provides a streamlined setup process for integrating the OctoEverywhere MCP server into LLM agent frameworks (Claude, other MCP-compatible clients) via a documented endpoint (https://octoeverywhere.com/api/mcp) and token-based authentication. The implementation abstracts MCP protocol details and server configuration, enabling developers to add printer control to agents in under 30 seconds by providing a Private Access Token and printer identifiers.","intents":["I want to quickly add 3D printer monitoring to my Claude agent without complex configuration","I need to integrate OctoEverywhere printer control into my MCP-compatible LLM framework with minimal setup time","I want to configure multiple agents to access the same printer fleet with independent tokens"],"best_for":["developers building LLM agents with printer control capabilities","teams rapidly prototyping printer monitoring agents","makers integrating printer control into existing LLM workflows"],"limitations":["Setup documentation is marketing-focused, not technical — no detailed MCP server configuration guide, tool schema definitions, or error handling documentation provided","MCP transport protocol not specified — unclear if server uses stdio, SSE, HTTP streaming, or other MCP transport mechanism","Configuration options not documented — unknown if server supports environment variables, config files, or other customization","No version information or API stability guarantees — unclear if breaking changes will occur or how deprecation is handled","Error handling and debugging not documented — agents cannot determine root cause of setup failures or connection issues","No local development or testing mode documented — unclear if server can be tested locally before production deployment"],"requires":["OctoEverywhere account with at least one printer connected","Private Access Token generated from OctoEverywhere dashboard","MCP-compatible LLM framework (Claude, other MCP clients)","Network connectivity to https://octoeverywhere.com/api/mcp endpoint"],"input_types":["Private Access Token (string)","MCP server endpoint URL (string)"],"output_types":["MCP tool definitions and resource schemas (implicit in MCP protocol)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-octoeverywhere-for-3d-printing__cap_2","uri":"capability://tool.use.integration.print.job.pause.control","name":"print-job-pause-control","description":"Sends a pause command to an active 3D print job via authenticated API call to OctoEverywhere, which relays the command to the printer's firmware (OctoPrint, Klipper, Bambu Lab, etc.). The implementation handles firmware-specific pause mechanisms (e.g., OctoPrint's pause endpoint vs Klipper's PAUSE gcode macro) transparently, returning confirmation of command receipt without guaranteeing execution state.","intents":["I want to pause a print job remotely if an LLM agent detects a quality issue from a webcam snapshot","I need to pause a printer from an automated workflow when a sensor or external condition triggers","I want to provide pause functionality in a multi-printer management agent without handling firmware-specific commands"],"best_for":["developers building automated print quality monitoring agents","teams creating remote printer control workflows","makers implementing conditional print pause logic based on sensor data or AI analysis"],"limitations":["Mutating operation with no rollback — pause cannot be undone through this API, only resumed via separate resume command (if available)","No confirmation of actual pause state — API returns success if command was sent, not if printer actually paused","Behavior undefined if printer is already paused, offline, or in error state","No timeout or retry logic documented — failed pause commands may require manual intervention","Firmware-specific pause behavior differences not documented (e.g., nozzle retraction, bed cooling, resume behavior)"],"requires":["OctoEverywhere account with active printer connection","Private Access Token for authentication","Active print job in progress on target printer","Printer firmware support for pause command (OctoPrint, Klipper, Bambu Lab all support this)"],"input_types":["printer_id or printer_name (string identifier for target printer)"],"output_types":["JSON confirmation object (fields: success boolean, message string, timestamp)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-octoeverywhere-for-3d-printing__cap_3","uri":"capability://tool.use.integration.print.job.cancellation.control","name":"print-job-cancellation-control","description":"Sends a cancel command to an active 3D print job via authenticated API call to OctoEverywhere, which relays the command to the printer's firmware and typically triggers cleanup operations (nozzle retraction, bed cooling, motor disabling). The implementation handles firmware-specific cancellation workflows transparently, returning confirmation of command receipt without guaranteeing execution or cleanup completion.","intents":["I want to cancel a failed or defective print remotely to prevent wasted filament and time","I need to stop a print job from an LLM agent if quality analysis detects critical defects","I want to provide emergency stop functionality in a multi-printer management system"],"best_for":["developers building automated print quality monitoring and failure detection agents","teams creating remote printer control workflows with failure recovery","makers implementing conditional print cancellation based on AI analysis or sensor data"],"limitations":["Destructive operation with no undo — cancelled prints cannot be resumed, only restarted from beginning","No confirmation of actual cancellation state — API returns success if command was sent, not if printer actually stopped","Cleanup behavior (nozzle retraction, bed cooling, motor disabling) is firmware-specific and not documented","Behavior undefined if printer is already idle, offline, or in error state","No timeout or retry logic documented — failed cancellation commands may leave printer in inconsistent state","No option to specify cleanup behavior (e.g., keep bed heated for material removal vs cool down immediately)"],"requires":["OctoEverywhere account with active printer connection","Private Access Token for authentication","Active print job in progress on target printer","Printer firmware support for cancel command (OctoPrint, Klipper, Bambu Lab all support this)"],"input_types":["printer_id or printer_name (string identifier for target printer)"],"output_types":["JSON confirmation object (fields: success boolean, message string, timestamp)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-octoeverywhere-for-3d-printing__cap_4","uri":"capability://tool.use.integration.multi.printer.state.aggregation","name":"multi-printer-state-aggregation","description":"Enables querying and aggregating state from multiple 3D printers in a single MCP context by supporting printer identification via ID or name parameters. The implementation allows LLM agents to call the state-querying tool multiple times with different printer identifiers, with OctoEverywhere's cloud backend managing per-printer authentication and state retrieval, enabling dashboard-style monitoring without requiring separate API clients or connection management.","intents":["I want to check the status of all my 3D printers at once to see which ones are actively printing","I need to build a unified dashboard showing progress, temperatures, and job details for 5+ printers","I want an LLM agent to monitor a printer farm and alert me if any printer exceeds temperature thresholds"],"best_for":["teams managing multiple 3D printers or printer farms","developers building unified printer monitoring dashboards","makers running production-scale 3D printing operations with multiple machines"],"limitations":["No bulk query endpoint documented — requires separate API call per printer, introducing latency for large fleets (N printers = N API calls)","No aggregation or filtering at server-side — all filtering and correlation must be done client-side by LLM agent","Rate limiting not documented — unknown if rapid multi-printer queries are throttled or cause service degradation","No transaction semantics — state snapshots from different printers may be taken at different times, causing inconsistency in fleet-wide views","Printer discovery mechanism not documented — agents must know printer IDs/names in advance, no enumeration API mentioned"],"requires":["OctoEverywhere account with multiple printers connected","Private Access Token for authentication","Knowledge of all printer IDs or names to query","Network connectivity to https://octoeverywhere.com/api/mcp endpoint"],"input_types":["array of printer_id or printer_name strings"],"output_types":["array of JSON printer state objects (one per printer)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-octoeverywhere-for-3d-printing__cap_5","uri":"capability://tool.use.integration.cross.firmware.printer.abstraction","name":"cross-firmware-printer-abstraction","description":"Provides a unified API abstraction layer that translates MCP tool calls into firmware-specific commands for OctoPrint, Klipper, Bambu Lab, and Elegoo Centauri Carbon printers. The implementation maps common operations (pause, cancel, status query) to each firmware's native API or gcode commands, handling protocol differences (REST vs socket vs proprietary) transparently so LLM agents interact with a single consistent interface regardless of underlying printer hardware.","intents":["I want to control a mixed fleet of OctoPrint, Klipper, and Bambu Lab printers from a single LLM agent without firmware-specific logic","I need to migrate from one printer firmware to another without rewriting my monitoring agent","I want to build a printer control agent that works with any supported printer without knowing its firmware in advance"],"best_for":["developers building firmware-agnostic 3D printer control agents","teams managing heterogeneous printer fleets with mixed firmware","makers building portable printer monitoring solutions"],"limitations":["Firmware-specific features not exposed — advanced OctoPrint plugins, Klipper macros, or Bambu Lab proprietary features cannot be accessed through MCP interface","Behavior differences across firmware not documented — same command may have different side effects (e.g., pause nozzle retraction behavior varies by firmware)","Firmware version compatibility not specified — unknown if older firmware versions are supported or if breaking changes occur","No firmware detection or capability querying — agents cannot determine which firmware a printer runs or what features are available","Error messages and failure modes may differ by firmware — agents cannot reliably distinguish between transient failures and unsupported operations"],"requires":["OctoEverywhere account with printer connected","Printer running one of: OctoPrint, Klipper, Bambu Lab, or Elegoo Centauri Carbon firmware","Private Access Token for authentication","Network connectivity to https://octoeverywhere.com/api/mcp endpoint"],"input_types":["printer_id or printer_name (string identifier)","operation type (pause, cancel, status, snapshot)"],"output_types":["standardized JSON response objects with consistent schema across all firmware types"],"categories":["tool-use-integration","abstraction-layer"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-octoeverywhere-for-3d-printing__cap_6","uri":"capability://tool.use.integration.cloud.relay.remote.access","name":"cloud-relay-remote-access","description":"Enables remote access to 3D printers located behind firewalls, NAT, or non-routable networks by relaying all commands and state queries through OctoEverywhere's cloud infrastructure. The implementation uses token-based authentication to establish a secure tunnel from the MCP client through OctoEverywhere's servers to the printer, eliminating the need for port forwarding, VPN, or direct network access to individual printers.","intents":["I want to monitor and control my 3D printer from anywhere without exposing it to the internet or configuring port forwarding","I need to manage printers in remote locations (offices, makerspaces, customer sites) without direct network access","I want to build a cloud-based printer monitoring service without requiring customers to open firewall ports"],"best_for":["developers building cloud-based 3D printer monitoring services","teams managing printers in multiple locations or behind corporate firewalls","makers running printers in non-routable networks (home networks, isolated labs)"],"limitations":["Introduces cloud dependency — printer control and monitoring require OctoEverywhere service availability; local network outages don't affect access but service outages do","Latency overhead from cloud relay — commands and state queries incur additional round-trip time through OctoEverywhere servers (latency not specified)","No local fallback mechanism documented — if OctoEverywhere is unavailable, direct local access is not supported through MCP","Data passes through OctoEverywhere infrastructure — requires trust in OctoEverywhere's security and privacy practices for sensitive printer data","No bandwidth throttling or optimization documented — large snapshot transfers or frequent queries may incur unexpected cloud bandwidth costs"],"requires":["OctoEverywhere account with printer connected and registered","Private Access Token for authentication","Printer with network connectivity (WiFi or Ethernet) to reach OctoEverywhere cloud","Network connectivity from MCP client to https://octoeverywhere.com/api/mcp endpoint"],"input_types":["printer_id or printer_name (string identifier)","operation type and parameters"],"output_types":["JSON responses from printer operations"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-octoeverywhere-for-3d-printing__cap_7","uri":"capability://tool.use.integration.token.based.authentication.and.authorization","name":"token-based-authentication-and-authorization","description":"Implements token-based authentication for all MCP tool calls using Private Access Tokens generated from the OctoEverywhere dashboard. The implementation uses the token as an API key or Authorization header value to authenticate requests to the https://octoeverywhere.com/api/mcp endpoint, with OctoEverywhere's backend validating token validity and associating requests with the authenticated user's printer fleet.","intents":["I want to securely authenticate my LLM agent to OctoEverywhere without embedding username/password credentials","I need to generate API tokens for different agents or applications with independent lifecycle management","I want to revoke access for a specific agent or integration without changing my account password"],"best_for":["developers building LLM agents that need secure printer access","teams managing multiple integrations with independent authentication lifecycles","makers implementing printer control in production environments"],"limitations":["Single token type — no documented role-based access control (RBAC) or per-printer permission scoping; all tokens have equal access to all printers","No token expiration or rotation mechanism documented — unclear if tokens are long-lived or require periodic renewal","No token revocation audit trail documented — cannot determine when or why a token was revoked","Token generation mechanism not documented — unclear if tokens are generated via API, dashboard UI, or other means","No multi-factor authentication (MFA) support documented — token compromise could grant full printer access without additional verification","No rate limiting per token documented — unknown if compromised tokens can be used for brute-force or DoS attacks"],"requires":["OctoEverywhere account with at least one printer connected","Access to OctoEverywhere dashboard to generate Private Access Token","Token must be provided to MCP client via configuration or environment variable"],"input_types":["Private Access Token (string)"],"output_types":["authentication confirmation (implicit in successful API responses)"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-octoeverywhere-for-3d-printing__cap_8","uri":"capability://tool.use.integration.spoolman.integration.for.filament.tracking","name":"spoolman-integration-for-filament-tracking","description":"Integrates with Spoolman (a filament inventory management system) through OctoEverywhere to track filament usage, spool inventory, and material properties across connected printers. The implementation allows MCP tools to query filament data associated with active print jobs, enabling LLM agents to monitor material consumption and alert when spools are running low or incompatible materials are loaded.","intents":["I want to track filament usage across multiple printers to optimize inventory and reduce waste","I need to alert my LLM agent when a spool is running low so it can pause or cancel prints before filament runs out","I want to query material properties (color, type, temperature) for active print jobs to validate print settings"],"best_for":["developers building filament inventory management agents","teams running production 3D printing operations with multiple materials","makers optimizing filament usage and reducing material waste"],"limitations":["Requires separate Spoolman installation and configuration — OctoEverywhere does not provide Spoolman hosting, only integration","Filament tracking accuracy depends on Spoolman calibration and printer firmware reporting — weight-based tracking may have measurement errors","No automatic filament detection — agents cannot detect if wrong spool is loaded without manual Spoolman entry","Integration mechanism not documented — unclear if Spoolman data is queried on-demand or synced periodically to OctoEverywhere","No filament consumption prediction — agents cannot estimate time until filament runs out without implementing their own calculation logic","Spoolman API compatibility not documented — unknown which Spoolman versions are supported or if breaking changes occur"],"requires":["OctoEverywhere account with printer connected","Spoolman instance installed and configured (separate from OctoEverywhere)","Printer firmware support for filament tracking (OctoPrint with Spoolman plugin, Klipper with Spoolman integration, etc.)","Private Access Token for OctoEverywhere authentication"],"input_types":["printer_id or printer_name (string identifier)"],"output_types":["JSON object containing filament data (fields: spool_id, material_type, color, weight_remaining, estimated_usage_rate)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-octoeverywhere-for-3d-printing__cap_9","uri":"capability://tool.use.integration.octofarm.multi.printer.dashboard.integration","name":"octofarm-multi-printer-dashboard-integration","description":"Integrates with OctoFarm (a multi-printer management dashboard) through OctoEverywhere to provide centralized monitoring and control of printer fleets. The implementation allows MCP tools to leverage OctoFarm's aggregation, grouping, and visualization capabilities, enabling LLM agents to query fleet-wide metrics, group printers by location or type, and access OctoFarm's custom monitoring rules and alerts.","intents":["I want to query printer fleet metrics (total active prints, average utilization, failure rate) from OctoFarm through an LLM agent","I need to group printers by location or type and query status for each group independently","I want to leverage OctoFarm's custom monitoring rules and alerts in my LLM agent workflows"],"best_for":["developers building fleet-wide printer monitoring agents","teams managing large printer farms with OctoFarm dashboards","makers implementing custom monitoring logic on top of OctoFarm data"],"limitations":["Requires separate OctoFarm installation and configuration — OctoEverywhere does not provide OctoFarm hosting, only integration","OctoFarm data freshness depends on OctoFarm's sync interval — state may be delayed compared to direct printer queries","Integration mechanism not documented — unclear if OctoFarm data is queried on-demand or cached by OctoEverywhere","Custom OctoFarm rules and alerts not exposed through MCP — agents cannot query or trigger OctoFarm-specific monitoring logic","OctoFarm API compatibility not documented — unknown which OctoFarm versions are supported or if breaking changes occur","No OctoFarm-specific error handling documented — agents cannot distinguish between OctoFarm unavailability and printer unavailability"],"requires":["OctoEverywhere account with printer connected","OctoFarm instance installed and configured (separate from OctoEverywhere)","OctoFarm connected to same printers as OctoEverywhere account","Private Access Token for OctoEverywhere authentication"],"input_types":["printer_group_id or location_name (string identifier for grouped printers)"],"output_types":["JSON object containing aggregated fleet metrics (fields: total_printers, active_prints, average_utilization, failure_count)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":32,"verified":false,"data_access_risk":"high","permissions":["OctoEverywhere account with active printer connection","Private Access Token generated from OctoEverywhere dashboard","Printer running compatible firmware (OctoPrint, Klipper, Bambu Lab, or Elegoo Centauri Carbon)","Network connectivity from MCP client to https://octoeverywhere.com/api/mcp endpoint","Private Access Token for authentication","Printer with attached USB or network webcam compatible with OctoPrint/Klipper/Bambu Lab","Network connectivity to https://octoeverywhere.com/api/mcp endpoint","OctoEverywhere account with at least one printer connected","MCP-compatible LLM framework (Claude, other MCP clients)","Active print job in progress on target printer"],"failure_modes":["Read-only capability — cannot modify printer settings or parameters, only observe state","State freshness depends on OctoEverywhere cloud sync latency (not specified in documentation)","Offline or disconnected printers may return stale state or error responses (behavior undefined)","No historical state data or time-series queries — only current snapshot available","Printer firmware differences may result in inconsistent or missing fields across OctoPrint vs Klipper vs Bambu Lab responses","Image format, resolution, and quality not documented — cannot guarantee compatibility with specific vision models or image processing pipelines","Snapshot refresh rate unknown — may be cached or delayed, unsuitable for real-time video streaming use cases","No image metadata provided (timestamp, camera settings, exposure) — difficult to correlate snapshots with printer state","Requires printer to have compatible webcam attached; behavior undefined if camera is disconnected or unavailable","No image manipulation options (cropping, rotation, filtering) — must be handled client-side","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.47,"ecosystem":0.25,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:03.579Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=octoeverywhere-for-3d-printing","compare_url":"https://unfragile.ai/compare?artifact=octoeverywhere-for-3d-printing"}},"signature":"1vXP+hbj01ESlVMFh+ktQbgmqaWdVcgIxxDrHDGcm1wrDzS8snvuVdNsuczfbsVdwTKT3Y/vfYgRNVhioRLXBA==","signedAt":"2026-06-22T23:26:45.307Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/octoeverywhere-for-3d-printing","artifact":"https://unfragile.ai/octoeverywhere-for-3d-printing","verify":"https://unfragile.ai/api/v1/verify?slug=octoeverywhere-for-3d-printing","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}