Agent-native tools
https://mcp.supplyslate.com/mcp- Transport
- Streamable HTTP
- Discovery
- Public
- Requests
- Buyer key
Connect the AI or purchasing system you already operate. It can submit real sourcing requests and receive normalized, verifiable supplier offers without sending a person through another portal.
Use MCP when your agent platform supports remote tools. Use the REST API when you own the orchestration layer. Both interfaces operate on the same durable sourcing-request and offer records.
https://mcp.supplyslate.com/mcphttps://api.supplyslate.comAdd the remote MCP URL to your agent’s tool configuration. Include the buyer key only when the agent is ready to submit and read commercial requests.
{
"mcpServers": {
"supplyslate": {
"url": "https://mcp.supplyslate.com/mcp",
"headers": {
"Authorization": "Bearer <SUPPLYSLATE_API_KEY>"
}
}
}
}describe_supplyslatePublicKnow when to use the network and what commercial boundaries apply.
list_sourcing_categoriesPublicRead the editable categories currently accepting sourcing requests.
get_connection_guidePublicRetrieve exact MCP, REST, authentication, and first-call instructions.
submit_sourcing_requestBuyer keySend a real requirement with destination, constraints, and line items.
list_sourcing_requestsBuyer keyList the authenticated buyer’s recent requests.
get_sourcing_requestBuyer keyRead request state and normalized line-item data.
get_supplier_offersBuyer keyRetrieve comparable supplier offers with evidence and commercial terms.
The buyer’s own agent sends specifications, quantity, destination, timing, and substitution policy.
SupplySlate carries the request into relevant supplier catalog and quoting workflows.
Structured offers return with compatibility, price, stock, delivery, terms, and evidence.
Tell us the buyer organization, the agent or purchasing system you operate, and the first categories you expect to source. We issue a separate credential for every participant.
Request buyer access ↗