> ## Documentation Index > Fetch the complete documentation index at: https://benchgen.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Replace a benchmark's files > Send one zip per file to replace, under its field name. A program zip needs `metadata.yaml` at its root. A benchmark with more than one task also needs `task`. A task that another benchmark also uses is refused, because changing it would change that benchmark too. Replacing never touches a run: runs that finished before the change keep their score and are listed so you can run those models again; nothing is re-run automatically. Unlike a question-answer benchmark's questions, these files stay replaceable however much has been run. Add `?dry_run=1` to validate without changing anything; it lists the runs the change would leave scored under the previous files. Only the creator and its collaborators may do this. Requires the `benchmark:edit` scope. ## OpenAPI ````yaml POST /api/competitions/{id}/replace_task_files/ openapi: 3.0.3 info: title: BenchGen Platform API version: 1.0.0 description: >- One API for the whole BenchGen platform: model catalogue and serving, fine-tuning and benchmarks, datasets (knowledge), and billing. ## Authentication Every request uses the same credential: a platform API token sent as `Authorization: Bearer bgn_...`. Create tokens in the web app under Profile Settings > Platform API tokens (the secret is shown exactly once), or via `POST /api/tokens/` with an interactive session. Revoking a token disables it platform-wide within 60 seconds. ## Scopes A token carries scopes chosen at creation; a request outside the token's scopes gets `403` with an explanatory message. | scope | grants | |---|---| | `models:read` | read model catalogues, job status, logs, GPU info | | `models:write` | deploy, train, merge, stop models and jobs | | `benchmark:read` | read benchmark runs and results | | `benchmark:run` | launch benchmark runs | | `benchmark:create` | create benchmarks in your account (drafts, Excel, bundles, specs); counts toward the creation limit | | `benchmark:manage` | edit and delete benchmarks you own or collaborate on | | `benchmark:publish` | publish and unpublish benchmarks you own or collaborate on | | `knowledge:read` | read your datasets and fine-tuning data | | `knowledge:write` | create, edit and delete datasets and fine-tuning data | | `billing:read` | read your balance and usage | | `agents:chat` | chat with your own agents through the API | | `agents:manage` | manage your agents, knowledge bases and channels | | `admin` | everything the account can do (staff accounts only) | ## For agents This document plus `/api/llms.txt` are the machine-readable entry points. Responses are JSON. Errors use conventional status codes; the body carries `error` or `message`. Knowledge endpoints return `[{"data": [...], "meta": {...}}]`. The complete auto-generated schema of every endpoint (including internal ones) lives at `/api/public-docs.json` (Swagger 2.0); this document is the curated, stable, supported surface. contact: url: https://benchgen.com servers: - url: https://api.benchgen.com security: - platformToken: [] tags: - name: auth description: Token introspection for services and integrations - name: tokens description: Manage your platform API tokens - name: models description: Model catalogue and serving - name: finetune description: Fine-tuning jobs, inference deployments, GPUs - name: knowledge description: Datasets and fine-tuning data (knowledge API) - name: billing description: Balance and usage - name: agents description: Chat with your agents (OpenAI-compatible facade) - name: benchmark description: Public benchmark (competition) listings. paths: /api/competitions/{id}/replace_task_files/: post: tags: - benchmark summary: Replace a bundle benchmark's scoring, ingestion or data in place description: >- Send one zip per file to replace, under its field name. A program zip needs `metadata.yaml` at its root. A benchmark with more than one task also needs `task`. A task that another benchmark also uses is refused, because changing it would change that benchmark too. Replacing never touches a run: runs that finished before the change keep their score and are listed so you can run those models again; nothing is re-run automatically. Unlike a question-answer benchmark's questions, these files stay replaceable however much has been run. Add `?dry_run=1` to validate without changing anything; it lists the runs the change would leave scored under the previous files. Only the creator and its collaborators may do this. Requires the `benchmark:edit` scope. parameters: - name: id in: path required: true schema: type: integer description: The benchmark id. - name: dry_run in: query required: false schema: type: string enum: - '1' description: Validate only; change nothing. requestBody: required: true content: multipart/form-data: schema: type: object properties: scoring_program: type: string format: binary ingestion_program: type: string format: binary reference_data: type: string format: binary input_data: type: string format: binary task: type: string description: Task id, needed when the benchmark has several. responses: '200': description: Checked (dry run) or replaced content: application/json: schema: type: object properties: valid: type: boolean id: type: integer tasks: type: array items: type: integer files: type: array items: type: object warnings: type: array items: type: string description: >- Leaderboard columns the new scoring program does not appear to write. replaced: type: array items: type: string description: Absent on a dry run. runs: type: object properties: finished: type: integer scored_under_previous_files: type: array description: >- Finished runs scored before the latest change. They keep their score; run the model again to score it with the current files. items: type: object properties: id: type: integer model_name: type: string owner: type: string created_when: type: string format: date-time '400': description: Fixable input, such as a zip that is not one or a shared task content: application/json: schema: type: object properties: valid: type: boolean errors: type: array items: type: string '403': description: Not the creator or a collaborator, or the token lacks benchmark:edit '404': description: No such benchmark components: securitySchemes: platformToken: type: http scheme: bearer bearerFormat: bgn_ opaque token description: >- Platform API token created under Profile Settings > Platform API tokens. Scopes are fixed at creation. ````