Curriculum

Rights checks

Before you use an asset · 5 lessons over published documents · Machine form: /v1/curriculum/rights-checks · Markdown

Checking a third-party asset before use: ask whether a license permits the exact use, read the Rights Receipt standard a cleared answer is issued under, the security specification behind the pre-call check, the pre-call check itself, and the error catalog every refusal resolves against.

Lessons

• Can I use this asset? — The ask flow: a plain question about an asset and an intended use, answered from the license record. Study: /can-i-use
• The Rights Receipt standard — What a Rights Receipt is: the signed, offline-verifiable record that an asset was cleared for an exact use. Study: /standards/rights-receipt
• The security specification — The spec behind the pre-call check: integrity, scanning and standing flags, in the open. Study: /security/spec
• The pre-call check — Before calling an outside tool: probe it first and read the integrity, scan and flag signals the answer carries. Study: /security · Run: GET /v1/security/precall
• When a call fails: the error catalog — Every error code carries its typical status, whether retrying can help, and what to do next. Study: /v1/errors · Run: GET /v1/errors