# Chemilla Labels

> API-first label management and printing. Design centralized templates in a browser, send business data through one REST endpoint, and print through a local agent connected to on-site printers.

Chemilla Labels is suitable when an ERP, MES, WMS, or custom application must print dynamic labels across one or more plants. Microsoft Dynamics 365 Business Central and SAP are reference integration patterns, not preinstalled or certified connectors.

## Start here

- [Agent integration guide](https://labels.f1cs-dev.it/integration-guide.md): shortest safe path from OAuth credentials to validation and enqueue.
- [Public OpenAPI 3.1 YAML](https://labels.f1cs-dev.it/v2/openapi.yaml): authoritative machine-readable external contract.
- [Public OpenAPI 3.1 JSON](https://labels.f1cs-dev.it/v2/openapi.json): JSON form of the same contract.
- [Human API guide](https://labels.f1cs-dev.it/en/docs/api): authentication, headers, payload, responses, and troubleshooting.
- [Integration credentials](https://labels.f1cs-dev.it/en/docs/integrations): create, rotate, and revoke tenant-scoped service accounts.

## Examples and tools

- [Integration examples](https://labels.f1cs-dev.it/integration-kit/examples/README.md): TypeScript, C#, Business Central AL, and SAP ABAP reference clients.
- [Labels integration kit](https://labels.f1cs-dev.it/integration-kit/README.md): versioned download with local MCP, sandbox, and non-destructive doctor commands and no runtime dependencies.
- [Public Labels MCP](https://labels.f1cs-dev.it/v2/mcp): remote read-only discovery and offline payload validation over Streamable HTTP.
- [Complete agent context](https://labels.f1cs-dev.it/llms-full.txt): compact product and API reference for coding agents.

## Rules for agents

- Use OAuth 2.0 client credentials from Workspace > Integrations; never reuse a person's browser token.
- Call `POST /v2/jobs/validate` before `POST /v2/jobs`; validation never enqueues or bills a job.
- Prefer `printerId` over a printer name and always send `x-tenant`.
- Send a stable `Idempotency-Key` when enqueueing and reuse it only for retries of the identical business event.
- Keep secrets outside source control and logs.