Skip to content
REFERENCE
← All reference documents
v0.1Contract specification published

TERMS ENFORCEMENT API

The programmatic interface through which AI platforms query the framework’s declared rights positions in real time. Distinct from the Registry’s lookup API: resolves what a platform may do with a given asset.

Document: CIP Terms Enforcement API — What Platforms Query AgainstVersion: v0.1Status: Contract specification published — deployment downstream of Registry
§1

Five operational determinations

Ingestion permission (maps to GIPL Layer 1). Output-derivative permission (maps to GIPL Layer 2 and NILP Downstream Obligation). Identity-engagement permission (NILP-specific). Distribution permission (algorithmic amplification, recommendation-engine inclusion). Audit-readiness verification (Platform Certification support).

§2

Endpoint contract

Base URL: https://api.creativeip.org/terms/v1/. POST /check (single asset). POST /batch-check (up to 1,000 per batch). POST /audit (platform audit). GET /health. The /v1/ path committed for v3.x lifetime.

§3

Authentication and rate limiting

Three key tiers: certified-platform (highest rate limits, audit access), development (90-day expiry), research (academic use). Per-key sliding-window rate limits. Bulk-check supports millions of queries per day.

§4

What the API does not do

Not enforcement (expresses operational determinations, does not block actions). Not takedowns (framework position: takedowns belong in human-mediated workflows). Not content delivery (platforms acquire content through normal routes).

Citation

CIP Terms Enforcement API v0.1, https://creativeip.org/terms-enforcement-api