---
title: "Read/intelligence tools (REST parity with MCP)"
method: GET
path: "/api/v1/insights/{kind}"
---

# Read/intelligence tools (REST parity with MCP)

`GET /api/v1/insights/{kind}`

## Request

- Base URL: `https://scope.bid`
- URL: `https://scope.bid/api/v1/insights/{kind}`
- Auth: HTTP bearer

Enveloped analytics: kind in spend, vendor-health, credential-alerts, conflict-log, market-rate, briefing. Returns summary + structured data + render_hints + deep link. Partner token needs the read scope. conflict-log requires party_name; market-rate requires category.

## Path parameters

- `kind` 'spend' | 'vendor-health' | 'credential-alerts' | 'conflict-log' | 'market-rate' | 'briefing', required

## Query parameters

- `group_by` string
- `days` integer
- `days_ahead` integer
- `party_name` string
- `category` string
- `jurisdiction` string

## Response `200`

Enveloped insight.

## Other responses

- `400`: Missing required parameter.
- `401`: Missing or invalid access token.
- `403`: The caller is not authorized: the caller's role does not grant the required capability, the partner token lacks the required scope, or the partner is not authorized to act for this firm.

---

[API](https://skmtc.dev/scope/apis/scope-api.md) · [All operations](https://skmtc.dev/scope/apis/scope-api/llms.txt) · [OpenAPI document](https://skmtc.dev/scope/apis/scope-api/revisions/164347b416ac?raw)