SDK

Build agent and automation workflows around FiveX.

FiveX SDK guidance helps builders model repeatable workflows around REST resources, MCP tools and connector-managed channel access, without scattering credentials across scripts.

Get started

Open FiveX MCP setup in your AI agent.

Start from the agent you already use. The prompt connects the agent to the FiveX MCP server, asks for your FiveX MCP key at runtime and verifies which FiveX data it can retrieve.

Using another IDE agent such as Cline or Windsurf? Copy this prompt.

Connect this workspace to the FiveX MCP server so I can retrieve my FiveX e-commerce data. MCP server URL: https://fivex.com/mcp/ Before connecting, ask me to paste my FiveX MCP key from https://fivex.com/portal/public/account/mcp. If the setup flow also shows a secret, do not print it, commit it, store it in source code or include it in logs. Treat credentials as private runtime input. Authentication: add the HTTP header "Authorization: Bearer <FIVEX_MCP_KEY>" to every request to the MCP server listed above. Use the key I provide at runtime. Instructions for you as an AI agent: - First check whether you have a command-line tool to add MCP servers, such as "claude mcp add", "codex mcp add", "gemini mcp add" or another MCP client command. - If you have a command-line tool, add the FiveX MCP server using the "http" transport and the server URL above. If the tool supports headers, configure the Authorization bearer header with the key I provide. If it uses OAuth, open the login flow and guide me through it. - If you do not have command-line MCP setup, manually add the server in your MCP or connector settings using the URL above and the header "Authorization: Bearer <FIVEX_MCP_KEY>". - After setup, retrieve the available tools from the FiveX MCP server. - Briefly tell me which FiveX account information, marketplace data, orders, inventory, advertising, product content or analytics you can now retrieve. - Start with read-only requests. Do not make operational changes until I explicitly approve the exact action.

SDK

SDK thinking, backed by the surfaces FiveX ships today.

Use these patterns when a coding agent, backend service or internal tool needs stable access to marketplace context.

01

Create free account

Create your workspace, connect the channels that matter and choose the developer surface that fits your build: REST endpoints, FiveX MCP or connector-managed workflows.

02

Browse connectors

FiveX connector infrastructure keeps authentication, retries, channel changes and data models in one layer so developer teams can build workflows instead of babysitting every platform API.

03

Explore MCP

Connect AI assistants to FiveX context for Amazon, bol, Kaufland, Otto, Shopify, Meta Ads, Google Ads and more. FiveX handles authentication, permissions and connector complexity so builders can create approved workflows without touching every platform API directly.

04

View API

FiveX SDK guidance helps builders model repeatable workflows around REST resources, MCP tools and connector-managed channel access, without scattering credentials across scripts.

Workflow

SDK thinking, backed by the surfaces FiveX ships today.

Use these patterns when a coding agent, backend service or internal tool needs stable access to marketplace context.

  1. 1

    Create your workspace, connect the channels that matter and choose the developer surface that fits your build: REST endpoints, FiveX MCP or connector-managed workflows.

  2. 2

    FiveX connector infrastructure keeps authentication, retries, channel changes and data models in one layer so developer teams can build workflows instead of babysitting every platform API.

  3. 3

    FiveX SDK guidance helps builders model repeatable workflows around REST resources, MCP tools and connector-managed channel access, without scattering credentials across scripts.

  4. 4

    Use FiveX as the governed layer between marketplace data, channel APIs and the teams or AI assistants that need to act on them.

Turn scripts into governed workflows.

Use FiveX as the permissioned layer between your code, AI assistants and marketplace channels.