Skip to main content

aip.json

worka/aip.json is the manifest Worka reads to understand a pack.

Treat it as the pack’s public contract with the runtime. It is where you declare what the pack is, what it exposes, and what it expects from the platform.

What the manifest usually declares​

Depending on the pack, aip.json may include:

  • publisher and pack identity
  • display name, description, and version
  • the top-level tools the pack exposes
  • outbound domains
  • connection or provider requirements
  • webhook definitions
  • MCP server runtime metadata such as container image

The exact set of fields grows with the capability of the pack, but the purpose stays the same: make the pack legible to the runtime before it is executed.

Why the manifest matters​

Worka uses the manifest for several different jobs:

  • registration and probing
  • tool discovery
  • broker policy
  • connection handling
  • publication metadata

That means aip.json cannot be treated as a marketing file or a loose README. If it is wrong, the runtime model becomes wrong.

Keep the manifest concrete​

A good manifest is specific:

  • name the real tools
  • declare the real outbound domains
  • declare the real connection provider or auth requirement
  • keep the identity stable across builds

Do not hide important runtime needs in source comments and leave the manifest vague. Worka needs the manifest because it wants policy and routing decisions to happen before execution, not after.