Synthsynd World API

Build with the marketplace

Browse public agents, prompts, tools, and MCP listings through REST or connect an MCP client to the marketplace tools.

GET

/api/v1/items

Public read endpoint

Supports q, type, limit, and offset. The maximum page size is 100.

curl "/api/v1/items?type=agent&q=research&limit=20&offset=0"

{
  "items": [
    {
      "id": "…",
      "name": "…",
      "description": "…",
      "image_url": "…",
      "price_usd": 0,
      "user_id": "…",
      "is_free": true,
      "created_at": "…",
      "statusType": "agent",
      "token_address": null
    }
  ],
  "count": 1,
  "limit": 20,
  "offset": 0
}

POST

/mcp

Streamable HTTP JSON-RPC endpoint. Create an API key, then send it as a Bearer token. The available read-only tools are search_marketplace and get_listing.

curl -X POST http://localhost:3000/mcp \
  -H "Authorization: Bearer $SYNTHSYND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

POST · API key required

/api/swarms/agent-completions

Run a task with one agent configuration. Responses use your configured model and debit credits from the account that owns the key.

curl -X POST http://localhost:3000/api/swarms/agent-completions -H "Authorization: Bearer $SYNTHSYND_API_KEY" -H "Content-Type: application/json" -d '{"agent_config":{"name":"Researcher"},"task":"Summarize marketplace activity."}'

POST · API key required

/api/swarms/swarm-completions

Run 2–5 configured agents in parallel, then synthesize their results. Each agent call and the synthesis call consume one inference credit unit; configure the unit cost with API_INFERENCE_CREDITS.

Supported filters

type: agent, prompt, tool, mcp, or all
q: searches item names and descriptions
limit / offset: paginated results

Publishing and payments

Compatibility routes include publishing, editing, reviews, owner products, paid-content access, token linking, and bundle creation. Inference needs OpenAI and Supabase service-role configuration plus account credits. Stripe checkout requires completed seller onboarding and webhook setup. Token launch and creator-fee claims use Jupiter Studio when configured; x402 settlement still needs a payment facilitator.