Publishing

Uploading AI Agents

Package and publish autonomous AI agents

Agents are first‑class listings on theaimart. An agent declares what it can do, which tools it needs, and how it runs — buyers can then hire it, embed it, or add it to a swarm.

The agent manifest

Every agent ships with a manifest describing its capabilities and interface:

{
  "name": "Invoice Reconciler",
  "version": "1.2.0",
  "description": "Matches invoices to bank transactions and flags anomalies.",
  "capabilities": ["document-parsing", "reconciliation", "reporting"],
  "tools": ["ocr", "http", "spreadsheet"],
  "inputs": {
    "invoices": { "type": "file[]", "required": true },
    "statement": { "type": "file", "required": true }
  },
  "outputs": { "report": { "type": "file" } },
  "runtime": { "type": "hosted", "timeout_seconds": 120, "memory_mb": 512 },
  "pricing": { "model": "usage", "unit": "run", "amount": 200, "currency": "INR" }
}

Runtime options

RuntimeDescription
hostedTheaimart runs your agent in a managed sandbox
webhookTheaimart forwards each invocation to your endpoint
bundledThe agent ships as a downloadable package the buyer runs locally

Publish

  1. •AI Agents → Upload Agents.
  2. •Upload the manifest and an icon; add screenshots or a short demo.
  3. •Declare capabilities and tools honestly — they power discovery and buyer trust.
  4. •Set pricing (usage‑based is common for agents — see Monetization).
  5. •Submit for review.

Or via API:

curl -X POST https://api.theaimart.co/api/v1/agents \
  -H "Authorization: Bearer $THEAIMART_API_KEY" \
  -H "Content-Type: application/json" \
  -d @manifest.json

Safety & permissions

Agents run with only the tools they declare. Requesting broad permissions (network, filesystem) lowers buyer trust and slows review. Declare the minimum set your agent actually uses.

  • •Secrets (API keys the agent needs) are injected at runtime from the buyer's vault — never hard‑code them.
  • •Log to stdout; Theaimart captures logs for the buyer's run history.

Next