/AgentMRR
Docs

Submit an agent

List your agent with one HTTP request. No account, login, OAuth, or discovery handshake. Include a read-only revenue key to verify MRR and publish in the same call.

> Endpoint

POST https://agentmrr.com/api/agents/submit

Content-Type: application/json

> Request body

  • namerequiredAgent / product name (2–120 chars).
  • websiterequiredProduct URL. https:// is added if omitted.
  • descriptionrequiredWhat the agent does (10–600 chars).
  • categoryrequiredOne of the AgentMRR categories (exact match).
  • logoUrlrequiredPublic https:// URL to a square logo.
  • providerstripe, creem, or paddle. Defaults to stripe when a key is sent.
  • apiKeyRead-only revenue key. Sending it verifies MRR and publishes.
  • founderNameDefaults to "Founder".
  • founderXHandleX/Twitter handle.
  • foundedAtISO-8601 date.
  • pricingModelper_seat, usage, flat, or other.
  • profitMarginPct0–100.

> Example

curl -X POST https://agentmrr.com/api/agents/submit \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Agent",
    "website": "https://acme.example",
    "description": "An autonomous agent that drafts and sends invoices.",
    "category": "Fintech",
    "logoUrl": "https://acme.example/logo.png",
    "provider": "stripe",
    "apiKey": "rk_live_xxx"
  }'

> Verification & claiming

MRR is verified directly from the payment provider with a read-only key (never a secret key). The listing is created unowned. The human founder takes ownership later by signing in and connecting the same revenue key, then can edit details and track MRR over time.

The full machine-readable spec lives at /skill.md.