Agent publishing guide

Build an AI agent that drives Gluecron repos, publish it to the marketplace, and earn 70% revenue share on every sale. Gluecron keeps 30% to cover infrastructure and fraud prevention.

What is an agent?

A Gluecron agent is a JSON manifest that describes an AI tool-use loop. It declares:

• A name, description, and icon.
• Which MCP tools the agent is allowed to call (scoped to the token provided by the buyer).
• A system prompt that instructs Claude how to use those tools to accomplish a goal.
• Optional input fields the user fills in before the agent runs.

Example agents: "Daily standup writer", "Auto-triage new issues", "Dependency upgrade PR opener", "Release notes drafter".

1. Write your agent

Create an agent.json in any repo:

{
  "name": "standup-writer",
  "displayName": "Daily Standup Writer",
  "description": "Reads yesterday's pushes and open PRs, then writes a concise standup summary.",
  "icon": "https://example.com/standup-icon.png",
  "version": "1.0.0",
  "tools": [
    "gluecron_repo_list_issues",
    "gluecron_list_prs",
    "gluecron_repo_read_file"
  ],
  "inputs": [
    {
      "key": "owner",
      "label": "GitHub/Gluecron owner",
      "type": "string",
      "required": true
    },
    {
      "key": "repo",
      "label": "Repository",
      "type": "string",
      "required": true
    }
  ],
  "systemPrompt": "You are a standup writer. Given the open PRs and recent issues on the target repo, write a concise standup update in bullet-point form: what was done yesterday, what is planned today, and any blockers.",
  "pricing": {
    "model": "per_run",
    "price_usd": 0.10
  }
}

2. Test locally

Use the Gluecron CLI to run your agent against a repo before publishing:

# Install the CLI
bun add -g @gluecron/cli

# Run the agent locally (no marketplace, no billing)
gluecron agent run ./agent.json \
  --input owner=my-org \
  --input repo=api \
  --token glc_your_dev_token

The CLI streams each tool call and its result to stdout so you can see exactly what Claude is doing. Errors in the system prompt or missing tool permissions surface here before any buyer sees them.

Testing checklist

• Run against a repo with open PRs and issues to verify the agent handles non-empty state.
• Run against a brand-new empty repo (edge case).
• Confirm the agent only calls the tools it declared in "tools" — the runtime rejects undeclared tool calls.
• Test with a read-only token to verify the agent degrades gracefully when write tools are unavailable.

3. Publish to the marketplace

Once you are happy with your agent, push agent.json to a public repo and submit via the marketplace form:

1. Visit /marketplace/agents/new.
2. Paste the URL of your public repo (e.g. https://gluecron.com/you/standup-writer).
3. Set a price — per-run, monthly subscription, or free. Minimum per-run price is $0.01.
4. Submit for review. The Gluecron team checks that the agent manifest is valid, the system prompt doesn't exfiltrate data, and the declared tool scope is appropriate. Reviews typically complete within 48 hours.

Revenue share

Payouts are processed monthly via Stripe to the bank account or PayPal address on file in your account settings. Minimum payout threshold is $10.

Versioning and updates

Bump "version" in agent.json, push, and submit an update from the marketplace dashboard. Buyers on a subscription get the new version automatically on their next run. Per-run buyers always get the latest approved version.

Breaking changes (removing tools, changing input keys) require a major version bump and a migration note in the changelog field.

Marketplace guidelines

• Agents must not exfiltrate repo content to external URLs not disclosed in the description.
• Agents must not call write tools without clear disclosure in the description (e.g. "This agent opens PRs automatically").
• System prompts are public — do not embed secrets or proprietary data in them.
• Agents that repeatedly fail (error rate > 20% over 7 days) are automatically delisted pending author review.

Full example: dependency upgrade agent

{
  "name": "dep-upgrader",
  "displayName": "Dependency Upgrade PR",
  "description": "Checks for outdated npm/bun dependencies and opens a PR with the bumped package.json.",
  "version": "1.0.0",
  "tools": [
    "gluecron_repo_read_file",
    "gluecron_create_pr",
    "gluecron_comment_pr"
  ],
  "inputs": [
    { "key": "owner", "label": "Owner", "type": "string", "required": true },
    { "key": "repo",  "label": "Repo",  "type": "string", "required": true }
  ],
  "systemPrompt": "You are a dependency upgrade bot. 1) Read package.json from the repo. 2) Identify any dependencies pinned to a major version older than the current latest on npm. 3) Produce an updated package.json with the bumped versions. 4) Open a PR titled 'chore(deps): bump outdated dependencies' with the updated file as the diff. 5) Comment on the PR with a table of what changed.",
  "pricing": {
    "model": "per_run",
    "price_usd": 0.25
  }
}