Skip to main content
A kit bundles some of your organization’s agents, skills, and environment templates under one link. Anyone can read a published kit, and members of any organization can copy it. A copy becomes ordinary resources in the copier’s organization, with no link back to the kit. Use a kit to hand a working setup to a customer, a teammate in another organization, or the public.
Okik’s own kits are coming soon. Their links show “This kit is coming soon” until they are published.

​
What a kit carries

  • Agents, with their model, instructions, and tools.
  • Skills, with every file in them.
  • Environment templates, with their inline files, packages, setup commands, and network policy.
Secrets never travel. Vault credentials and the values of template environment variables are left out. The kit lists them as credentials the copier adds after copying. A template that mounts uploaded files cannot go in a kit; use inline files instead. A kit has a name, a description, a README, and an author, which its page shows. It holds at most 50 of each kind of resource.

​
Make and publish a kit

Any member can make, publish, and withdraw kits.
  1. Open Kits and choose Make kit.
  2. Fill in Name, Author, Description, and README, and pick the agents, skills, and templates to include. Choose Make kit.
  3. In the kit’s row menu, choose Publish. Then Copy link to share it.
Publishing takes a snapshot. Edits you make to the kit or to its agents, skills, and templates afterwards do not reach the public page until you publish again, which adds a new version under the same link. The link looks like https://app.orcapods.ai/kits/kit- followed by 17 letters and digits. Withdrawing a kit makes its link say it was withdrawn, and nobody can copy it. Publishing again brings it back under the same link. Copies already made are not affected. Every agent’s model is checked when you publish, as on any save.

​
Copy a kit

Open the kit’s link.
  • Signed out: choose Get started to make your Orca account and your own copy.
  • Signed in: choose Get started, then choose what to copy and what to call each copy, and choose Copy.
From the CLI:
With the API, read the kit with GET /api/public/kits/{public_id} (no key needed), then POST /api/kits/{public_id}/copy with {"assets": [{"key": "agent-1", "name": "my-support"}]}, listing each asset to copy and its new name. A copy is all or nothing. It is refused, and nothing is copied, when:
  • A name is taken. A copy would take a name already used by the same kind of resource: HTTP 409 name_taken. Choose other names and copy again.
  • A model needs a key you do not have. Each agent’s model is checked as on any save, so an agent that runs on its author’s own provider key needs your key for the same provider. Without it the response is HTTP 400 on assets, such as “own cannot be copied: Add your OpenAI key in Settings, Providers, or choose an Orca credit model”. Add the key and copy again.
After a copy, add the credentials the kit lists: an MCP server’s credential goes in a vault, and an environment variable goes on the copied template. A withdrawn kit returns HTTP 410 kit_withdrawn.

​
Routes

Paths are relative to https://api.orcapods.ai, without /v1.