> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squasher.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Provider capabilities API

> Query project-scoped GitHub, Linear, Railway, and Vercel data through connected provider accounts.

Provider capability endpoints let API clients, the Squasher CLI, and MCP agents ask Squasher for
project-scoped integration data without handling provider tokens directly.

## GitHub activity

```text theme={null}
GET https://api.squasher.ai/v1/projects/{project_id}/providers/github/activity
```

Returns recent commits and pull requests for the project's primary linked repository.

## GitHub CI failures

```text theme={null}
GET https://api.squasher.ai/v1/projects/{project_id}/providers/github/ci-failures
```

Returns recent GitHub CI failure groups that Squasher has already ingested for the project.
Use `limit`, `branch`, `repo`, and `since` to narrow the result set.

## Linear issues

```text theme={null}
GET https://api.squasher.ai/v1/projects/{project_id}/providers/linear/issues
```

Returns recent issues for the Linear team configured on the project.

## Railway deployments and logs

```text theme={null}
GET https://api.squasher.ai/v1/projects/{project_id}/providers/railway/deployments
GET https://api.squasher.ai/v1/projects/{project_id}/providers/railway/logs
POST https://api.squasher.ai/v1/projects/{project_id}/providers/railway/restart
POST https://api.squasher.ai/v1/projects/{project_id}/providers/railway/redeploy
```

Use `service` and `environment` when the bound Railway project has more than one target.
Restart and redeploy are dangerous operations and should be confirmed by the caller.

## Vercel deployments and logs

```text theme={null}
GET https://api.squasher.ai/v1/projects/{project_id}/providers/vercel/deployments
GET https://api.squasher.ai/v1/projects/{project_id}/providers/vercel/deployment
GET https://api.squasher.ai/v1/projects/{project_id}/providers/vercel/deployment-logs
GET https://api.squasher.ai/v1/projects/{project_id}/providers/vercel/runtime-logs
```

Common query parameters include `deployment_id`, `branch`, `environment`, `state`, `query`,
and `limit`. Runtime logs also accept `level`, `source`, `request_id`, `status_code`, `since`,
and `until`.

## Agent handoff

Use provider capability endpoints when the project has an integration connected and the agent needs project-scoped context:

```text theme={null}
Inspect provider context for Squasher project <project_id>. Start read-only, use provider-specific filters, summarize deployment, CI, issue, or log evidence, and ask before restart, redeploy, or other write actions.
```

CLI equivalents live under `squasher providers ...`. MCP clients should call `search("providers")` or the exact operation id, then `execute` with the selected project and filters.