Skip to main content

Access monitoring reports through the API and MCP

View Tines 3B reports via API endpoints and via MCP.

Written by Jamie Gaynor

Tines 3B exposes your monitoring data through REST endpoints at /api/v1/reports/ and through MCP tools. These let you retrieve workflow health, storage, connector traffic, AI usage, and dependency data programmatically, so you can integrate Tines 3B metrics into your own tooling, dashboards, or automation.

Available reports

You can request the following reports:

  • Workflows (/api/v1/reports/workflows): Execution counts, failure rates, and last-run timestamps for active workflows.

  • Spaces (/api/v1/reports/spaces): Storage consumed per space.

  • Dependencies (/api/v1/reports/dependencies): Python, Node.js, and Dockerfile dependencies declared by your workflows.

  • Connectors (/api/v1/reports/connectors): Request and error counts per connector, grouped by day, workflow, or source.

  • AI usage (/api/v1/reports/ai): Token usage, model, and spend across workflow runs, workflow builds, and personal chats.

Each report returns items matching your access: if you have tenant-wide read access, you see all spaces; otherwise, you see only the spaces you can read. Personal-chat usage is visible only to the person who generated it.

Authentication

Reports require an API key passed as a Bearer token in the Authorization header. Create an API key from your user or service account settings. The key acts as you or as the service account, so the reports respect your grants.

curl https://your-tenant.3b.tines.com/api/v1/reports/workflows \   -H 'Authorization: Bearer 3b_sk_your_key'

Filtering and grouping

Most reports accept query parameters to filter and group results:

  • space_id: Limit to a single space.

  • days: A rolling window, from 1 to 90 days (default 30). Time-series reports like AI usage and connector traffic use this window.

  • start and end: Explicit ISO 8601 timestamps, aligned to UTC day boundaries.

  • group_by: Change aggregation. For example, workflows can group by workflow, space, or day; dependencies can group by workflow or dependency.

Refer to the interactive API documentation at /api/v1/docs on your tenant for the full parameter list per endpoint.

Pagination

Reports are paged. A default page returns up to 50 items. Pass limit to request fewer items per page. When more results exist, the response includes a Link header with rel="next" and an X-Next-Cursor header. Follow the link or pass the cursor as ?cursor= on your next request.

curl 'https://your-tenant.3b.tines.com/api/v1/reports/workflows?limit=10' \   -H 'Authorization: Bearer 3b_sk_your_key'

MCP access

If you have connected an MCP client to Tines 3B, you can call the corresponding tools:

  • get_workflows_report

  • get_spaces_report

  • get_dependencies_report

  • get_connectors_report

  • get_ai_report

Each tool accepts the same filters and grouping options as its REST counterpart and returns the same data shape.

Read the Connect an AI client to Tines 3B with MCP article for setup steps.

Response structure

Every report response includes:

  • scope: Either tenant (you have tenant-wide read access) or visible_spaces (you see only spaces you can read).

  • window: The time range the report covers, with start, end, and days. Storage reports have no window and return null.

  • filters: The filters applied to this result.

  • items: The array of report rows.

The shape of each item depends on the report and grouping. Consult /api/v1/docs for schemas.

Related Articles
Did this answer your question?