Run your city from your own agent

Getting started

1. Sign up at /signup with your email, pick a plan and pay with Stripe. Your plan gives you a city of your own and its monthly credits.
2. Open your city. Each building is one job; crates (ideas, designs, products) travel between them. The Factory makes the product through a print-on-demand partner, or sources a dropship item.
3. Visit the Town Hall. Items waiting for a decision show up there. Approve or reject; nothing moves on without you while a building is set to ask.
4. Open Settings to set the default autonomy, change your password and create API keys.

Autonomy

Every building runs in one of three modes: suggest (it proposes, you do everything), ask (it does the work and waits for your approval) or auto (it acts on its own). Auto is only available on plans that include it and is never on by default.

MCP server

Point any MCP client at https://app.slopship.com/mcp with a bearer key. It speaks JSON-RPC over HTTP (initialize, ping, tools/list, tools/call); responses are plain JSON and the server keeps no session.

{
  "mcpServers": {
    "slop-city": {
      "url": "https://app.slopship.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Read tools: buildings_list, ideas_list, designs_list, ip_check_get, products_list, listings_list, orders_list, bank_summary, approvals_list, stuck_list, autonomy_get. Write tools: approvals_approve, approvals_reject, autonomy_set. Ask the server for tools/list to see the current set.

API access is included on City and Metropolis. Write tools need an MCP scope of read and write. A write never publishes, orders or spends by itself.

REST API

The REST API lives under https://app.slopship.com/api/v1 and uses the same bearer key. The OpenAPI 3.1 description is at /openapi.json.

curl -H "Authorization: Bearer $API_KEY" https://app.slopship.com/api/v1/approvals

• GET /api/v1/buildings, ideas, designs, ip-checks, products, listings, orders, bank, stuck, approvals, autonomy
• POST /api/v1/approvals/{item_id}/approve and /reject
• PUT /api/v1/autonomy/{building_id}

Free tools over MCP and REST

The free tools need no key. Without an Authorization header, /mcp lists and runs only these six tools, and each one is also a REST endpoint. Fair-use rate limits apply to every address.

• print_size_check, pod_profit_calc, trademark_risk_check, etsy_tags_titles, dropship_margin_calc, niche_validate
• GET or POST /api/v1/tools/<tool_name> with JSON or query arguments; GET /api/v1/tools lists them
• See /tools for the install snippet

API keys

Create keys in Settings. A key is shown once, only its hash is stored, and you can revoke it at any time. Keys stop working immediately if the plan no longer includes API access.

Use it from your agent

Step-by-step setup for Claude Code, Cursor and Claude Desktop is on the agents page: /docs/agents.

Machine-readable files

• /llms.txt and /llms-full.txt: a short and a full text description for AI assistants
• /openapi.json: REST API description
• /server.json and /.well-known/mcp: MCP server metadata
• /sitemap.xml