> ## Documentation Index > Fetch the complete documentation index at: https://docs.agentsfleet.net/llms.txt > Use this file to discover all available pages before exploring further. # Onboard a tenant Fleet library entry > Onboards a Fleet library entry into the caller's workspace catalog from a GitHub source reference. Requires the `library:write` scope plus ownership of the target workspace. Re-onboarding identical bytes converges on one `(workspace_id, content_hash)` row. The response carries metadata only. ## OpenAPI ````yaml https://raw.githubusercontent.com/agentsfleet/agentsfleet/main/public/openapi.json post /v1/workspaces/{workspace_id}/fleet-libraries openapi: 3.1.0 info: title: agentsfleet Control Plane API version: 1.0.0 description: API for managing workspaces, fleets, triggers, and runs. contact: name: agentsfleet url: https://agentsfleet.net servers: - url: https://api.agentsfleet.net description: Production security: - BearerAuth: [] tags: - name: Health description: System status and readiness probes x-mintlify: navigation: Health - name: Authentication description: Command Line Interface (CLI) sign-in sessions and GitHub sign-in x-mintlify: navigation: Authentication - name: Workspaces description: Create and manage workspaces x-mintlify: navigation: Workspaces - name: Tenant description: Manage tenant provider settings and models x-mintlify: navigation: Tenant - name: auth-identity-events description: >- Process signed account events from Clerk. This route is not for customer fleets. x-mintlify: navigation: Auth Identity Events - name: Fleets description: Create, configure, and run fleets x-mintlify: navigation: Fleets - name: Schedules description: Manage and receive scheduled Fleet events x-mintlify: navigation: Schedules - name: Memory description: Read and search saved fleet memory x-mintlify: navigation: Memory - name: Secrets description: Manage named secrets for fleets in a workspace x-mintlify: navigation: Secrets - name: Admin description: Manage shared provider keys and models x-mintlify: navigation: Admin - name: Billing description: Read tenant balances and charge records x-mintlify: navigation: Billing - name: Integration Grants description: Manage fleet access to third-party services x-mintlify: navigation: Integration Grants - name: Connectors description: Connect workspaces to third-party providers x-mintlify: navigation: Connectors - name: Fleet Keys description: Manage keys that let external clients call a fleet x-mintlify: navigation: Fleet Keys - name: API Keys description: Manage tenant admin API keys x-mintlify: navigation: API Keys - name: Webhooks description: Receive signed events and approval decisions x-mintlify: navigation: Webhooks - name: Approvals description: List, inspect, and resolve pending approvals x-mintlify: navigation: Approvals - name: Fleet description: Enroll and manage runners x-mintlify: navigation: Fleet - name: Fleet Bundles description: Manage fleet source bundles in a workspace x-mintlify: navigation: Fleet Bundles - name: Fleet library description: Browse and add reusable fleet sources x-mintlify: navigation: Fleet library - name: Model Library description: List models available to the tenant x-mintlify: navigation: Model Library paths: /v1/workspaces/{workspace_id}/fleet-libraries: post: tags: - Fleet library summary: Onboard a tenant Fleet library entry description: >- Onboards a Fleet library entry into the caller's workspace catalog from a GitHub source reference. Requires the `library:write` scope plus ownership of the target workspace. Re-onboarding identical bytes converges on one `(workspace_id, content_hash)` row. The response carries metadata only. operationId: onboard_tenant_fleet_library parameters: - name: workspace_id in: path required: true description: UUIDv7 of the workspace. schema: type: string format: uuid requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/FleetLibraryOnboardRequest' responses: '201': description: Entry onboarded into the workspace catalog. content: application/json: schema: $ref: '#/components/schemas/FleetLibraryOnboardResult' '400': $ref: '#/components/responses/Error' '401': $ref: '#/components/responses/Error' '403': $ref: '#/components/responses/Error' '413': $ref: '#/components/responses/Error' '502': $ref: '#/components/responses/Error' '503': $ref: '#/components/responses/Error' default: $ref: '#/components/responses/Error' components: schemas: FleetLibraryOnboardRequest: type: object required: - source_kind properties: source_kind: type: string description: >- Where the entry comes from. `github` and `template` are fetched and validated server-side; `upload` carries the SKILL.md (and optional TRIGGER.md) Markdown inline for a skill-only entry. enum: - template - upload - github replace: type: boolean default: false description: >- Platform tier only. The catalog id comes from the bundle's SKILL.md frontmatter name, not this repository path. So a bundle may declare a name another repository already owns. That is refused with `UZ-CATALOG-004`, rather than silently swapping the bundle every workspace installs. Retry with `replace: true` to overwrite it deliberately. source_ref: type: string maxLength: 512 description: >- Required for `github` (an `owner/repo` locator) and `template` (a first-party template id). ref: type: string maxLength: 100 description: >- Optional branch or tag for `github` sources; absent fetches the default branch. The dashboard's Fetch-update sends the entry's stored ref, so a ref pinned via the catalog PATCH is honored by the refetch rather than silently reset. Same character rules as a repository segment. skill_markdown: type: string maxLength: 204800 description: >- Raw SKILL.md bytes. Required for `upload`; ignored for fetched sources. trigger_markdown: type: string maxLength: 204800 description: >- Optional raw TRIGGER.md bytes for `upload`. Ignored for fetched sources. FleetLibraryOnboardResult: type: object description: >- Result of onboarding a Fleet library entry (platform or tenant tier). Carries the entry identity, its tier in `visibility`, the content hash, and the derived requirements — never a support-file manifest, an object-store key, or support-file content. required: - id - name - visibility - content_hash - requirements properties: id: type: string description: >- Entry id — the slug for platform entries, a UUIDv7 for tenant entries. name: type: string visibility: type: string description: The catalog tier the entry was onboarded into. enum: - platform - tenant content_hash: type: string description: SHA-256 content hash of the onboarded snapshot. requirements: $ref: '#/components/schemas/FleetBundleRequirements' FleetBundleRequirements: type: object required: - credentials - tools - network_hosts - trigger_present properties: credentials: type: array items: type: string tools: type: array items: type: string network_hosts: type: array items: type: string trigger_present: type: boolean ErrorBody: type: object description: RFC 7807 problem detail error response (application/problem+json) required: - docs_uri - title - detail - error_code - request_id properties: docs_uri: type: string format: uri description: Stable link to documentation for this error code example: https://docs.agentsfleet.net/api-reference/error-codes#UZ-AGT-009 title: type: string description: Short human-readable label, same for every occurrence of this code example: Fleet not found detail: type: string description: Instance-specific context describing what went wrong example: No fleet with id 'abc123' in this workspace. error_code: type: string description: Machine-readable error code example: UZ-AGT-009 request_id: type: string description: Correlation ID for this request current_state: type: string description: >- Resource state that blocked the requested change. Present only on 409 responses. example: paused user_message: type: string description: > Plain message safe to show to a user. Present only when an error defines one. Use `detail` or `title` when this field is absent. example: >- We couldn't find that Fleet. It may have been deleted, or the ID doesn't match one in this workspace. etag: type: string description: >- Resource version returned on 412 responses so the caller can refetch and retry. responses: Error: description: RFC 7807 problem detail error response content: application/problem+json: schema: $ref: '#/components/schemas/ErrorBody' securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- Obtain a token via the CLI auth flow (POST /v1/auth/sessions) or GitHub OAuth ````