Canonical agent workflows manifest
Zero-auth JSON manifest of common multi-step workflows an agent might want to run. Each workflow references capability ids from /api/v1/capabilities so the published contract stays internally consistent — an agent framework can chain capability_id → OpenAPI operationId → HTTP shape in two lookups. Workflow id values and steps[].capability_id values are APPEND-ONLY forever; new workflows may be added, existing ones gain new optional fields but never shrink or rename. schema_version on both the top level and _meta advertises the manifest schema for client caching.
Each workflow carries enriched planner metadata — intent, expected_outcome, failure_modes, estimated_time_ms, and agent_instructions — plus per-step expected_response describing the body the step returns on success. The response also includes a schema.org JSON-LD @context and @graph with one HowTo node per workflow, so AI crawlers that speak schema.org but not Apier's bespoke shape can still plan a multi-step flow. See /recipes for the human-readable counterpart.
Request
- Base URL: https://www.apier.no
- URL: https://www.apier.no/workflows.json
- Auth: none required
Response
Workflow manifest with _meta carrying data_freshness and workflow_count, plus a schema.org JSON-LD @graph of HowTo nodes.
Example response
{
"version": "1",
"schema_version": "1.1.0",
"@context": "https://schema.org",
"@graph": [
{
"totalTime": "PT1S"
}
],
"workflows": [
{
"id": "workflow.lookup-deadlines",
"steps": [
{
"capability_id": "public.deadlines"
}
]
}
],
"_meta": {
"source": "apier.no internal manifest",
"schema_version": "1.1.0"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.