EasyTrades platform

Build with a trusted local marketplace.

One privacy-safe service layer for suppliers, homeowner jobs, coverage and activation workflows.

The foundation

Secure by default.

Approved access

Private operations use revocable bearer credentials with scoped permissions and individual rate limits.

Privacy-safe results

Public lead reads never include homeowner names, phone numbers, email addresses or exact locations.

One service layer

The website, REST API, MCP and automation all use the same validated marketplace logic.

REST API

Clear marketplace operations.

Use the REST API for approved server-to-server integrations. The base URL is https://easytrades.co.uk/api/v1.

POST/suppliers/import

Import a sourced public supplier

GET/suppliers/search

Search public supplier records

GET · PATCH/suppliers/:id

Inspect or update a supplier

POST/suppliers/:id/claim

Claim a public listing

GET · POST/jobs

Create or search marketplace jobs

GET/coverage

Read area and trade coverage

GET · POST/outreach/queue

Manage activation intent

Example request
curl "https://easytrades.co.uk/api/v1/coverage?area=Frodsham" \
  -H "Authorization: Bearer $EASYTRADES_API_KEY"

Model Context Protocol

EasyTrades for AI agents.

Compatible assistants can search local trades and anonymised homeowner opportunities using the remote Streamable HTTP endpoint.

https://easytrades.co.uk/mcpOpen the connection guide
Public toolssearch_tradessearch_leadsget_leadget_supplierget_coverageget_service_areas

Supplier lifecycle

From public record to verified trade.

  1. 01
    Discover

    Find a genuine business from a public source.

  2. 02
    List

    Import published facts and retain the source URL.

  3. 03
    Claim

    The business owner securely claims their profile.

  4. 04
    Verify

    EasyTrades completes the required onboarding checks.

Trust is part of the API.

  • Never fabricate or infer supplier details.
  • Always retain a direct public source URL.
  • Imported businesses are never automatically verified.
  • Outreach remains governed separately from queueing intent.
  • Every mutation and MCP tool call is audited.