Licences, links and delivery
How a licence is issued, what it grants, and how the signed download link behaves.
Issue a licence
POST /api/bank/license
{"asset_id": "a_...", "license_type": "standard", "buyer": "[email protected]"}
-> {"license": {"id": "lic_...", "license_type": "standard", "price_usd": 9.0},
"download_url": "/api/bank/download/lic_....<expiry>.<signature>",
"expires_in_seconds": 86400,
"asset": { ... }}The two licences
| Licence | Grants |
|---|---|
| Standard | Worldwide, perpetual, non-exclusive use in digital and print media, advertising, presentations and packaging, up to 500,000 impressions or copies. No resale of the file itself, no use in a competing asset library, no trademark registration. |
| Extended | Everything above with no impression limit, plus items for resale. |
The download link
The link carries the licence id, an expiry and a signature over both, so it proves itself without a lookup. It is checked for a valid signature, an expiry in the future, and an asset still on sale — an asset pulled from the catalogue stops being downloadable even on a link issued earlier. Redemptions are counted: generous enough for a download that fails halfway, finite enough that a link pasted in public is not a free copy.
The licence is perpetual. Only the link expires. Keep the file.
Paying
A catalogue can be run with free licensing, in which case no payment reference is needed. Otherwise settlement happens through the x402 rail on the MCP endpoint, which verifies and settles before the licence is issued. A payment reference that nothing can verify is refused rather than recorded as a sale.