Authentication¶
CutWeaver uses a single header: X-API-Key.
Tiers¶
| Tier | Daily quota | How to get it |
|---|---|---|
| Anonymous playground | 5 solves / day / IP | nothing — just call the endpoint |
| Evaluation key | 25 solves / day, 250 / month | manual request for now via cutweaver.io/#pricing |
| Starter | 3 000 solves / month | plan request on cutweaver.io/#pricing, first live integration |
| Pro | 15 000 solves / month | plan request, deeper optimization for waste-sensitive jobs |
| Scale | 75 000 solves / month | plan request, team keys and usage visibility |
The free tiers are intentionally sized for evaluation, smoke tests, and hobby use. If a real business depends on the endpoint every day, start at Starter.
Checkout and automatic key issuance are part of the next monetization step. Today evaluation and paid hosted keys are provisioned through the request flow.
Sending the key¶
bash
curl -X POST https://api.cutweaver.io/v1/solve \
-H "X-API-Key: cnw_pro_xxxxxxxxxxxxxxxxxxxxxxxx" \
-H "Content-Type: application/json" \
-d '{ ... }'
Checking your usage¶
bash
curl https://api.cutweaver.io/v1/usage \
-H "X-API-Key: cnw_pro_xxxxxxxxxxxxxxxxxxxxxxxx"
json
{
"ok": true,
"key": "cnw_pro_xxxxxxxxxxxxxxxxxxxxxxxx",
"plan": "pro",
"period": "2026-04",
"usage": { "solves": 1247, "limit": 15000 }
}
Self-hosted Docker
Self-hosted instances do not use X-API-Key. They validate an
Ed25519-signed license file at startup. See Self-hosted Docker.