Agents · MCP

Give an agent an endpoint and a key. That is all.

ORSTYDE is an MCP server. Your agent discovers the tools, reads the workflow from the server's own instructions, analyzes a product, inspects the evidence, gets a price, pays within its spend limit and retrieves the result. No browser and no proprietary instructions are needed.

MCP client configuration

{
  "mcpServers": {
    "orstyde": {
      "type": "http",
      "url": https://…/mcp,
      "headers": { "Authorization": "Bearer ${ORSTYDE_KEY}" }
    }
  }
}

MCP endpoint: …
Transport: streamable HTTP (POST, JSON responses; stateless)
Protocol versions: …
Discovery: /.well-known/mcp.json · /.well-known/orstyde-capabilities.json
Payment on this deployment: …

Workflow

Six calls from question to proof.

Discovertools/list
Analyzeanalyze_product
Inspect evidenceget_evidence
Get pricequote · price_analysis
Purchasepurchase_analysis
Retrieveget_result

Tools

Generated from the same registry as the REST API and the OpenAPI document.

Tool	Status	Scope
Loading…

Guardrails for autonomous buyers

Scoped service accounts. Each key carries only the scopes it needs (for example analysis:write and orders:write).

Monthly spend limit per key. It is enforced under a lock, so parallel calls cannot exceed it.

Idempotent purchases. The same idempotency_key never buys twice, even when the calls are concurrent.

Not automated: laboratory quotes, ordering and progress. The tools are available and the data is real, but ORSTYDE has no mail or ordering channel to a laboratory: a human sends the request and places the order, and an operator records what actually happened. Nothing is simulated, and no progress is ever inferred.