agilent-technologies
Agilent Technologies is a global leader in life sciences, diagnostics, and applied chemical markets, providing instruments, software, services, and consumables for laboratory workflows. Agilent offers APIs for laboratory operations management including iLab for core facility billing and scheduling, SLIMS for laboratory information management, CrossLab Asset Manager for instrument management, and VWorks for laboratory automation.
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 agilent-technologies the way a machine reads it — 95 machine-readable artifacts across 10 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 — agilent-technologies scores 55.4/100 (developing), with a separate agent-readiness read of 48/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.
How we profile agilent-technologies
Each block below is one kind of artifact we hold for agilent-technologies. 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 10
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.
Agilent SLIMS REST API
The SLIMS (Smart Laboratory Information Management System) REST API provides programmatic access to Agilent SLIMS laboratory data management platform. SLIMS features three APIs ...
Agilent CrossLab Asset Manager API
The CrossLab Asset Manager API provides programmatic access to Agilent's CrossLab instrument services platform, enabling management of laboratory assets, instrument service reco...
Agilent VWorks Automation API
The VWorks API provides a Component Object Model (COM) application programming interface for VWorks laboratory automation software (version 14.0 and later). It enables programma...
agilent-technologies Cores API
Core facility resources — the root resource of the API
agilent-technologies Invoices API
Billing invoices and financial records
agilent-technologies Members API
Core facility membership and user management
agilent-technologies Projects API
Research projects and cost accounts
agilent-technologies Reservations API
Equipment reservations and scheduling
agilent-technologies Service Requests API
Service request submissions and management
agilent-technologies Services API
Services and price lists offered by a core facility
Scroll within the panel for all 10 ·
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 six things the Kin Score reads for commercial clarity.
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.
Agilent Technologies 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.
Features 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
RESTful Architecture
iLab and CrossLab APIs leverage RESTful architecture with HATEOAS for discoverable resource navigation.
OAuth2 Authentication
Secure access to APIs via OAuth2 with client ID and API token-based authentication.
Financial System Integration
Pre-built integration support for SAP, Oracle/PeopleSoft, Lawson, and Banner financial systems.
LIMS Integration
Integration with laboratory information management systems for sample tracking and results management.
Instrument Data Import
Ability to import usage logs and data directly from connected laboratory instruments.
Plugin Architecture
SLIMS supports custom plugin development via Java and Python APIs for workflow extension.
Auto-Generated API Documentation
SLIMS REST API documentation is automatically generated from each deployed instance.
Scroll within the panel for all 7 ·
Semantic 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.
Spectral Rules 2
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.
agilent-technologies API Rules
SPECTRALagilent-technologies API Rules
SPECTRALJSON Schema 19
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Core
JSON SCHEMACores List Response
JSON SCHEMAError Response
JSON SCHEMAInvoice
JSON SCHEMAInvoices List Response
JSON SCHEMAMember
JSON SCHEMAMembers List Response
JSON SCHEMAPrice
JSON SCHEMAPrice Update Request
JSON SCHEMAPrices List Response
JSON SCHEMAProject
JSON SCHEMAProjects List Response
JSON SCHEMAReservation
JSON SCHEMAReservations List Response
JSON SCHEMAService Request Create Request
JSON SCHEMAService Request
JSON SCHEMAService Requests List Response
JSON SCHEMAService
JSON SCHEMAServices List Response
JSON SCHEMAScroll within the panel for all 19 ·
JSON Structure 19
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Ilab Operations Api Core Structure
JSON STRUCTUREIlab Operations Api Cores List Response Structure
JSON STRUCTUREIlab Operations Api Error Response Structure
JSON STRUCTUREIlab Operations Api Invoice Structure
JSON STRUCTUREIlab Operations Api Invoices List Response Structure
JSON STRUCTUREIlab Operations Api Member Structure
JSON STRUCTUREIlab Operations Api Members List Response Structure
JSON STRUCTUREIlab Operations Api Price Structure
JSON STRUCTUREIlab Operations Api Price Update Request Structure
JSON STRUCTUREIlab Operations Api Prices List Response Structure
JSON STRUCTUREIlab Operations Api Project Structure
JSON STRUCTUREIlab Operations Api Projects List Response Structure
JSON STRUCTUREIlab Operations Api Reservation Structure
JSON STRUCTUREIlab Operations Api Reservations List Response Structure
JSON STRUCTUREIlab Operations Api Service Request Structure
JSON STRUCTUREIlab Operations Api Service Structure
JSON STRUCTUREIlab Operations Api Services List Response Structure
JSON STRUCTUREScroll within the panel for all 19 ·
Examples 19
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 19 ·
Security Posture 2
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.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Core Facility Billing Automation
Automate billing workflows between iLab core facilities and institutional financial systems such as SAP or Oracle.
Laboratory Scheduling Integration
Integrate external scheduling applications with iLab's equipment reservation and usage tracking.
Sample Lifecycle Management
Use the SLIMS API to track samples from receipt through analysis and reporting across NGS, biobank, and R&D workflows.
Instrument Asset Tracking
Manage laboratory instrument service records, calibration schedules, and compliance documentation via CrossLab Asset Manager API.
Automation Workflow Control
Programmatically control VWorks-driven liquid handling robots and integrated workstations for high-throughput workflows.
LIMS Data Reporting
Extract and aggregate laboratory data from SLIMS for custom reporting and business intelligence integrations.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
SAP
Financial system integration for billing and cost accounting via iLab API.
Oracle PeopleSoft
ERP integration for institutional billing and financial reporting.
Lawson
Financial management system integration for laboratory billing workflows.
Banner
Higher education ERP integration for core facility cost center management.
LabWare LIMS
Integration between Agilent instruments and LabWare LIMS for data transfer and workflow coordination.
Identity Management Systems
Integration with institutional identity providers for single sign-on and user provisioning.
Resources
Every other property we hold for agilent-technologies — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
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/agilent-technologies · machine-readable index on apis.io