makesPDF
← All updates

Artifact downloads are rate-limited at 500/hour

GET /api/v1/artifacts/:id/:kind now allows 500 downloads per hour — per caller for session and API-key callers, per IP for a signed ?token= link or an x402 poll token. Forged or expired links fail instantly and never touch the artifact store.

apilimitssecurity

GET /api/v1/artifacts/:id/:kind — the download route behind X-Artifact-Id, the render history, and every downloadUrl an MCP render tool hands back — now accepts 500 downloads per hour. Session and API-key callers are counted per caller, so their own downloads never use up the per-IP budget they share with anyone else — though if that IP's budget is already used up, every request from it gets a 429 until it recovers. A signed ?token= link, and an x402 pollToken download (which resolves no caller), are counted per client IP.

The number matches the two siblings that already had one: the get_render_download_url MCP tool that mints fresh links, and GET /api/v1/assets/:id/raw. Downloading your own renders is not a high-volume operation, and a limit is what keeps a flood of made-up artifact ids from turning into database work. A download over the limit returns 429 with a Retry-After header, and — like every unauthorised response on the route — it says nothing about whether the artifact exists.

Signed download links also got cheaper to reject: a link is now checked against the artifact id and kind in the URL before anything is looked up, so a tampered, expired or mismatched link is an instant 404 instead of a database read. Valid links behave exactly as before — same 15 minutes, same one-artifact scope, same Referrer-Policy: no-referrer.

No change is needed on your side unless you script more than 500 downloads an hour from one identity; if you do, tell us what you are building.