Manage and delete resources

Everything you create stays in your workspace until you remove it. This page collects the cleanup path for each resource type in one place. It covers how to list what you have, how to delete a single resource, and how to delete in bulk. Each example assumes an initialized client. See Get started with the SDK.

Deletion methods

Resource	SDK method	REST endpoint
Agents	`client.agents.delete(agent_id)`	`DELETE /v2/flow/agents/{agent_id}`
Tools	`client.tools.delete(tool_id)`	`DELETE /v1/flow/tools/{tool_id}`
Files	`client.files.delete(id)`	`DELETE /v1/flow/files/{file_id}`
Vector databases	`client.vector_database.delete(database_id)`	`DELETE /v1/flow/vectordb/{database_id}`
Files in a vector database	`client.vector_database.delete_file(database_id, file_id)`	`DELETE /v1/flow/vectordb/{database_id}/files/{file_id}`
Data jobs	`client.data_jobs.delete(data_job_id)`	`DELETE /v1/flow/data-jobs/{data_job_id}`
Fine-tuning jobs		`DELETE /v1/flow/fine-tunes/{fine_tune_id}`
Fine-tuning projects		`DELETE /v1/flow/projects/{project_id}`

Delete fine-tuning jobs and projects over REST. See Delete fine-tuning jobs and projects for a worked example.

Deletion is permanent for every resource in the table. Nothing is moved to a recoverable state first, and a deleted resource cannot be restored.

List your resources

Begin by listing the resource type you intend to remove. The list methods differ in shape. Some return a list directly. Others return a response object with the results under data.

agents = client.agents.list_agents()           # list[Agent]
tools = client.tools.list().data               # paginated, default limit 100
files = client.files.list().data
databases = client.vector_database.list().data
jobs = client.data_jobs.list().data            # paginated, default limit 25
fine_tunes = client.fine_tuning.list().data
projects = client.projects.list().data         # paginated, default limit 100

for agent in agents:
    print(f"{agent.id}  {agent.name}")

client.tools.list(), client.files.list(), client.data_jobs.list(), and client.projects.list() accept paging arguments. When a workspace holds more resources than one page returns, increase limit or request successive pages with offset.

all_tools = []
offset = 0

while True:
    page = client.tools.list(offset=offset, limit=100)
    all_tools.extend(page.data)
    if len(all_tools) >= page.total:
        break
    offset += 100

print(f"{len(all_tools)} tools")

client.data_jobs.list() also filters by job_type and sorts with sort_by and sort_order. See Manage data jobs.

Delete a single resource

Each delete method takes the resource ID.

client.agents.delete(agent_id)
client.tools.delete(tool_id)
client.files.delete(file_id)
client.vector_database.delete(database_id)
client.data_jobs.delete(data_job_id)

Deleting a vector database removes the database and everything indexed in it. To remove one document and keep the database, delete the file instead. See Manage vector databases.

client.vector_database.delete_file(database_id, file_id)

Delete in bulk

To remove several resources at once, filter a list call to the resources you want to delete, then iterate over the result. This example removes every tool whose name starts with a test prefix.

targets = [t for t in client.tools.list().data if t.name.startswith("test-")]

print(f"Deleting {len(targets)} tools")
for tool in targets:
    client.tools.delete(tool.id)
    print(f"Deleted {tool.id}  {tool.name}")

Print the selection and confirm it before the delete loop runs. Deletion is permanent, and a filter that matches more than you expected cannot be undone.

Delete in dependency order when resources reference each other. Delete an agent before the tools it uses, and delete a vector database before the files that were ingested into it.

Delete fine-tuning jobs and projects

Delete fine-tuning jobs and projects with a direct HTTP request to the REST endpoints. Deleting a project does not delete the fine-tuning jobs in it. The jobs are disassociated from the project and remain in your workspace. To remove them as well, delete the jobs first.

import os
import requests

headers = {"Authorization": os.environ["SEEKR_API_KEY"]}

# Delete a fine-tuning job and its artifacts
requests.delete(
    f"https://flow.seekr.com/v1/flow/fine-tunes/{fine_tune_id}",
    headers=headers,
).raise_for_status()

# Delete a project
requests.delete(
    f"https://flow.seekr.com/v1/flow/projects/{project_id}",
    headers=headers,
).raise_for_status()

curl -X DELETE https://flow.seekr.com/v1/flow/fine-tunes/<fine_tune_id> \
  -H "Authorization: <your_api_key>"

curl -X DELETE https://flow.seekr.com/v1/flow/projects/<project_id> \
  -H "Authorization: <your_api_key>"

Both endpoints return 204 No Content on success. The deleted job or project no longer appears in client.fine_tuning.list() or client.projects.list().

Cancelling a job is not the same as deleting it. Cancel stops a job while it is queued or running and keeps the record, so the job stays in your list with a cancelled status. Delete removes the record and its artifacts, and works on a job in any state.

To remove all finished fine-tuning jobs from a workspace, list them with the SDK and delete them over REST.

import os
import requests

headers = {"Authorization": os.environ["SEEKR_API_KEY"]}
finished = [j for j in client.fine_tuning.list().data if j.status == "completed"]

print(f"Deleting {len(finished)} fine-tuning jobs")
for job in finished:
    requests.delete(
        f"https://flow.seekr.com/v1/flow/fine-tunes/{job.id}",
        headers=headers,
    ).raise_for_status()
    print(f"Deleted {job.id}")

​Deletion methods

​List your resources

​Delete a single resource

​Delete in bulk

​Delete fine-tuning jobs and projects

Deletion methods

List your resources

Delete a single resource

Delete in bulk

Delete fine-tuning jobs and projects