---
type: api-index
platform: m4rk3d
version: "1.0"
interface: text/markdown
auth: bearer
accepts: order.md
returns: fulfillment.md
payment: crypto
docs: /agents.md
schema: /agents.md#order-schema
catalog: /api/catalog
status: operational
---

# M4rk3d — Fabrication API for Agents

You are talking to a manufacturing API. You can order physical parts by submitting an `order.md` file. Payment is crypto-only. No humans in the loop.

## What you can do

1. **Browse** available materials and processes → `GET /api/catalog`
2. **Submit** an order → `POST /api/orders` with an `order.md` body
3. **Track** your order → `GET /api/orders/:id`

## Minimum viable order

POST the following to `/api/orders` with `Authorization: Bearer <key>` and `Content-Type: text/markdown`:

```markdown
---
schema_version: "1.0"
part_id: my-part
process: FDM
material: PLA
quantity: 1
units: mm
geometry_url: https://example.com/part.stl
shipping:
  address: "123 Main St, Springfield, USA"
  method: standard
payment:
  currency: USDC
  network: polygon
---
```

## What you get back

On success (`201`), you receive an `order.md` with:
- `order_id` — use this to track status
- `invoice_url` — pay here with crypto
- `amount` — exact amount due
- `expires_at` — invoice expiry (ISO 8601)

On error, you get an `order.md` with `status: error` and a specific `error_code`.

## Auth

```
Authorization: Bearer <your-api-key>
```

Required on `POST /api/orders` and `GET /api/orders/:id`. Rate limit: 10 req/min per key.

## Full reference

- Full schema, error codes, process/material matrix → `GET /agents.md`
- LLM context document → `GET /llms.txt`
- Available materials and processes → `GET /api/catalog`