Discovery

Compact multi-step workflow planning manifest with telemetry-derived p95

Compact machine-readable planning manifest for AI agents executing multi-step Norwegian company authority and filing workflows. Distinguished from /workflows.json by the observed_p95_ms field on each workflow: derived from mcp_query_log rolling 30-day p95 (success rows only, summed across the workflow's tool_names) at request time. NOT an authored estimate. NOT a committed SLA. The top-level differentiation_note carries the literal phrase "observed, not committed" so an agent reading the manifest cannot confuse the value with a service-level guarantee. Fail-OPEN: if the telemetry query fails or a workflow's tools have zero rows in the 30-day window, observed_p95_ms is null (the route never throws and never returns 5xx). Schema lives at /agents.json/schema.json (JSON Schema 2020-12). For verbose HowTo planning (intent / expected_outcome / per-step expected_response), see /workflows.json — details_url on each entry cross-links there.

get/agents.json

Request

  • Base URL: https://www.apier.no
  • URL: https://www.apier.no/agents.json
  • Auth: none required

Response

Agent planning manifest. The route ALWAYS returns 200 — fail-OPEN per the telemetry-derived observed_p95_ms contract.

schema_versionstring required
differentiation_notestring required

Plain-prose statement explaining that observed_p95_ms is telemetry-derived (not committed) and cross-referencing /workflows.json for the verbose HowTo surface. Contains the literal substring observed, not committed.

generated_atstring date-time required

Changes

No recorded changes to this operation across all 1 revision of this API.