REST and MCP documentation

Release 0.2.0-alpha.5 serves contract 0.2.0, taxonomy frontierbeacon.taxonomy.cybersecurity_services@0.1.0, and the frozen 37-profile corpus.

REST

Open ordinary profile JSON · OpenAPI JSON

curl 'https://api.frontierbeacon.io/v0.2.0/profiles?as_of=2026-09-04T00:00:00.000Z'
curl 'https://api.frontierbeacon.io/v0.2.0/profiles/by-market?country_code=DK&contract_version=0.2.0'

Routes also support canonical profile ID and typed external-identifier lookup. Contract 0.1.0 is a compatibility projection where representable. Unsupported versions return 409; malformed inputs return 400; missing profiles return 404.

MCP client

MCP server metadata JSON. Configure a Streamable HTTP client with:

{"mcpServers":{"frontierbeacon":{"url":"https://api.frontierbeacon.io/mcp"}}}

Or initialize directly:

curl -X POST 'https://api.frontierbeacon.io/mcp' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"example","version":"1.0.0"}}}'

The four read-only tools are list_profiles, get_profile, lookup_external_identifier, and filter_market_presence. There are no write tools or authentication in this bounded alpha. Product code cannot override a third-party harness that denies network or shell access.

Evidence, provenance and freshness

Every material claim carries a claim class, evidence references, observation time and extraction metadata. Claim classes are registry_verified, source_observed, business_claimed, inferred and unknown. An inference is never a verified claim. Each profile includes freshness timestamps and a next-review time; reads after that time add a review overlay while preserving the historical evaluation. Use as_of for reproducible reads.