TetraScience
TetraScience is the scientific data and AI platform company behind the Tetra Scientific Data and AI Cloud — purpose-built infrastructure that liberates, replatforms, and engineers raw lab data from instruments, informatics systems, and partner organizations into FAIR, AI-native Tetra Data. The platform combines lab data automation (agents and integrations for hundreds of instruments and applications), a vendor- agnostic data lake, an Intermediate Data Schema (IDS) layer, pipelines for data engineering, GxP-aligned compliance, and the Tetra AI Layer with Tetra Sciborgs (scientific AI agents) to accelerate discovery, development, manufacturing, and quality outcomes for pharma, biotech, CROs, and CDMOs.
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 TetraScience the way a machine reads it — 116 machine-readable artifacts across 2 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 — TetraScience scores 54.2/100 (developing), with a separate agent-readiness read of 22/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from TetraScience's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tetrascience/"
title="TetraScience on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tetrascience.svg"
alt="TetraScience Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/tetrascience/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tetrascience/"
title="TetraScience on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tetrascience/card.svg"
alt="TetraScience Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile TetraScience
Each block below is one kind of artifact we hold for TetraScience. 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 35
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.
TetraScience Access Groups API
The Access Groups API from TetraScience — 6 operation(s) for access groups.
TetraScience Agents API
The Agents API from TetraScience — 8 operation(s) for agents.
TetraScience ai-workflows API
The ai-workflows API from TetraScience — 8 operation(s) for ai-workflows.
TetraScience Attributes API
The Attributes API from TetraScience — 2 operation(s) for attributes.
TetraScience Audit Trail API
The Audit Trail API from TetraScience — 1 operation(s) for audit trail.
TetraScience clusters API
The clusters API from TetraScience — 2 operation(s) for clusters.
TetraScience Commands API
The Commands API from TetraScience — 4 operation(s) for commands.
TetraScience Connectors API
The Connectors API from TetraScience — 23 operation(s) for connectors.
TetraScience Data Acquisition API
The Data Acquisition API from TetraScience — 6 operation(s) for data acquisition.
TetraScience Data App Providers API
The Data App Providers API from TetraScience — 3 operation(s) for data app providers.
TetraScience Data Apps API
The Data Apps API from TetraScience — 12 operation(s) for data apps.
TetraScience databricks API
The databricks API from TetraScience — 2 operation(s) for databricks.
TetraScience Edit Subscriptions API
The Edit Subscriptions API from TetraScience — 4 operation(s) for edit subscriptions.
TetraScience Embedded Data Apps API
The Embedded Data Apps API from TetraScience — 1 operation(s) for embedded data apps.
TetraScience Files API
The Files API from TetraScience — 5 operation(s) for files.
TetraScience Hubs API
The Hubs API from TetraScience — 2 operation(s) for hubs.
TetraScience IDS API
The IDS API from TetraScience — 8 operation(s) for ids.
TetraScience lakehouse API
The lakehouse API from TetraScience — 8 operation(s) for lakehouse.
TetraScience Linked Data Apps API
The Linked Data Apps API from TetraScience — 2 operation(s) for linked data apps.
TetraScience Login API
The Login API from TetraScience — 7 operation(s) for login.
TetraScience Logs API
The Logs API from TetraScience — 1 operation(s) for logs.
TetraScience Organizations API
The Organizations API from TetraScience — 3 operation(s) for organizations.
TetraScience Pipelines API
The Pipelines API from TetraScience — 17 operation(s) for pipelines.
TetraScience Protocols API
The Protocols API from TetraScience — 11 operation(s) for protocols.
TetraScience Requests API
The Requests API from TetraScience — 5 operation(s) for requests.
TetraScience Roles API
The Roles API from TetraScience — 5 operation(s) for roles.
TetraScience Schemas API
The Schemas API from TetraScience — 9 operation(s) for schemas.
TetraScience Search API
The Search API from TetraScience — 2 operation(s) for search.
TetraScience Task Scripts API
The Task Scripts API from TetraScience — 8 operation(s) for task scripts.
TetraScience Tenants API
The Tenants API from TetraScience — 4 operation(s) for tenants.
TetraScience tetraflows API
The tetraflows API from TetraScience — 8 operation(s) for tetraflows.
TetraScience tetraspheres API
The tetraspheres API from TetraScience — 8 operation(s) for tetraspheres.
TetraScience Users API
The Users API from TetraScience — 10 operation(s) for users.
TetraScience View Subscriptions API
The View Subscriptions API from TetraScience — 2 operation(s) for view subscriptions.
TetraScience Workflows API
The Workflows API from TetraScience — 5 operation(s) for workflows.
Scroll within the panel for all 35 ·
Postman Collections 35
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Scroll within the panel for all 35 ·
Open Collections 37
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Agents API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Attributes API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Audit Trail API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups clusters API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Commands API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Connectors API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Data Apps API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups databricks API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Files API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Hubs API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups IDS API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups lakehouse API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Login API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Logs API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Pipelines API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Protocols API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Requests API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Roles API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Schemas API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Search API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Tenants API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups tetraflows API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Users API
OPEN COLLECTIONTetraScience Data and AI Cloud Access Groups Workflows API
OPEN COLLECTIONTetraScience Data and AI Cloud API
OPEN COLLECTIONScroll within the panel for all 37 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Tetrascience Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Tetrascience Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Tetrascience Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
TetraScience API Rules
SPECTRALSecurity 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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for TetraScience — 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 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/tetrascience · machine-readable index on apis.io
This is an independent, third-party profile of TetraScience, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.