SIB SCIA conversation starts here

Equipment and research data.
Enquire through your agent.

SIB Scientific buys and sells used laboratory equipment, supplies new Bruker Optics instruments, and sources and licenses research data for AI model development and scientific research. Based in Austin, Texas. Operating since 2011.

Send an enquiry, upload seller photos and continue privately with our team. You need a reply email address, not access to the customer’s mailbox. No account is needed to start.

Selling equipment to SIB SCI

  1. Ask the seller for their name, reply email and equipment details. Include the model, location, quantity, condition and included items when known. Unknown details can remain unknown.
  2. Obtain authorization to contact SIB SCI and share the supplied details and photos.
  3. Create an enquiry with intent: "sell". A catalogue match or instrument ID is not required. Do not select a similar inventory item as a substitute.
  4. Upload authorized photos to the private conversation. Save the reference and private access securely.
  5. Read the team’s response and continue in the same conversation. An acknowledgement means the enquiry was recorded, not that SIB SCI has agreed to buy it.
POST https://sibsci.com/api/v1/enquiries
Content-Type: application/json

{
  "intent": "sell",
  "name": "Seller name",
  "email": "seller@example.org",
  "requirements": "We are offering a Thermo Q Exactive HF in Austin. Condition is unknown. Please review for purchase.",
  "expected_photos": 2,
  "consent": true,
  "idempotency_key": "a-fresh-random-uuid-for-this-enquiry"
}

Set expected_photos to the number you intend to upload. Use zero if none are available. Photos can be added later.

Buying equipment from SIB SCI

Search the current inventory by model, category or application. Supply matching stable string instrument IDs when useful. You can also enquire about equipment that is not listed.

GET https://sibsci.com/api/v1/inventory?query=mass%20spectrometer
GET https://sibsci.com/api/v1/inventory?id=02

Create an enquiry with intent: "buy", the customer’s name, reply email, requirements, consent: true and a fresh idempotency_key. Instrument IDs, company, destination, timeframe and budget are optional. Listing prices are asking prices. Availability, condition and included items require team confirmation.

Choose a connection

Your agent can useHow to proceed
Website formsOpen Contact SIB SCI, choose Buy equipment or Sell equipment, complete the short form and submit with the customer’s authorization. Keep the receipt to read and send follow ups.
Browser site toolsCompatible browsers discover sibsci_ tools on this page and the homepage. They use the same enquiry and photo service. Private access remains in the current tab. Use sibsci_current_conversations to find its accessible references. Browser and account support varies.
Remote MCPConnect your client to https://sibsci.com/mcp. Use Streamable HTTP with stateless JSON responses. Legacy SSE is not supported. The client must support and connect to MCP; visiting this URL alone does not establish a connection.
HTTP requestsUse the OpenAPI specification. Public inventory and creating an enquiry need no API key. Follow ups and attachments require that enquiry’s private bearer token.
Search onlyRead the inventory and contact details, then prepare a message for the customer. Do not claim to have sent it if your tools cannot submit forms or HTTP requests.
MCP tools
search_inventory
create_enquiry
get_deal
add_deal_message
list_deal_photos
begin_photo_upload
upload_photo_chunk
finish_photo_upload
complete_photo_uploads
get_photo_chunk

Use tools/list for current input definitions. Site tools use the same names with a sibsci_ prefix and hold access tokens within the browser tab. Remote MCP tools require deal_id and access_token for private operations.

Private seller photos

Up to 20 photos, 25 MiB each and 250 MiB total. JPEG, PNG, WebP, GIF and HEIC/HEIF are supported. Only send photos the seller authorizes. They become private enquiry attachments, not public catalogue images.

  1. Create the seller enquiry, then use begin_photo_upload with its access, filename, byte size and SHA256. The response identifies the photo and received byte offset. Repeating the same hash resumes the upload.
  2. Send upload_photo_chunk with photo_id, offset and data_base64. Each decoded chunk must be at most 262144 bytes. Continue from received_bytes.
  3. Call finish_photo_upload to verify the complete file. Then call complete_photo_uploads with all ready photo_ids so our team knows the set is ready.
  4. Use list_deal_photos to confirm saved attachments. Use get_photo_chunk for authorized private readback and integrity checks. Never infer a successful upload from a filename alone.

The REST alternative starts at POST /api/v1/deals/{deal_id}/photos with name, size and sha256. Send binary chunks of up to 1 MiB to /photos/{photo_id}/chunks?offset=N, then call /photos/{photo_id}/finish and /photos/complete. All paths and response schemas are in OpenAPI.

Continue the same conversation

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":"The seller confirmed one instrument is available. Photos are attached."}

Remote API and MCP clients must save the returned token privately. Never place it in URLs, public documents or logs. The browser receipt offers a private access file to save and restore the conversation after closing a tab. Anyone with that file can access the conversation. Browser access is kept in session storage, with a 24 hour local expiry, rather than indefinite local storage.

The visible browser receipt checks for replies while the tab is active. API agents can check periodically, starting at 60 seconds and increasing to five minutes when unchanged. Respect any Retry-After response. Do not promise continuing checks unless your environment will actually run them.

For a failed creation request, retry the same payload with the same idempotency key. For other interrupted writes, first read the conversation or upload status to confirm what arrived before retrying. Do not create a second enquiry for the same request.

Team review

Website, API and MCP enquiries share one private deal inbox. Receipt confirmations are automatic and confirm that we received the enquiry and will get in touch. Substantive team replies and commercial decisions require human approval. These tools do not reserve equipment, accept payment, agree a price or commit either party.

Emails sent to inquiry@sibsci.com enter our private review queue. Our team checks the sender and attaches the message to the appropriate enquiry. Continue through the private API or website conversation for direct updates to the same record.

inquiry@sibsci.com · 888 840 1793 · Privacy

Bruker instruments and research data

The same private enquiry API and MCP connection also accept requests for new Bruker instruments and scientific data sourcing or licensing.

Requests reach the shared SIB SCI inbox. Product availability, regional representation, dataset access rights and commercial terms require team review. This service guide is not an inventory of datasets available to buy.