---
title: "Repo Feeds"
method: GET
path: "/v1/teams/{team_id}/repo/feeds"
tags: ["team repo"]
---

# Repo Feeds

`GET /v1/teams/{team_id}/repo/feeds`

Every `kind: feed` record in this team's tree, with its clock and its tape.

THE CLOCKS THAT LIVE IN THE TREE. `scheduled_tasks` holds the wakes an
agent armed; a feed is a rhythm the shop declared in its own files, and
until this route the only way to see one was to open the folder. Each row
carries when it last ran, whether it worked, when it is next due, and the
last runs with every field they moved — the same history the healthcheck
turn reads, so the schedules tab and the turn cannot disagree about what
changed at 06:00.

## Path parameters

- `team_id` string, uuid, required

## Query parameters

- `history_limit` integer

## Headers

- `authorization` string, nullable
- `x-darwin-token` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422` — Validation Error

## Changes

> 32 revisions in range; 1 not diffed.

- **2026-09-05** `f1c8ed62c117` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/stormy/apis/stormy-control-plane/changes/v1/teams/:team_id/repo/feeds/get.md)

---

[API](https://skmtc.dev/stormy/apis/stormy-control-plane.md) · [All operations](https://skmtc.dev/stormy/apis/stormy-control-plane/llms.txt) · [OpenAPI document](https://skmtc.dev/stormy/apis/stormy-control-plane/revisions/b09e3c4ee2af?raw)
