Tradehand Developer Portal

Build read-only integrations that discover Tradehand, retrieve public pages as markdown, or call the Tradehand MCP server. These endpoints do not create jobs, contact people, or change business data.

Quickstart

Check the versioned REST API:

curl https://tradehand.com/api/v1/status

Read a public page as markdown:

curl -H "Accept: text/markdown" https://tradehand.com/pricing

Initialize the MCP Streamable HTTP transport:

curl https://tradehand.com/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"example","version":"1.0"}}}'

Documentation and schemas

Access, API keys, and environments

The public read API and MCP discovery tools require no API key and are free to call.

The production endpoint is safe for examples because these public operations cannot write data.

Tradehand does not currently expose private business operations or a public write sandbox.

Versioning and deprecation

REST endpoints use a major version in the URL, beginning with /api/v1. Breaking changes move to a new major version. A deprecated version remains available for at least 180 days and returns Deprecation, Sunset, and a successor-version link before removal.

The legacy /api/markdown route sunsets on 22 February 2027; use /api/v1/pages/markdown for new integrations.

Rate limits

Each public REST runtime allows 60 requests per 60 seconds per client address. Responses return structured RateLimit and RateLimit-Policy fields under the tradehand-public policy; HTTP 429 also returns Retry-After.

Errors

REST errors use RFC 9457 application/problem+json with type, title, status, detail, and instance. Tradehand adds a stable code and a resolution hint. MCP errors remain JSON-RPC 2.0 errors as the MCP protocol requires.