Authentication
Public registry endpoints can be inspected without a Project Key. Runtime and workspace operations require signed-in context and scoped credentials.
Developers
The API is the programmatic path from public Skill discovery to signed-in runtime invocation.
Public registry endpoints can be inspected without a Project Key. Runtime and workspace operations require signed-in context and scoped credentials.
Use registry/search endpoints to list public Skills, filter by task, runtime, verification state, and permission profile.
Skill detail endpoints expose manifest, schema, permissions, version, publisher, and review state before adoption.
Runtime invocation should authenticate with a Project Key created inside a signed-in project.
API clients should handle validation errors, unauthorized calls, policy blocks, rate limits, missing Project Keys, and prelaunch payment gates.
POST /v1/runtime/invoke with Authorization: Bearer PROJECT_KEY and a Skill slug plus typed input payload.