SupplySlate

REMOTE · MCP.SUPPLYSLATE.COM · SCANNED AUG 17

B2B supply network for buyer-owned agents to source requirements and receive verified offers.

Available components

+9 this week 71 71 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security69

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability75

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 3694 tokens (~67/item across 55 items; 55 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management37

Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage74

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
9% of tool parameters carry a description.Partial
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a current MCP spec version (2026-07-28).Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.supplyslate.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http com-supplyslate-sourcing https://mcp.supplyslate.com/mcp

# ~/.codex/config.toml

[mcp_servers.com-supplyslate-sourcing]
url = "https://mcp.supplyslate.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-supplyslate-sourcing": {
      "type": "remote",
      "url": "https://mcp.supplyslate.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-supplyslate-sourcing --url https://mcp.supplyslate.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-supplyslate-sourcing:
    url: "https://mcp.supplyslate.com/mcp"

// mcp.json

{
  "mcpServers": {
    "com-supplyslate-sourcing": {
      "type": "http",
      "url": "https://mcp.supplyslate.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog Show cosmetic changes

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

17 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
15 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
14 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
11 Aug 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
10 Aug 26 +3
- HSTS header: fail → pass ▲ security
- Tool “create_purchase_plan” rewrote its description, which is the text the model reads security
- Schema quality: 3073 → 3694 ▼ functional
- Schema quality: poor → fair functional
- New tool “decide_supplier_order_cancellation” functional
- New tool “open_warranty_claim” functional
- New tool “report_order_issue” functional
- New tool “request_order_cancellation” functional
- New tool “request_order_return” functional
- New tool “update_supplier_order_issue” functional
- New tool “update_supplier_order_return” functional
- New tool “update_supplier_warranty_claim” functional
- “create_project” added an optional parameter “fixture_kind” cosmetic
- “submit_sourcing_request” added an optional parameter “fixture_kind” cosmetic
9 Aug 26 +5
- Authorization: unverified → partial ▲ security
- Tool “decline_supplier_rfq” rewrote its description, which is the text the model reads security
- Tool “get_supplier_offers” rewrote its description, which is the text the model reads security
- Tool “list_sourcing_requests” rewrote its description, which is the text the model reads security
- Tool “submit_supplier_quote” rewrote its description, which is the text the model reads security
- Tool “upsert_supplier_catalog” rewrote its description, which is the text the model reads security
- Schema quality: 56 → 65 ▼ functional
- Tool coverage: 23% → 10% ▼ functional
- “decline_supplier_rfq” added a required parameter “reason_code”, so existing callers break ▼ functional
- “upsert_supplier_catalog” added a required parameter “idempotency_key”, so existing callers break ▼ functional
- “submit_supplier_quote” dropped the required parameter “source_evidence” ▼ functional
- Tool “decline_supplier_rfq” now declares an output schema ▲ functional
- Tool “describe_supplyslate” now declares an output schema ▲ functional
- Tool “get_connection_guide” now declares an output schema ▲ functional
- Tool “get_sourcing_request” now declares an output schema ▲ functional
- Tool “get_supplier” now declares an output schema ▲ functional
- Tool “get_supplier_offers” now declares an output schema ▲ functional
- Tool “get_supplier_profile” now declares an output schema ▲ functional
- Tool “get_supplier_rfq” now declares an output schema ▲ functional
- Tool “list_sourcing_categories” now declares an output schema ▲ functional
- Tool “list_sourcing_requests” now declares an output schema ▲ functional
- Tool “list_supplier_rfqs” now declares an output schema ▲ functional
- Tool “list_supplier_taxonomy” now declares an output schema ▲ functional
- Tool “search_suppliers” now declares an output schema ▲ functional
- Tool “submit_sourcing_request” now declares an output schema ▲ functional
- Tool “submit_supplier_quote” now declares an output schema ▲ functional
- Tool “upsert_supplier_catalog” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: fair → poor functional
- Server version: 1.1.0 → 2.0.0 functional
- New tool “ask_rfq_clarification” functional
- New tool “attach_artifact_reference” functional
- New tool “create_artifact_upload” functional
- New tool “create_catalog_import” functional
- New tool “create_project” functional
- New tool “create_provider_checkout_handoff” functional
- New tool “create_purchase_plan” functional
- New tool “get_bom” functional
- New tool “get_checkout_handoffs” functional
- New tool “get_compatibility” functional
- New tool “get_live_fabrication_capabilities” functional
- New tool “get_order” functional
- New tool “get_product” functional
- New tool “get_project” functional
- New tool “get_purchase_plan” functional
- New tool “get_requirement_schema” functional
- New tool “list_fabrication_processes” functional
- New tool “list_orders” functional
- New tool “list_project_validations” functional
- New tool “list_supplier_orders” functional
- New tool “request_purchase_approval” functional
- New tool “revise_supplier_quote” functional
- New tool “search_live_components” functional
- New tool “search_products” functional
- New tool “source_project” functional
- New tool “update_availability” functional
- New tool “update_project_requirements” functional
- New tool “update_supplier_capabilities” functional
- New tool “update_supplier_order” functional
- New tool “upsert_bom” functional
- New tool “validate_project” functional
- “submit_supplier_quote” added an optional parameter “fees_minor” cosmetic
- “submit_supplier_quote” added an optional parameter “quote_number” cosmetic
- “submit_supplier_quote” added an optional parameter “shipping_minor” cosmetic
- “submit_supplier_quote” added an optional parameter “tax_minor” cosmetic
- “submit_supplier_quote” dropped the optional parameter “quote_reference” cosmetic
8 Aug 26 −1
- Tool coverage: 38% → 23% ▼ functional
- Schema quality: 382 → 908 ▼ functional
- Schema quality: good → fair functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “decline_supplier_rfq” functional
- New tool “get_supplier” functional
- New tool “get_supplier_profile” functional
- New tool “get_supplier_rfq” functional
- New tool “list_supplier_rfqs” functional
- New tool “list_supplier_taxonomy” functional
- New tool “search_suppliers” functional
- New tool “submit_supplier_quote” functional
- New tool “upsert_supplier_catalog” functional
7 Aug 26 0
- Stability: unverified → 0.03 ▲ functional

Show 5 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 17 Aug 2026 · Probed https://mcp.supplyslate.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=supplyslate.com	CN=WE1,O=Google Trust Services,C=US	6 Aug 2026	4 Nov 2026	ECDSA 256	ECDSA-SHA256	6cf50b171c37eaba13152fc521393ff3
SANs: supplyslate.com, mcp.supplyslate.com, *.mcp.supplyslate.com
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of mcp.supplyslate.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
supplyslate.com.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=31536000
content-security-policy	default-src 'none'; frame-ancestors 'none'
x-content-type-options	nosniff
x-frame-options	DENY
referrer-policy	no-referrer
permissions-policy	camera=(), microphone=(), geolocation=(), payment=()

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.supplyslate.com/mcp	Verified	200
http (plaintext)	http://mcp.supplyslate.com/mcp	Inconclusive	405

MCP tools · 55 exposed · ~3,694 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

ask_rfq_clarification ~46

Ask the buyer a clarification question on an approved supplier RFQ without changing the immutable request package.

Input Output Examples

Name	Type	Req	Description
match_id	string	yes	–
question	string	yes	–

Name	Type	Req	Description
clarification	object	yes	–

No examples provided.

attach_artifact_reference ~116

Attach an HTTPS repository, document, drawing, datasheet, BOM, or design reference to the current project revision without copying its bytes. Private or expiring URLs remain the buyer's responsibility until uploaded directly.

Input Output Examples

Name	Type	Req	Description
artifact_type	string	yes	–
checksum_sha256	string	–	–
data_classification	string	yes	–
media_type	string	–	–
original_filename	string	–	–
project_id	string	yes	–
purpose	string	yes	–
source_url	string	yes	–

Name	Type	Req	Description
artifact	object	yes	–

No examples provided.

create_artifact_upload ~102

Create a short-lived, one-time private artifact upload URL. The caller must stream the exact declared bytes with a SHA-256 checksum.

Input Output Examples

Name	Type	Req	Description
artifact_type	string	yes	–
checksum_sha256	string	yes	–
data_classification	string	yes	–
media_type	string	yes	–
original_filename	string	yes	–
project_id	string	yes	–
purpose	string	yes	–
size_bytes	integer	yes	–

Name	Type	Req	Description
artifact	object	yes	–
upload	object	–	–

No examples provided.

create_catalog_import ~98

Create a durable CSV, XLSX, JSON, feed, API, document, or manual catalog import. Supply parsed rows for immediate validation, or an artifact/source reference to enter the mapping workflow.

Input Output Examples

Name	Type	Req	Description
idempotency_key	string	yes	–
mapping	object	–	–
rows	array	–	–
source_artifact_id	string	–	–
source_type	string	yes	–
source_url	string	–	–

Name	Type	Req	Description
catalog_import	object	–	–
import	object	–	–

No examples provided.

create_project ~178

Create a durable supply project from an idea, file, BOM, exact part, or RFQ origin. Requires a scoped buyer credential.

Input Output Examples

Name	Type	Req	Description
brief	string	yes	–
budget_currency	string	–	–
budget_minor	integer	–	–
build_quantity	number	–	–
data_classification	string	–	–
demand_lane	string	yes	–
external_id	string	–	–
fixture_kind	string	–	Explicit lineage for integration fixtures; never use synthetic records as market evidence.
name	string	yes	–
need_by	string	–	–
origin_type	string	yes	–
project_type	string	yes	–
requirements	array	–	–
ship_to_country	string	–	–
ship_to_postal_code	string	–	–
substitution_policy	string	–	–

Name	Type	Req	Description
project	object	yes	–

No examples provided.

create_provider_checkout_handoff ~157

After a human has approved the exact purchase plan, create one supplier-hosted payment link for a checkout-connected provider offer. This creates an unpaid provider order but never submits payment or exposes payment credentials to SupplySlate.

Input Output Examples

Name	Type	Req	Description
contact	object	–	Optional. Omit to let the provider-hosted page collect contact details from the human.
merchant_group_key	string	yes	–
purchase_plan_id	string	yes	–
return_url	string	–	–
ship_to	object	–	Optional. Omit to let the provider-hosted page collect the shipping address from the human.
shipping_option_id	string	–	Exact approved shipping option. Omit to use the least-cost option already priced into the approved plan.

Name	Type	Req	Description
checkout_handoff	object	yes	–
idempotent_replay	boolean	–	–
merchant_of_record	string	yes	–
payment_boundary	string	yes	–

No examples provided.

create_purchase_plan ~86

Create an immutable, single-currency, multi-supplier purchase plan from selected current quote lines, choosing at most one commercial option per requested line. This records a plan only; it neither approves nor purchases anything.

Input Output Examples

Name	Type	Req	Description
expires_at	string	–	–
idempotency_key	string	yes	–
quote_item_ids	array	yes	–
request_id	string	yes	–

Name	Type	Req	Description
idempotent_replay	boolean	–	–
purchase_plan	object	yes	–

No examples provided.

decide_supplier_order_cancellation ~76

Accept or reject a buyer cancellation request for the authenticated supplier's unshipped merchant order. Acceptance is the state-changing merchant decision.

Input Output Examples

Name	Type	Req	Description
cancellation_request_id	string	yes	–
decision	string	yes	–
merchant_reference	string	–	–
note	string	–	–
order_id	string	yes	–

Name	Type	Req	Description
order	object	yes	–

No examples provided.

decline_supplier_rfq ~53

Decline an approved RFQ with a structured reason so the buyer and network can route more accurately.

Input Output Examples

Name	Type	Req	Description
match_id	string	yes	–
reason	string	yes	–
reason_code	string	yes	–

Name	Type	Req	Description
decline	object	–	–
sourcing_request	object	–	–

No examples provided.

describe_supplyslate ~32

Explain what SupplySlate does, what it does not do, and when a buyer-owned agent should use it.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
access	string	yes	–
boundaries	array	yes	–
mcp_endpoint	string	yes	–
openapi	string	yes	–
purpose	string	yes	–
rest_api	string	yes	–
service	string	yes	–
supplier_directory	string	yes	–
use_when	array	yes	–

No examples provided.

get_bom ~46

Read the current revision of one project BOM, including hierarchy, quantities, sourcing state, and interface dependencies.

Input Output Examples

Name	Type	Req	Description
bom_id	string	yes	–
project_id	string	yes	–

Name	Type	Req	Description
bom	object	yes	–

No examples provided.

get_checkout_handoffs ~52

List merchant-hosted checkout, supplier invoice, or merchant-order handoffs for an approved plan. Suppliers remain merchant of record and SupplySlate does not process funds.

Input Output Examples

Name	Type	Req	Description
purchase_plan_id	string	yes	–

Name	Type	Req	Description
data	array	yes	–
merchant_of_record	string	yes	–
purchase_plan_id	string	yes	–

No examples provided.

get_compatibility ~42

Read one published compatibility or substitution assertion with exact subject, object, conditions, confidence, evidence source, and observation time.

Input Output Examples

Name	Type	Req	Description
compatibility_id	string	yes	–

Name	Type	Req	Description
compatibility	object	–	–
data	object	–	–

No examples provided.

get_connection_guide ~52

Return the exact MCP and REST connection details a buyer, developer, or agent operator needs to connect to SupplySlate.

Input Output Examples

Name	Type	Req	Description
client	string	–	The agent client or integration style that will connect to SupplySlate.

Name	Type	Req	Description
client	string	yes	–
first_action	string	yes	–
mcp	object	yes	–
obtain_access	string	yes	–
rest	object	yes	–

No examples provided.

get_live_fabrication_capabilities ~39

Read attributed live fabrication capabilities from the connected AFN provider. This is discovery only and neither uploads a design nor requests a quote.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
attribution	string	yes	–
capabilities	–	yes	–
commercial_boundary	string	yes	–
observed_at	string	yes	–
provider	string	yes	–
source_url	string	yes	–

No examples provided.

get_order ~37

Read one merchant-confirmed order with items, fulfillment, shipments, issues, evidence, and event history.

Input Output Examples

Name	Type	Req	Description
order_id	string	yes	–

Name	Type	Req	Description
order	object	yes	–

No examples provided.

get_product ~36

Read one published canonical product with variants, category links, evidence scope, observation dates, and freshness.

Input Output Examples

Name	Type	Req	Description
product_id	string	yes	–

Name	Type	Req	Description
data	object	–	–
product	object	–	–

No examples provided.

get_project ~38

Read a project, its current immutable-capable revision, requirements, artifacts, BOM summaries, and validation history.

Input Output Examples

Name	Type	Req	Description
project_id	string	yes	–

Name	Type	Req	Description
project	object	yes	–

No examples provided.

get_purchase_plan ~43

Read one exact purchase-plan version with selected lines, merchants, totals, risks, evidence, approvals, and checkout handoffs.

Input Output Examples

Name	Type	Req	Description
purchase_plan_id	string	yes	–

Name	Type	Req	Description
purchase_plan	object	yes	–

No examples provided.

get_requirement_schema ~75

Read the evidence-safe input schema for a configurable supply category or fabrication process, including required fields, recommended fields, accepted artifacts, and safety notes.

Input Output Examples

Name	Type	Req	Description
identifier	string	yes	Category code, fabrication-process slug, or fabrication-process ID.
type	string	–	Optional disambiguation when an identifier could exist in both namespaces.

Name	Type	Req	Description
category	–	–	–
data	object	–	–
process	–	–	–

No examples provided.

get_sourcing_request ~33

Read the current status and normalized line items for one authenticated buyer sourcing request.

Input Output Examples

Name	Type	Req	Description
request_id	string	yes	–

Name	Type	Req	Description
sourcing_request	object	yes	–

No examples provided.

get_supplier ~36

Read one public supplier profile with source URLs and evidence for every category, capability, and brand claim.

Input Output Examples

Name	Type	Req	Description
supplier_id	string	yes	–

Name	Type	Req	Description
data	object	–	–
supplier	object	–	–

No examples provided.

get_supplier_offers ~62

Retrieve current normalized supplier quote revisions for one buyer sourcing request, including unquoted lines, compatibility, price, availability, lead time, terms, and evidence. SupplySlate returns explicit tradeoffs and applies no hidden winner score.

Input Output Examples

Name	Type	Req	Description
request_id	string	yes	–

Name	Type	Req	Description
offers	array	yes	–
unquoted_items	array	–	–

No examples provided.

get_supplier_profile ~29

Read the authenticated supplier's SupplySlate profile and current catalog-item count. Requires a supplier API key.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
profile	object	–	–
supplier	object	–	–

No examples provided.

get_supplier_rfq ~36

Read an approved RFQ and its normalized buyer line items. Requires a supplier API key.

Input Output Examples

Name	Type	Req	Description
match_id	string	yes	–

Name	Type	Req	Description
rfq	object	–	–
sourcing_request	object	–	–

No examples provided.

list_fabrication_processes ~32

List configurable fabrication, kitting, assembly, and test processes with their required artifacts and requirement schemas.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
data	array	yes	–

No examples provided.

list_orders ~31

List merchant-confirmed orders for the buyer organization. A plan or queued handoff is never represented as an order.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
data	array	yes	–
summary	object	yes	–

No examples provided.

list_project_validations ~32

List versioned validation reports for a project without implying licensed engineering approval.

Input Output Examples

Name	Type	Req	Description
project_id	string	yes	–

Name	Type	Req	Description
data	array	yes	–

No examples provided.

list_sourcing_categories ~30

List the editable supply categories currently accepting requests. Agents may still submit a precise request outside this list.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
data	array	yes	–

No examples provided.

list_sourcing_requests ~34

List recent sourcing requests owned by the authenticated buyer organization across API keys and OAuth agents.

Input Output Examples

Name	Type	Req	Description
limit	integer	–	–

Name	Type	Req	Description
data	array	yes	–
summary	object	yes	–

No examples provided.

list_supplier_orders ~37

List merchant-confirmed orders attributable to the authenticated supplier. RFQs, quotes, plans, and checkout handoffs are not represented as orders.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
data	array	yes	–
summary	object	yes	–

No examples provided.

list_supplier_rfqs ~33

List approved RFQs matched to the authenticated supplier. Requires a supplier API key.

Input Output Examples

Name	Type	Req	Description
limit	integer	–	–

Name	Type	Req	Description
data	array	yes	–
summary	object	yes	–

No examples provided.

list_supplier_taxonomy ~31

List the product categories used by the public industrial compressor service-parts supplier directory, including verified supplier counts.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
data	array	yes	–

No examples provided.

open_warranty_claim ~63

Open a durable warranty claim on an accepted order or specific order line. This records the claim and notifies the supplier without asserting eligibility or approval.

Input Output Examples

Name	Type	Req	Description
description	string	yes	–
order_id	string	yes	–
order_item_id	string	–	–

Name	Type	Req	Description
order	object	yes	–

No examples provided.

report_order_issue ~87

Open a durable post-purchase issue for a merchant-confirmed order. This notifies the supplier-side organization and records owner, status, and event history; it does not claim a resolution.

Input Output Examples

Name	Type	Req	Description
issue_type	string	yes	–
order_id	string	yes	–
order_item_id	string	–	–
owner_type	string	–	–
summary	string	yes	–

Name	Type	Req	Description
order	object	yes	–

No examples provided.

request_order_cancellation ~59

Ask the merchant to cancel an unshipped order. This creates a request and notification; it never reports the order as cancelled until the supplier or an operator accepts it.

Input Output Examples

Name	Type	Req	Description
order_id	string	yes	–
reason	string	yes	–

Name	Type	Req	Description
order	object	yes	–

No examples provided.

request_order_return ~51

Open a return request after shipment. The supplier remains merchant of record and controls authorization and refund state.

Input Output Examples

Name	Type	Req	Description
items	array	–	–
order_id	string	yes	–
reason	string	yes	–

Name	Type	Req	Description
order	object	yes	–

No examples provided.

request_purchase_approval ~62

Create a human review link bound to the exact purchase-plan version, suppliers, maximum amount, currency, risks, and expiry. This does not approve or purchase the plan.

Input Output Examples

Name	Type	Req	Description
expires_in_minutes	integer	–	–
purchase_plan_id	string	yes	–

Name	Type	Req	Description
approval	object	yes	–

No examples provided.

revise_supplier_quote ~132

Create a new immutable revision of a supplier quote. The previous revision remains in history and the new revision becomes current.

Input Output Examples

Name	Type	Req	Description
currency	string	yes	–
delivery_terms	string	–	–
fees_minor	integer	–	–
items	array	yes	–
match_id	string	yes	–
notes	string	–	–
payment_terms	string	–	–
quote_id	string	yes	–
quote_number	string	–	–
shipping_minor	integer	–	–
tax_minor	integer	–	–
valid_until	string	–	–
warranty	string	–	–

Name	Type	Req	Description
quote	object	yes	–

No examples provided.

search_live_components ~75

Search attributed current electronic-component product, availability, lead-time, and price data from Mouser. Results retain provider, observation time, and merchant URLs; no checkout or order is created.

Input Output Examples

Name	Type	Req	Description
limit	integer	–	–
manufacturer	string	–	–
query	string	yes	–
search_type	string	–	–

Name	Type	Req	Description
attribution	string	yes	–
cached	boolean	yes	–
count	integer	yes	–
data	array	yes	–
provider	string	yes	–

No examples provided.

search_products ~62

Search published canonical product facts. Commercial price, stock, compatibility, and lead time are returned only when separately supported by current evidence.

Input Output Examples

Name	Type	Req	Description
category	string	–	–
limit	integer	–	–
manufacturer	string	–	–
q	string	–	–

Name	Type	Req	Description
data	array	yes	–

No examples provided.

search_suppliers ~157

Search source-backed public supplier profiles by product category, brand, company type, service, compressor type, industry, or text. No authentication required.

Input Output Examples

Name	Type	Req	Description
brand	string	–	Exact publicly listed brand, such as Atlas Copco.
category	string	–	Exact category code from list_supplier_taxonomy.
company_type	string	–	–
compressor_type	string	–	–
country	string	–	Two-letter country code. Defaults to US; use all only when broader coverage is intentional.
industry	string	–	–
limit	integer	–	–
offset	integer	–	–
q	string	–	Text contained in a supplier name, summary, or listed brand.
service	string	–	–

Name	Type	Req	Description
count	integer	–	–
data	array	yes	–
total	integer	–	–

No examples provided.

source_project ~163

Lock the validated project revision into an immutable sourcing package, create normalized request lines, and return transparent supplier candidates. This does not contact suppliers; a human operator must approve every outbound recipient, message, and artifact scope.

Input Output Examples

Name	Type	Req	Description
artifact_ids	array	–	–
category	string	yes	–
data_classification	string	–	–
external_id	string	–	Buyer-controlled idempotency key.
items	array	–	Optional fast exact-part or RFQ lines. Omit to source the current BOM.
need_by	string	–	–
notes	string	–	–
project_id	string	yes	–
ship_to_country	string	–	–
ship_to_postal_code	string	–	–
substitutions_allowed	boolean	–	–

Name	Type	Req	Description
sourcing_request	object	yes	–

No examples provided.

submit_sourcing_request ~179

Submit a real non-sensitive B2B sourcing request on behalf of the buyer. SupplySlate routes it to relevant suppliers and returns structured offers later. Requires a buyer API key.

Input Output Examples

Name	Type	Req	Description
category	string	yes	Supply category. Use a precise category even if it is not in the current category list.
data_classification	string	–	–
external_id	string	–	Buyer-controlled idempotency key for this request.
fixture_kind	string	–	Explicit lineage for integration fixtures; never use synthetic records as market evidence.
items	array	yes	–
need_by	string	–	Requested delivery date in YYYY-MM-DD format.
notes	string	–	–
ship_to_country	string	yes	Two-letter ISO country code.
ship_to_postal_code	string	–	–
substitutions_allowed	boolean	–	–

Name	Type	Req	Description
sourcing_request	object	yes	–

No examples provided.

submit_supplier_quote ~133

Submit the first structured commercial quote for a human-approved RFQ. Money is integer minor units with an explicit currency; partial line coverage and labeled alternatives are allowed.

Input Output Examples

Name	Type	Req	Description
currency	string	yes	–
delivery_terms	string	–	–
fees_minor	integer	–	–
items	array	yes	–
match_id	string	yes	–
notes	string	–	–
payment_terms	string	–	–
quote_number	string	–	–
shipping_minor	integer	–	–
tax_minor	integer	–	–
valid_until	string	–	–
warranty	string	–	–

Name	Type	Req	Description
quote	object	yes	–

No examples provided.

update_availability ~35

Append timestamped supplier availability evidence and update current catalog state by supplier SKU without rewriting historical snapshots.

Input Output Examples

Name	Type	Req	Description
items	array	yes	–

Name	Type	Req	Description
data	array	–	–
updated_count	integer	–	–

No examples provided.

update_project_requirements ~48

Replace the structured requirement set on an unlocked project revision. Confirmed flags distinguish buyer-confirmed facts from agent interpretation.

Input Output Examples

Name	Type	Req	Description
project_id	string	yes	–
requirements	array	yes	–

Name	Type	Req	Description
project	object	yes	–

No examples provided.

update_supplier_capabilities ~40

Replace the supplier-submitted capability set while preserving separately sourced public, operator-verified, and transaction-proven evidence.

Input Output Examples

Name	Type	Req	Description
capabilities	array	yes	–

Name	Type	Req	Description
capabilities	array	–	–
data	array	–	–

No examples provided.

update_supplier_order ~68

Acknowledge or update fulfillment on a merchant-confirmed supplier order, optionally recording a shipment. State transitions and order-item quantities are validated and audited.

Input Output Examples

Name	Type	Req	Description
note	string	–	–
order_id	string	yes	–
shipment	object	–	–
status	string	yes	–

Name	Type	Req	Description
order	object	yes	–

No examples provided.

update_supplier_order_issue ~69

Update ownership, status, or resolution for a buyer-reported issue on the authenticated supplier's merchant order.

Input Output Examples

Name	Type	Req	Description
issue_id	string	yes	–
order_id	string	yes	–
owner_type	string	–	–
resolution	string	–	–
status	string	yes	–

Name	Type	Req	Description
order	object	yes	–

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

6 Aug 17 Aug

Day	Score
6 Aug	55
7 Aug	55
8 Aug	54
9 Aug	59
10 Aug	62
11 Aug	68
12 Aug	68
13 Aug	68
14 Aug	69
15 Aug	70
16 Aug	70
17 Aug	71