Science Exchange
Science Exchange is an R&D supplier orchestration and procurement platform for life-sciences organizations. It runs a marketplace of 3,800+ pre-qualified scientific service providers under a single master service agreement, and streamlines supplier sourcing, onboarding, contracting, compliance, and payment. The platform integrates with ERP (SAP, Oracle, Workday), P2P (Ariba, Coupa), and SSO/SAML identity systems, and exposes a read-only Providers REST API (v1) that lets scientific-service suppliers pull their RFQs, quotes, services, facilities, line items, ratings, tags, and users. Founded in 2011 and headquartered in Palo Alto, California; backed by a16z, Index Ventures, and Union Square Ventures.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Science Exchange the way a machine reads it — 27 machine-readable artifacts across 23 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Science Exchange scores 49.8/100 (developing), with a separate agent-readiness read of 55/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Science Exchange
Each block below is one kind of artifact we hold for Science Exchange. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 23
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Science Exchange addresses API
Addresses resource.
Science Exchange attachments API
Attachments resource.
Science Exchange currency_codes API
CurrencyCodes resource.
Science Exchange experiment_type_fields API
ExperimentTypeFields resource.
Science Exchange experiment_types API
ExperimentTypes resource.
Science Exchange facilities API
Facilities resource.
Science Exchange facility_members API
FacilityMembers resource.
Science Exchange facility_photos API
FacilityPhotos resource.
Science Exchange groups API
Groups resource.
Science Exchange line_items API
LineItems resource.
Science Exchange pricing_units API
PricingUnits resource.
Science Exchange quote_versions API
QuoteVersions resource.
Science Exchange quotes API
Quotes resource.
Science Exchange ratings API
Ratings resource.
Science Exchange rfq_collaborators API
RFQCollaborators resource.
Science Exchange rfq_events API
RFQEvents resource.
Science Exchange rfq_fields API
RFQFields resource.
Science Exchange rfq_messages API
RFQMessages resource.
Science Exchange rfqs API
RFQs resource.
Science Exchange services API
Services resource.
Science Exchange tag_contexts API
TagContexts resource.
Science Exchange tags API
Tags resource.
Science Exchange users API
Users resource.
Scroll within the panel for all 23 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
science-exchange-mcp.yml
MCP SERVERSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Science Exchange — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/science-exchange · machine-readable index on apis.io