printbench.xyz valid
print-bench
Co-designed, parametric 3D-printable designs in OpenSCAD — plus the
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://www.printbench.xyz/llms.txt
- llms-full.txt
- https://www.printbench.xyz/llms-full.txt
- Sections
- 5
- Links
- 62
- Size
- 24298 bytes
- Registered
- 2026-08-30
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T04:53:36.063Z
- Last checked
- 2026-10-25T04:53:37.086Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T04:53:36.076Z. Cached copy · Source on printbench.xyz
# print-bench
> Co-designed, parametric 3D-printable designs in OpenSCAD — plus the
> platform that gates them: render/printability/slice CI, drift-checked
> docs, and a human-gated autonomy loop. Every page on this site is
> generated from a committed markdown source; this file indexes where
> each source is served.
## Contributing (the platform)
- [Contributing to the print-bench platform](/docs/contributing/README.md): The contributor guide for the system underneath the designs — the scripts, gates, CI, shared libraries, tools, product site, and autonomy routines.
- [The autonomy loop](/docs/contributing/autonomy.md): The scheduled agent routines that keep the backlog moving without a human driving each step — what each one does, and the safety architecture that makes an unattended agent with a repo secret an acceptable thing to run.
- [CI and the gates](/docs/contributing/ci-and-gates.md): How CI decides what to run for your PR, what each gate proves, and the one behavior that surprises newcomers most: CI pushes commits onto your branch.
- [Conventions](/docs/contributing/conventions.md): The standing rules platform code is held to — each one enforced by a check, each check born from a real failure.
- [Extending the platform](/docs/contributing/extending.md): Recipes for each kind of platform change, each step tied to the check that enforces it where one exists.
- [Getting started](/docs/contributing/getting-started.md): How to stand up the toolchain, understand the environment contract every script assumes, and get your first green check run — the on-ramp for platform contributions.
- [Pull requests](/docs/contributing/pull-requests.md): The lifecycle of a PR here — what CI will do to your branch, who reviews what, and where the process differs from an ordinary repo.
## Architecture
- [Architecture](/docs/architecture/README.md): Two layers, kept apart on purpose.
- [CI & automation platform](/docs/architecture/ci-platform.md): The domain-agnostic half of print-bench: how any repository built this way selects its gates, keeps derived files honest, and runs unattended agents.
- [Design workflow](/docs/architecture/design-workflow.md): The domain half: what print-bench actually builds, and the gates that decide a design is done.
## Designs (product pages)
- [aerochord](/designs/aerochord/README.md): A musical wind instrument that (a) prints in place as **one piece** with no supports, (b) does not correspond to any instrument in the historical record, and (c) is only really designable/printable with an FDM machine and a computed internal geometry. The brief was an explicit stress test of the whole co-design pipeline.
- [Alcove rod socket](/designs/alcove-rod-socket/README.md): A parametric, two-part **screw-together end socket** for a 40 mm round curtain/closet rod spanning a recess or alcove, used in pairs: a wall boss screwed flat to each facing wall, the rod's ends plugging into knurled collars that hand-thread onto the bosses. Removi
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| bernstein.run | Bernstein | interface AI and machine learning AI agents and MCP +2 | — | 46 | ✓ | ✓ | |
| continual.ai | Continual | documentation AI and machine learning AI agents and MCP +1 | US | 52 | ✓ | ||
| agentskit.io | Agents Playbook | documentation AI agents and MCP Developer tools | — | 45 | ✓ | ✓ | |
| xano.com | Xano | interface AI agents and MCP Infrastructure +1 | US | 56 | ✓ | ||
| overhand.dev | Overhand | documentation Developer tools AI agents and MCP | — | 45 | ✓ | ✓ | |
| docuwriter.ai | DocuWriter.ai | interface AI and machine learning Developer tools +1 | — | 57 | ✓ | ✓ | |
| swapp.ai | SWAPP | documentation AI and machine learning Construction and architecture | US | 53 | ✓ | ||
| harness.io | Harness | interface Infrastructure DevOps and observability +1 | US | 58 | ✓ |
Machine-readable: GET /v1/resolve?q=printbench.xyz · GET /v1/domain/printbench.xyz · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage printbench.xyz, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for printbench.xyz:
1. POST https://agentwebmap.com/v1/sites/printbench.xyz/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://printbench.xyz/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/printbench.xyz/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/printbench.xyz).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.