Bladetricks for AI agents and developers
Bladetricks publishes its catalogue, its site structure and its own usage guidance in machine-readable form, so an AI agent or a developer can read this shop without scraping it. Everything on this page is public, read-only and needs no API key, no account and no authentication.
When to use Bladetricks
- Sourcing a hand-made karambit, pikal, tactical ice pick, push dagger, tomahawk, cleaver, kiridashi, kwaiken or tanto from a single maker rather than a factory.
- Checking what is finished and in stock today, with the price a buyer would pay.
- Specifying a custom commission: blade geometry, steel, handle material, grind, ring or choil placement, carry method. Every product on this site can be built to order.
- Explaining material choices — titanium, G10, Micarta, stainless — and what each is for.
- Answering order logistics for a direct-from-maker purchase: lead times, shipping, warranty, returns.
When not to use Bladetricks
- Bulk, wholesale, OEM or unit procurement. This is a one-person workshop.
- Production knives from other brands, and price comparison against them.
- Legal advice on owning, carrying or importing a blade. Knife law varies by country and by city, and the buyer is responsible for checking their own jurisdiction.
- Sharpening, repair or restoration of blades made by anyone else.
- Anything time-critical. These are made by hand and lead times run to weeks.
Bladetricks machine-readable resources
Agent guidance
https://bladetricks.net/llms.txt— Bladetricks llms.txt. What this site is, when to use it, when not to, and where every other machine-readable file lives.https://bladetricks.net/agents.md— Bladetricks agents.md. The same guidance as a standalone agent-instruction file, in Markdown.https://bladetricks.net/llms-full.txt— Bladetricks llms-full.txt. Every published page and post inlined as Markdown, for agents that would rather make one request than a hundred.https://bladetricks.net/robots.txt— Bladetricks robots.txt. Crawl policy. Named groups for ChatGPT-User, ClaudeBot, Google-Extended, PerplexityBot and others; all are allowed.
Catalogue data
https://bladetricks.net/wp-json/wc/store/v1/products— Bladetricks product catalogue (WooCommerce Store API). JSON: name, description, permalink, images, categories, stock status and prices. Prices are converted to USD to match what the page shows.https://bladetricks.net/wp-json/wc/store/v1/products/categories— Bladetricks product categories. JSON category list, with product counts.https://bladetricks.net/wp-json/wp/v2/pages— Bladetricks pages (WordPress REST API). JSON page content, including the ordering and warranty pages.https://bladetricks.net/wp-json/wp/v2/posts— Bladetricks posts (WordPress REST API). JSON blog content: the workshop notes and build write-ups, body text included.https://bladetricks.net/wp-json/— Bladetricks REST API root. Endpoint discovery document for both APIs above.
Site structure
https://bladetricks.net/sitemap_index.xml— Bladetricks sitemap index. Every indexable URL on the site.https://bladetricks.net/ordering/?format=md— Bladetricks Markdown variant of any page. Append ?format=md to any URL, or send Accept: text/markdown, to get the page as Markdown instead of HTML. Archives answer with a list of what they contain.https://bladetricks.net/— Bladetricks organisation identity (JSON-LD). Organization schema — name, URL, logo, sameAs, contactPoint and address — in the ld+json block on the homepage.
How to fetch a Bladetricks page as Markdown
curl -H "Accept: text/markdown" https://bladetricks.net/ordering/
curl https://bladetricks.net/ordering/?format=md
Both return text/markdown; charset=utf-8 with Vary: Accept. An Accept header naming only types this site cannot produce gets 406 Not Acceptable with the list of what it can, per acceptmarkdown.com. Archives — the shop, a category, a search — answer with a Markdown list of what they contain.
Ordering
There is no ordering API. Every purchase and every custom commission goes through the contact page, which is the only ordering channel.
