DEVELOPER CONTRACT / REST + MCP

Build against physical supply without inventing the missing facts.

REST and remote MCP expose the same durable project, evidence, sourcing, approval, and fulfillment state. This guide defines the authority boundaries that matter most.

01 / QUICKSTART

Connect the agent you already operate.

Use remote MCP for an agent platform that supports OAuth. Use REST for custom orchestration. Public discovery tools require no credential; private project and commercial state always does.

EXAMPLE / COPYABLE
{
  "mcpServers": {
    "supplyslate": {
      "url": "https://mcp.supplyslate.com/mcp"
    }
  }
}

The shortest complete workflow

  1. Create a project from an idea, file, BOM, exact part, or RFQ.
  2. Add structured requirements and private artifacts.
  3. Validate the current revision; preserve unknowns.
  4. Source an immutable package.
  5. A human approves suppliers, recipients, message, and artifacts.
  6. Suppliers clarify, quote, revise, or decline.
  7. Create an exact purchase plan and request human approval.
  8. Use supplier-hosted checkout and track merchant fulfillment.
EXAMPLE / COPYABLE
POST /v1/projects
Authorization: Bearer ss_live_••••
Idempotency-Key: your-project-id
Content-Type: application/json

{
  "name": "Outdoor inspection rover",
  "project_type": "mixed_build",
  "demand_lane": "builder",
  "origin_type": "idea",
  "brief": "Carry a 12 kg payload outdoors for four hours.",
  "build_quantity": 1,
  "ship_to": { "country_code": "US", "postal_code": "02108" },
  "substitution_policy": "approval_required",
  "data_classification": "commercial",
  "requirements": [],
  "fixture_kind": "real"
}