> ## Documentation Index > Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt > Use this file to discover all available pages before exploring further. # Change the projects a registry robot reaches > Change which projects the robot reaches. Where the registry can change the robot in place, its login and secret keep working: on Harbor that takes a robot reaching several projects and a user as the admin credential, because no robot may hold Harbor's robot update right. Any other change replaces the robot, and only with allow_new_secret: the answer carries the new secret once, and whatever logs in with the current one stops working. Asking for what the robot already holds changes nothing. The robot keeps its name, description and expiry. A browser session twin is mounted at the same path without the /api/v1 prefix (cookie authentication). ## OpenAPI ````yaml https://platform.ankra.app/openapi.json put /api/v1/org/registry-robots/{robot_name}/projects openapi: 3.1.0 info: title: Ankra Platform API version: v1 description: >- The Ankra platform HTTP contract. The /api/v1 surface is the public, bearer-authenticated API used by the Ankra CLI, MCP clients and automation; send a personal or service API token as `Authorization: Bearer `. Browser routes under /org and /chat are served on api.platform.ankra.app (each declares that server); they and /oauth/access authenticate with the ankra_session cookie, and mutations also require the X-Ankra-CSRF header. Every operation declares the credential it accepts, and no operation is served without one. This document is published deliberately: it describes the contract only and carries no organisation data or credentials. Report security issues to security@ankra.ai (see /.well-known/security.txt). servers: - url: https://platform.ankra.app security: - BearerAuth: [] tags: - name: Onboarding description: >- Generate a first website from a prompt and deploy it to a new organisation's cluster. - name: Access Gate description: >- Private service sign-in and membership checks for trusted Ankra proxy relays. - name: Canvas Datasets description: >- Read the fixed, named datasets canvas dashboards bind their charts, tables and stats to. - name: Canvases description: >- Keep dashboards and pages in the organisation's canvas library, with revision history, undo and pins. - name: Canvas Pages description: >- Publish a chat canvas artifact at a public pages address and take it down again. - name: Cloud Delegation description: >- Platform browser consent and organisation-bound connections for Ankra Cloud. - name: Organisation IAM description: >- Custom organisation roles and scoped role assignments for member and service-account identities. - name: Clusters description: Create, inspect and manage clusters, and the stacks deployed on them. - name: Managed Clusters description: Provider-managed control planes, driven through one common surface. - name: Imported Clusters description: Clusters that already existed and were connected to Ankra. - name: Cluster Access description: Kubeconfigs, service-account tokens and per-cluster access grants. - name: Kubernetes description: Read and act on the Kubernetes objects inside a cluster. - name: AWS Clusters description: >- Provision and manage self-managed k3s / kubeadm clusters on AWS EC2 in your own VPC. - name: Ankra Cloud Clusters description: >- Provision and manage self-managed kubeadm / k3s clusters on Ankra Cloud servers: a private network, a NAT router and a bastion per cluster. - name: DigitalOcean Clusters description: Provision and manage DigitalOcean Kubernetes clusters. - name: Hetzner Clusters description: Provision and manage Hetzner Kubernetes clusters. - name: OVH Clusters description: Provision and manage OVH Kubernetes clusters. - name: Scaleway Clusters description: Provision and manage Scaleway Kapsule clusters. - name: UpCloud Clusters description: Provision and manage UpCloud Kubernetes clusters. - name: Applications description: Deploy, configure and observe applications across the fleet. - name: Pipelines description: >- Pipeline definitions, the approval of the authority they declare, and the caches pipelines keep between runs. - name: Workspaces description: >- Personal workspaces on the organisation's CI pool where a repository's heavy commands run, and the repository profiles they are built from. - name: Deploy Targets description: >- Environments, the hosts registered to receive deployments, and the releases deployed to them. - name: Deploy Provenance description: >- Whether an application's deploys verify signed provenance from the organisation's own pipeline, the keys that provenance is signed with, and a dry-run that verifies images without deploying. - name: Backups description: >- Backup vaults, restore points, protection posture and captures for stacks and application deployments; a completed capture is not a verified restore. - name: Stack Profiles description: Reusable stack definitions, their versions and sharing. - name: Services description: >- Versioned service packages and explicit sharing. Runtime admission is separate from publication. - name: Charts description: Browse the chart catalogue behind stacks and addons. - name: Helm description: Helm registries, credentials and the charts they expose. - name: Executions description: Long-running platform executions and their jobs. - name: Operations description: Cancel in-flight cluster operations and their jobs. - name: Chat description: Conversational sessions, plans and confirmable actions. - name: AI Management description: >- Customer agent lifecycle, authenticated identity and organisation automation controls. - name: AI Agent Runs description: Autonomous agent runs and their outcomes. - name: AI Tickets description: The AI ticket board, its sync connections and settings. - name: AI Playbooks description: Reusable playbooks the AI lanes execute. - name: AI Conditions description: Conditions that gate AI autonomy. - name: AI Remediation description: >- The organisation's auto-remediation policy: what the AI lanes may fix by themselves, and who approves the rest. - name: AI Engineering Handoffs description: Work the AI lanes escalate to a human engineer. - name: AI Environment description: The environment and base stacks AI demos deploy into. - name: AI Memory description: >- What the assistant has learned about you: your cross-session memories and learned profile. - name: MCP Servers description: >- Register the MCP servers the organisation's AI agents can call, choose their tools and grant them to roles. - name: Security description: Findings, advisories, SBOMs, compliance and posture. - name: Cost description: Cluster and fleet cost, rate cards and cost settings. - name: Decisions description: >- The decision ledger behind the Security and Cost queues: proposals a surface computed, the approve and set-aside decisions people took on them, and the receipts of running them. - name: Usage description: >- What your organisation used of Ankra - vCPU-hours, playgrounds, managed services, hosted logs and metrics, and AI - per meter and period, with how completely it was measured and whether a published rate applies. - name: Billing description: Subscription and spend caps. - name: Organisation description: Members, invitations, audit logs and organisation settings. - name: Account description: >- Your own account: the contact email Ankra mails when it differs from your sign-in address. - name: Account Tokens description: Personal access tokens for the API and CLI. - name: Credentials description: The shared credential store. - name: AWS Credentials description: >- AWS credentials: access keys or CloudFormation-onboarded STS roles for cost, EKS and self-managed provisioning. - name: Ankra Cloud Credentials description: >- Ankra Cloud API tokens, shared by the self-managed and managed Ankra Cloud lanes. - name: Azure Credentials description: Azure credentials and SSH keys. - name: DigitalOcean Credentials description: DigitalOcean credentials and SSH keys. - name: Hetzner Credentials description: Hetzner credentials and SSH keys. - name: HPE Morpheus Credentials description: HPE Morpheus credentials and the capacity and quotas behind them. - name: OVH Credentials description: OVH credentials and SSH keys. - name: Proxmox Credentials description: Proxmox VE credentials and the capacity and quotas behind them. - name: Scaleway Credentials description: Scaleway credentials. - name: UpCloud Credentials description: UpCloud credentials and SSH keys. - name: Data Source Credentials description: Credentials for metrics and log sources. - name: DNS Credentials description: Credentials for DNS providers. - name: Object Storage Buckets description: >- Buckets Ankra creates and manages on an organisation's own provider credentials. - name: DNS description: DNS zones and records, including custom organisation zones. - name: Cloudflare description: Cloudflare domains and the credentials behind them. - name: Avura description: >- The linked Avura organization, the domains it shares with Ankra Platform, and their DNS records. - name: Variables description: Organisation- and cluster-scoped variables. - name: Secret Slots description: >- Store secrets in Vault and reference them by ${SECRET_SLOT:} sentinel instead of by value. - name: SOPS description: Encrypt and decrypt values with the organisation SOPS config. - name: Alerts description: Alert integrations and ingest credentials. - name: Notifications description: Notification routes and their delivery targets. - name: Support description: Support tickets. - name: AI Settings description: Organisation AI provider, model catalog and per-function model settings paths: /api/v1/org/registry-robots/{robot_name}/projects: put: tags: - Credentials summary: Change the projects a registry robot reaches description: >- Change which projects the robot reaches. Where the registry can change the robot in place, its login and secret keep working: on Harbor that takes a robot reaching several projects and a user as the admin credential, because no robot may hold Harbor's robot update right. Any other change replaces the robot, and only with allow_new_secret: the answer carries the new secret once, and whatever logs in with the current one stops working. Asking for what the robot already holds changes nothing. The robot keeps its name, description and expiry. A browser session twin is mounted at the same path without the /api/v1 prefix (cookie authentication). operationId: >- update_registry_robot_projects_api_v1_org_registry_robots__robot_name__projects_put parameters: - in: path name: robot_name required: true schema: title: Robot Name type: string - in: header name: authorization required: false schema: anyOf: - type: string - type: 'null' title: Authorization - in: header name: x-ankra-organisation-id required: false schema: anyOf: - type: string - type: 'null' title: X-Ankra-Organisation-Id requestBody: content: application/json: schema: $ref: '#/components/schemas/RegistryRobotProjectsUpdateRequest' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/RegistryRobotProjectsUpdated' description: Successful Response '401': description: Unauthorized '403': description: Forbidden '404': description: No robot with that name '409': description: >- The change needs a new secret and allow_new_secret is not set, the robot is managed by Ankra or has expired, the admin credential may not make the robot asked for, the robot's registry does not support this, or another change to it is still in progress '422': content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' description: Validation Error '503': description: The registry could not be reached security: - BearerAuth: [] components: schemas: RegistryRobotProjectsUpdateRequest: description: >- The projects a robot should reach from now on, replacing the ones it reaches. properties: allow_new_secret: default: false description: >- Let Ankra replace the robot when the registry cannot change it in place. The robot gets a new secret, and its login changes when it moves between one project and several. Whatever logs in with the current secret stops working. title: Allow New Secret type: boolean projects: description: >- Every project the robot should reach, 1 to 20 different ones, each with its own scope or permissions. items: $ref: '#/components/schemas/RegistryRobotProjectRequest' title: Projects type: array required: - projects title: RegistryRobotProjectsUpdateRequest type: object RegistryRobotProjectsUpdated: allOf: - $ref: '#/components/schemas/RegistryRobot' - properties: docker_login: description: >- The login command for the new secret; only when the secret changed. title: Docker Login type: string secret: description: The new secret, answered once; only when the secret changed. title: Secret type: string secret_changed: description: >- Whether the robot was replaced. When false, its login and secret still work. title: Secret Changed type: boolean warning: description: >- Set when the change was made but something after it did not finish, and says what is left. title: Warning type: string required: - secret_changed type: object title: RegistryRobotProjectsUpdated HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' title: Detail type: array title: HTTPValidationError type: object RegistryRobotProjectRequest: properties: permissions: anyOf: - type: array items: type: string - type: 'null' description: The robot's own grants on this project instead of a preset scope. title: Permissions project: anyOf: - type: string - type: 'null' description: >- The project: omitted, null or default for the organisation's own, otherwise an extra project's name; on an integrated registry, a project or repository name there (required). title: Project scope: anyOf: - enum: - push - pull - custom type: string - type: 'null' description: >- A preset for this project: push (push and pull) or pull. Defaults to push when neither a scope nor permissions are stated. title: Scope title: RegistryRobotProjectRequest type: object RegistryRobot: properties: account_email: description: >- The service account a robot on Google Artifact Registry is; absent on Harbor. title: Account Email type: string application: anyOf: - $ref: '#/components/schemas/RegistryRobotApplication' - type: 'null' description: >- The application an application robot belongs to; null for every other kind, and for one whose application is gone. created_at: type: string title: Created At credential_name: description: >- The registry credential holding the login. Unique across the listing, which a robot's name is not. title: Credential Name type: string description: type: string title: Description expires_at: anyOf: - type: string - type: 'null' description: >- When the registry stops honouring the robot; null for one that never expires. title: Expires At host: type: string title: Host kind: description: >- Who the robot belongs to: a member (user), organisation provisioning (organisation: the ci and pull robots) or one application (application). enum: - user - organisation - application title: Kind type: string managed: description: >- True for a robot Ankra minted and whose secret it fans out itself. It is listed and read here, never rotated or revoked. title: Managed type: boolean name: description: >- A member's robot: the name it was created under. A managed robot: ci, pull, or app-. title: Name type: string permissions: description: >- Every grant the robot holds, written resource:action; for a robot reaching several projects, every grant it holds on any of them. items: type: string title: Permissions type: array project: title: Project type: string project_access: description: >- Every project the robot reaches with the grants it holds there: one entry for a robot bound to one project, several for a robot reaching several, none for a managed robot whose project cannot be read. items: $ref: '#/components/schemas/RegistryRobotProjectAccess' title: Project Access type: array project_name: description: >- What a member addresses the project by: default for the organisation's own, the name it was created under for an extra project, and empty for a project on a registry the organisation runs itself. title: Project Name type: string projects: description: >- Every registry project the robot reaches; project and project_name are the first of them. items: type: string title: Projects type: array provider: description: >- The kind of registry the robot lives on: harbor for the Ankra registry and any integrated Harbor, google_artifact_registry for an integrated Google Artifact Registry. enum: - harbor - google_artifact_registry title: Provider type: string robot_name: title: Robot Name type: string rotated_at: anyOf: - type: string - type: 'null' title: Rotated At scope: description: >- The preset the grants amount to, or custom when they are neither preset. For a robot reaching several projects, the preset every project holds alike, or custom when they differ. enum: - push - pull - custom title: Scope type: string required: - name - kind - managed - robot_name - host - project - project_name - projects - project_access - scope - permissions - description - credential_name - application - created_at - rotated_at - expires_at title: RegistryRobot type: object ValidationError: properties: loc: items: anyOf: - type: string - type: integer title: Location type: array msg: title: Message type: string type: title: Error Type type: string required: - loc - msg - type title: ValidationError type: object RegistryRobotApplication: properties: id: type: string title: Id name: type: string title: Name required: - id - name title: RegistryRobotApplication type: object RegistryRobotProjectAccess: properties: permissions: description: >- Every grant the robot holds on this project, written resource:action. items: type: string title: Permissions type: array project: title: Project type: string project_name: description: >- What a member names the project by on a create: default or an extra project's name on the Ankra registry, the project's own name on a registry the organisation runs itself. title: Project Name type: string scope: description: The preset the grants on this project amount to, or custom. enum: - push - pull - custom title: Scope type: string required: - project - project_name - scope - permissions title: RegistryRobotProjectAccess type: object securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.