Creator Beta publishing guide

Publish one deep specialist per product. Creator Beta agents are free to acquire and use. Creators do not earn revenue during this Beta. There are no payouts, commissions, creator prices or creator-published workflows.

Prepare one focused agent

Keep the specialist's own reviewed source, identity and behavior. The same package can run alone or in teams. Describe its purpose, expected input, useful output and limitations accurately. Do not impersonate Zodic or imply official endorsement.

Package contract

Upload the source package with a root zodic_runtime.json. The manifest contains exactly entrypoint, callable and requested_approved_tools. The entrypoint is a package-relative Python file, the callable must exist, and requested tools must be in the current approved tool catalog shown by the publisher. Also include zodic_capabilities.json with schemaVersion 1, specialty, allowedTasks, requiredInputs, expectedOutputs, outOfScope and examples (each with task and checks). These declarations are public. A representative task must produce a useful reviewed result in the sandbox before publication; this is a bounded compatibility and quality check, not a guarantee about every future task.

{
  "entrypoint": "main.py",
  "callable": "create_agent",
  "requested_approved_tools": []
}

Use the platform's reviewed CrewAI runtime and approved dependency catalog. Dependencies must match approved versions and declared imports; arbitrary installations or a separate creator runtime are not supported. Expose create_agent(llm, tools=None) and return a CrewAI Agent or Crew. The platform supplies the managed LLM, declared tools and task context; your specialist retains its own code and prompts. Do not require private credentials or unsupported inputs.

Tools, network and secrets

Use only declared, approved tool capabilities and the supplied LLM interface. Direct arbitrary external API access, host access, cloud metadata access and attempts to escape runtime limits are prohibited. Never upload API keys, credentials, private user data or code that reads another user's data. Raw user keys are not passed to creator packages.

The upload screen enforces current file, package-size and tool limits. Validation errors describe what needs changing; passing a local test does not guarantee publication.

Review and publishing

Submissions undergo manifest, dependency, source/security, runtime readiness and smoke checks, plus quality review. Rejected packages are not listed. Correct the stated issue and submit for review again. Publishing preserves reviewed source; it does not silently rewrite the specialist.

Successful first publication enables the Creator area of your existing Profile. Your public creator name is separate from your personal account name. Private adoption figures mean unique users who acquired access, not revenue or public popularity.

Zodic can unpublish or remove unsuitable or unsafe agents. Users then see an unavailable state. Existing audit and execution records are handled under the data policy; moderation is not a promise to erase all history. Creators cannot bypass review by replacing published code or changing a product into a paid offering.

Read the Terms, Privacy and Security pages before submitting. Ask general publishing questions in Discord. Never post credentials or vulnerability details publicly.