Picogrid

Legion Platform API

The Legion Platform HTTP API (v3, OpenAPI 3.1.0) for controlling and integrating data from unmanned and mission systems: entities and entity locations, feeds (message and file data) and feed definitions, tracks and track locations, tasking (dispatch commands over MQTT) and command registration, events and event subscriptions with delivery channels, notifications, video streams and DVR recordings, WebRTC connections, fine-grained authorization and permission templates, organizations and users, integrations (OAuth clients), and cross-Legion federation. Secured with OAuth 2.0 through a Keycloak "legion" realm.

GitHub

Documentation

📖
APIReference
https://docs.picogrid.com/reference
📖
GettingStarted
https://docs.picogrid.com/reference/start
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/picogrid/refs/heads/main/authentication/picogrid-authentication.yml

Other Resources

🔗
OAuthScopes
https://raw.githubusercontent.com/api-evangelist/picogrid/refs/heads/main/scopes/picogrid-scopes.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/picogrid/refs/heads/main/errors/picogrid-problem-types.yml
🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/picogrid/refs/heads/main/conventions/picogrid-conventions.yml
🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/picogrid/refs/heads/main/data-model/picogrid-data-model.yml
🔗
Webhooks
https://raw.githubusercontent.com/api-evangelist/picogrid/refs/heads/main/asyncapi/picogrid-events-webhooks.yml
🔗
X-MCPServerCandidate
https://raw.githubusercontent.com/api-evangelist/picogrid/refs/heads/main/mcp/picogrid-mcp.yml
🔗
Conformance
https://raw.githubusercontent.com/api-evangelist/picogrid/refs/heads/main/conformance/picogrid-conformance.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/picogrid/refs/heads/main/apis.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/legion-platform-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
name: Legion Platform API
description: 'The Legion Platform HTTP API (v3, OpenAPI 3.1.0) for controlling and integrating data from
  unmanned and mission systems: entities and entity locations, feeds (message and file data) and feed
  definitions, tracks and track locations, tasking (dispatch commands over MQTT) and command registration,
  events and event subscriptions with delivery channels, notifications, video streams and DVR recordings,
  WebRTC connections, fine-grained authorization and permission templates, organizations and users, integrations
  (OAuth clients), and cross-Legion federation. Secured with OAuth 2.0 through a Keycloak "legion" realm.'
humanURL: https://docs.picogrid.com/reference
baseURL: https://legion-prod.picogrid.com
version: 3.0.0
tags:
- Legion
- Systems Integration
- Command and Control
properties:
- type: APIReference
  url: https://docs.picogrid.com/reference
- type: GettingStarted
  url: https://docs.picogrid.com/reference/start
- type: Authentication
  url: authentication/picogrid-authentication.yml
- type: OAuthScopes
  url: scopes/picogrid-scopes.yml
- type: ErrorCatalog
  url: errors/picogrid-problem-types.yml
- type: Conventions
  url: conventions/picogrid-conventions.yml
- type: DataModel
  url: data-model/picogrid-data-model.yml
- type: Webhooks
  url: asyncapi/picogrid-events-webhooks.yml
- type: X-MCPServerCandidate
  url: mcp/picogrid-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate
    — a tool list derived from the published API contracts, not an existing server. The scorer already
    read the manifest and reported mcp_server correctly; the MCPServer type was crediting the artifact-type
    surfaces with a server that does not exist.'
- type: Conformance
  url: conformance/picogrid-conformance.yml