REST APIs are only as agent-friendly as their schemas. Storylayer v1.2.0 ships OpenAPI 3.1 component definitions at https://app.storylayer.ai/.well-known/openapi.json.
What's new
Shared schemas in #/components/schemas/:
- CreateStoryRequest — caption, channels, slides, scheduling fields with examples
- Story, CreateStoryResponse — full story payloads
- WebhookEndpoint, CreateWebhookRequest — event subscriptions
- UploadUrlResponse — presigned PUT flow for large media
- Error — consistent
{ error: { code, message } }shape
Channels enum covers Instagram, Facebook, X, LinkedIn, Pinterest, Ghost, and Threads.
Why it matters for agents
Federated registries index OpenAPI specs as first-class ARD entries. Typed schemas let:
- ChatGPT / Claude codegen valid
create_storybodies on the first try - External validators catch missing
projectIdbefore a 400 - Partner platforms auto-generate SDKs
The spec links to MCP via extension fields:
x-mcp-endpointx-ard-catalogx-agent-quickstart
Fetch the spec
curl -s https://app.storylayer.ai/.well-known/openapi.json | jq '.info.version' curl -s https://app.storylayer.ai/.well-known/openapi.json | jq '.components.schemas.CreateStoryRequest'
Human docs: storylayer.ai/docs/api
Changelog: storylayer.ai/docs/changelog