# Materials Zone > Materials Zone (MaterialsZone) is a materials-informatics platform that centralizes materials R&D data into a single source of truth. Its RESTful API integrates with lab instruments, Python scripts and analytical tools to automate workflows, connect diverse data sources, and perform domain-specific analysis. Data is organized as Folders > Tables > Items, enriched with Parameters, Values, Measurements, Protocols and Parsers. This llms.txt was generated by the API Evangelist enrichment pipeline from the provider's public OpenAPI and developer documentation. ## API - [Materials Zone API (OpenAPI 3.1.0)](https://api.materials.zone/v2beta1/swagger.json): 20 paths / 35 operations across folders, tables, items, parameters, measurements, protocols, parsers, files and jobs. Base URL https://api.materials.zone/v2beta1. Auth: private API key in the `authorization` header. - [Developer portal & interactive docs](https://developer.materials.zone/) ## Specs & Artifacts - [OpenAPI (harvested)](openapi/materials-zone-openapi.json) - [Authentication profile](authentication/materials-zone-authentication.yml) - [API conventions (auth, cursor pagination, error envelope, versioning)](conventions/materials-zone-conventions.yml) - [Error catalog](errors/materials-zone-problem-types.yml) - [Data model / ERD](data-model/materials-zone-data-model.yml) - [Lifecycle & versioning](lifecycle/materials-zone-lifecycle.yml) - [Conformance](conformance/materials-zone-conformance.yml) - [Agentic access contracts](agentic-access/materials-zone-agentic-access.yml) - [Domain security probe](security/materials-zone-domain-security.yml) ## Docs - [Website](https://www.materials.zone/) - [Application sign in](https://app.materials.zone/signin) - [Terms of Service](https://www.materials.zone/legals/terms-of-service) - [Privacy Policy](https://www.materials.zone/legals/privacy-policy) ## Key conventions - Authentication: private per-user API key passed in the `authorization` header on every request; keys are rotatable. - Pagination: cursor-based. Pass `cursor` (previous page's `endCursor`) and optional `pageSize` (default 100). Responses wrap results in `{ data: [...], pagination: { startCursor, endCursor, hasNextPage } }`. - Errors: JSON `{ code, message }` (not RFC 9457). Common statuses: 400, 401, 403, 409. - Versioning: version in URI path (`/v2beta1`).