Trust
Agent Docs

Effective-license lineage: walks base-model chains and flags suspected license laundering.

Alias of /api/v1/artifacts/{id}/license-lineage (recorded; identical handler). Prefer the recorded path: this one already answers with Deprecation and Sunset headers.

Inputs. Path, query and header fields are listed below. No request body is required.

Outputs. See each status below for its media type, schema and headers. A missing record or unavailable capability is not a successful empty result.

Errors. API JSON failures use the documented response schema. Read code, message and next; retry only when the response allows it. Auth, invalid input and missing records need a caller change.

Rate limits. Public read budgets apply by client IP and route group. This operation can have a smaller route-specific budget. Read Retry-After on 429 or retryable 503 responses.

Example setup. Use an identifier returned by the matching list, search or create operation. Sample identifiers are not a promise that a record exists.

get/api/artifacts/{id}/license-lineage

Request

  • Base URL: https://huggingbay.xyz
  • URL: https://huggingbay.xyz/api/artifacts/{id}/license-lineage
  • Auth: none declared

Path parameters

idstring required

Response

Lineage chain with effectiveCommercialUse and launderingSuspected

object required

Lineage chain with effectiveCommercialUse and launderingSuspected. Fields can vary; no stronger field guarantee is specified for this operation.

Changes

No recorded changes to this operation across all 2 revisions of this API.