Science has questions.
Your agent can ask.

Read every listed instrument. Send a structured enquiry. Keep the requirements and replies in one private deal record, reviewed by the SIB SCI team.

Inventory + enquiry API + MCP available

Start with the inventory.

Our current catalogue is available without a login. Each includes a stable reference, category, asking price snapshot, description and monochrome equipment image.

Download inventory JSON Read inventory API OpenAPI specification Plain text agent guide

GET https://sibsci.com/api/v1/inventory
GET https://sibsci.com/api/v1/inventory?query=ZenoTOF
GET https://sibsci.com/api/v1/inventory?id=02

Prices reflect the October 5, 2026 catalogue snapshot. Availability, condition, included components and commercial terms require team confirmation. Equipment images are illustrative.

Connect through MCP.

Server URL: https://sibsci.com/mcp
Transport: Streamable HTTP (stateless JSON responses)
Tools: search_inventory, create_enquiry, get_deal, add_deal_message

Public search does not require authentication. A new enquiry returns a secret token scoped to that single deal. Keep it private and use it for subsequent reads and messages. This endpoint does not support legacy SSE clients.

A conversation, with its context intact.

Discover: search models and applications; use stable instrument IDs.
Ask: obtain the buyer’s permission, then send their enquiry and contact details.
Keep the reference: save the deal ID and private access token from the response.
Continue: add requirements or questions to the same deal. The team is notified.
Read the reply: poll the private deal at a reasonable interval. Intake messages are automated; team messages are labelled separately.

POST https://sibsci.com/api/v1/enquiries
Content-Type: application/json

{
  "name": "Buyer name",
  "email": "buyer@example.org",
  "company": "Laboratory name",
  "instrument_ids": ["02"],
  "requirements": "Please confirm configuration and condition evidence.",
  "destination": "Austin, Texas, USA",
  "timeframe": "This quarter",
  "budget": "To be discussed",
  "consent": true,
  "idempotency_key": "a-fresh-random-uuid-for-this-enquiry"
}

On a network retry, reuse the exact same key and payload to recover the same deal. A 429 response includes a retry interval. Never put the returned access token in a public URL, document or log.

GET /api/v1/deals/{deal_id}
Authorization: Bearer {access_token}

POST /api/v1/deals/{deal_id}/messages
Authorization: Bearer {access_token}
Content-Type: application/json

{"message":"Please include the available software and licence details."}

Clear capabilities. Clear limits.

This service records enquiries, asks for missing brief details, notifies our team, and supports private follow up. It does not independently confirm stock, issue binding quotations, reserve equipment, accept payment or commit either party to a deal.

Website and API messages share the deal inbox. Email notifications reach our team; ordinary mailbox replies are not yet imported into the deal record automatically.

Talk to a person · Privacy notice

Selling equipment? Include photos.

Create an enquiry with intent: "sell", then use its private deal token to upload photos through the REST API. Up to 20 photos, 25 MB each and 250 MB total. JPG, PNG, WebP, GIF and HEIC are accepted. Obtain the seller’s authorization before sending their photos.

Start a photo at POST /api/v1/deals/{deal_id}/photos with its filename, byte size and SHA-256.
Send original bytes in chunks of at most 1 MiB to /{photo_id}/chunks?offset={received_bytes}. Reuse the same hash to resume.
Call /{photo_id}/finish to verify receipt, then /complete with the ready photo_ids to notify our team.