Resolve an upstream repo URL, owner/name, or artifact id to one Hugging Bay record.

Alias of /api/v1/resolve (recorded; identical handler). Prefer the recorded path: this one already answers with Deprecation and Sunset headers. Use this when a human or agent pasted a Hugging Face, ModelScope, GitHub, Zenodo, or arXiv URL. The response includes a normalized repo, exact artifact match when present, hosted download rows when ready, fallback search rows, and safe next actions.

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.