SCOUT IntelligenceSDK
MCP beta Swagger Documents Reference Implementation Demo
Developer site

Integrate the SCOUT Intelligence SDK into your own app.

The SCOUT Intelligence SDK gives integrators a machine-to-machine path into monitored assets and event feeds. Authenticate with OAuth2 client credentials, fetch a user feed, and build your own event views, maps, and alert workflows.

Swagger Documents Reference implementation Demo site
Production API
https://api.scout.silverpine.com/access
Auth model
OAuth2 client_credentials via Cognito
Customer configuration
Mapped account email, user UUID, client ID, and separately delivered client secret

Quickstart

  1. Load the customer-specific account email, user UUID, client ID, and client secret from your server-side configuration.
  2. Request an access token using HTTP Basic authentication and the OAuth2 client_credentials grant.
  3. Include the returned access_token as a Bearer token in requests to https://api.scout.silverpine.com/access.
  4. Call GET /v1/feed/{userid} with the mapped user UUID, or manage monitored assets through /v1/assets.
curl --request POST \
  --user "$CLIENT_ID:$CLIENT_SECRET" \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'grant_type=client_credentials' \
  --data-urlencode 'scope=keepsafe-access/api keepsafe-access/feed keepsafe-access/assets.read keepsafe-access/assets.create keepsafe-access/assets.update keepsafe-access/assets.delete' \
  https://oauth.scout.silverpine.com/oauth2/token

Keep the client secret on the server. Never expose it to browser code, source control, logs, tickets, or shared documents. The production token hostname above is the canonical SCOUT OAuth endpoint; customer credentials work only with their provisioned scopes and mapped identity.

Beta

SCOUT MCP

MCP is a separate, read-only interface over SCOUT Access for compatible AI clients. It complements the REST API; it does not replace it.

MCP endpoint
https://mcp.scout.silverpine.com/mcp

Available tools

  • scout_list_assets
  • scout_get_asset
  • scout_get_feed

Required profile scopes

  • keepsafe-access/mcp
  • keepsafe-access/feed
  • keepsafe-access/assets.read

The identity and feed user are derived by the server. MCP exposes no create, update, delete, or raw proxy tools.

The beta begins as an internal and synthetic-data pilot. Existing customer credentials are unchanged and cannot use MCP unless they are explicitly provisioned for it.

Feed endpoint

GET/v1/feed/{userid}

Returns the event feed for the specified user. The response includes compatibility metadata under _keepsafe.

Asset collection

GET/v1/assets
POST/v1/assets

List monitored assets for the authenticated user or create a new one with coordinates, radius, and optional description/query fields. Create requests must include the mapped account email supplied during onboarding.

Individual asset

GET/v1/assets/{id}
PUT/v1/assets/{id}
DELETE/v1/assets/{id}

Retrieve, update, or delete a specific asset. Ownership is enforced, so users can only modify assets associated with their token identity; updates must retain the mapped account email.