medusa-api-routes skillA
medusa-api-routes is agent-read markdown (skill) from orcaqubits/agentic-commerce-skills-plugins: Create custom Medusa v2 API routes — file-based routing, HTTP method exports, middleware configuration, Zod validators, authentication middleware, and additional-data pattern. Use when adding REST endpoints..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Medusa v2 Custom API Routes ## Before writing code **Fetch live docs**: 1. Fetch `https://docs.medusajs.com/learn/fundamentals/api-routes` for API route overview 2. Web-search `site:docs.medusajs.com custom API route file convention` for file-based routing 3. Web-search `site:docs.medusajs.com API route middleware` for middleware configuration 4. Web-search `site:docs.medusajs.com API route validation zod` for request validation 5. Web-search `site:docs.medusajs.com additional data API routes` for the additional-data pattern ## File-Based Routing Medusa v2 uses a file-system router under `src/api/`: | File Path | Resulting Endpoint | |-----------|-------------------| | `src/api/store/custom/route.ts` | `GET/POST /store/custom` | | `src/api/admin/custom/route.ts` | `GET/POST /admin/custom` | | `src/api/store/custom/[id]/route.ts` | `GET/POST /store/custom/:id` | | `src/api/custom/route.ts` | `GET/POST /custom` (no auth prefix) | ### Conventions - File must be named `route.ts` (not `index.ts`) - Dynamic parameters use `[param]` folder syntax - The `store/` prefix applies storefront authentication scope - The `admin/` prefix applies admin authentication scope …
Read the whole file at its exact version.
How to install
mdr add orcaqubits/agentic-commerce-skills-plugins/medusa-api-routes@git:20260326.769051fmdr add orcaqubits/agentic-commerce-skills-plugins/medusa-api-routes@sha256:8c6e4f4f2aa75a36Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_wskd3viuhvicg6vy)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6148 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
orcaqubits/agentic-commerce-skills-plugins · 39 stars · license MIT · pushed 2026-09-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wskd3viuhvicg6vy GET https://markdownregistry.com/api/v1/resolve?ref=orcaqubits/agentic-commerce-skills-plugins/medusa-api-routes GET https://markdownregistry.com/api/v1/blob/8c6e4f4f2aa75a36ab6f8a5e77c29a1c8f8bf31718432f08d52a77cadf90d66e
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.