Manifest reference

A manifest is a JSON object that describes your listing. The marketplace validates every submitted manifest with the schemas exported by @dunea/plugin-sdk (pluginManifestSchema, themeManifestSchema, templateManifestSchema, skillManifestSchema), and validateManifest() runs exactly the same checks locally.

Keep the manifest in dunea.plugin.json (or dunea.theme.json, dunea.template.json, dunea.skill.json) at the root of your project. The dunea-plugin CLI looks for those names, and also accepts a .js or .cjs file that exports the manifest.

{
  "schemaVersion": 1,
  "kind": "plugin",
  "id": "order-alerts",
  "version": "1.0.0",
  "...": "the rest of the fields below"
}

If you prefer TypeScript, the typed helpers definePlugin(), defineTheme(), defineTemplate() and defineSkill() fill in schemaVersion and kind and give you autocomplete. The CLI does not read .ts files, so compile the manifest to .js, or write it out as JSON:

import { writeFileSync } from 'node:fs';
import { definePlugin } from '@dunea/plugin-sdk';

const manifest = definePlugin({
  id: 'order-alerts',
  version: '1.0.0',
  // ...the rest of the fields below
});

writeFileSync('dunea.plugin.json', `${JSON.stringify(manifest, null, 2)}\n`);

Shared fields

Every kind of listing has these fields.

Every URL field must start with https:// and be at most 500 characters.

developer

pricing

pricing is one of three shapes, chosen by model. Amounts are in US cents.

{ "model": "free" }

{ "model": "one_time", "amount": 1900, "currency": "USD" }

{ "model": "monthly", "amount": 900, "currency": "USD", "trialDays": 14 }

Templates are free or one_time only. See Pricing and payouts for how paid listings are billed.

Plugin fields

agentTools

Each entry is a tool the Dunea AI can call. See AI tools.

input describes the tool's arguments:

usage

Optional. Declares metered usage your service reports with POST /usage, charged to the owner's credits within their monthly cap.

siteScripts

See Site scripts and consent.

settings

Fields the owner fills in when they install your plugin. Dunea renders the form and sends you the values.

Values arrive as settings in the plugin.installed event, and you can read the current values any time with GET /settings. Owners can change them later; subscribe to plugin.settings.updated to hear when they do.

Cross-field rules

The validator also checks these rules across fields:

• Every event in subscribes needs the permissions listed for it in the events table. For example, shop.order.paid needs orders:read.
• webhookUrl is required if subscribes or agentTools is not empty.
• siteScripts requires the site:scripts permission.
• Tool names in agentTools must be unique.
• Every name in a tool's input.required must exist in its input.properties.

Theme fields

tokens

See the Themes guide for how to use each one.

Template fields

See Templates for the snapshot rules and the remix flow.

Skill fields

See Skills for how the AI uses them.

Validate locally

import { readFileSync } from 'node:fs';
import { validateManifest } from '@dunea/plugin-sdk';

const manifest: unknown = JSON.parse(readFileSync('dunea.plugin.json', 'utf8'));
const result = validateManifest(manifest);

if (!result.ok) {
  // e.g. "subscribes: \"shop.order.paid\" needs the \"orders:read\" permission"
  console.error(result.errors.join('\n'));
  process.exit(1);
}

Each error is path: message. dunea-plugin validate runs the same check from the command line, and dunea-plugin check adds the rest of the review checklist (screenshots, descriptions, prices, contrast, skill instructions) with a rule id for each finding.