Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/HelenaLM32/ECHO/llms.txt

Use this file to discover all available pages before exploring further.

ECHO is a comprehensive digital platform built for the art and culture sector. It brings together three types of participants — creative professionals who want to showcase and sell their work, individuals and companies looking for artistic talent, and venue owners seeking content for their events — in a single unified marketplace.

Quick Start

Create your account and make your first connection on ECHO in minutes.

Platform Roles

Understand the three roles on ECHO and which one fits your needs.

Core Features

Explore the marketplace, orders, events, portfolios, and more.

API Reference

Integrate with ECHO’s REST API to build on top of the platform.

How ECHO works

ECHO solves the fragmentation of the cultural market by providing a single place where creative work is discovered, contracted, and delivered. The platform supports three interconnected workflows:

Create & Sell

Artists upload portfolios, publish services, and apply to physical events at venues.

Discover & Hire

Buyers browse listings, place orders, and communicate directly with creators.

Host & Manage

Venue managers list spaces, organize events, and connect with artists.

Get started

1

Create your account

Register at ECHO using your email or sign in with Google. Choose the role that matches your goals.
2

Set up your profile

Fill in your public name, bio, location, and social links. Upload an avatar and banner image to make your profile stand out.
3

Start participating

Content creators can publish services and portfolio projects. Service requesters can browse and place orders. Venue managers can list spaces and create events.
4

Manage your activity

Track orders, exchange messages with counterparties, leave reviews, and resolve any issues through the built-in dispute system.
ECHO supports both email/password login and Google OAuth. All authenticated API requests must include a JWT Bearer token obtained at login.

Build docs developers (and LLMs) love