canonical: https://jentic.com/apis/go-cal.com.co/go-cal # Go-cal API The Go-cal API manages a calibration laboratory's instruments, calibration results, certificates, and the documents that support them. Instruments and their measurement variables are registered, calibration results and best-measurement-capability entries are recorded against them, and certificates are issued with traceability back to reference standards. Documents, certificates, and billing quotes are versioned so a laboratory keeps an auditable history, and indicator endpoints report metrics such as calibrations per day and instrument interventions. ## For AI agents Register calibration instruments, record calibration results, issue traceable certificates, manage versioned laboratory documents, and read calibration indicators through the Go-cal API. ## Scope Does not handle geolocation, CRM pipelines, or social media publishing. Use for managing calibration laboratory instruments, certificates, and records only. ## Capabilities - Register calibration instruments and their measurement variables - Record calibration results and best-measurement-capability entries for an instrument - Issue calibration certificates with traceability to reference standards - Store and version laboratory documents and their attachments - Read calibration indicators such as calibrations per day and instrument interventions - Build billing quotes, price lists, and taxes for calibration services ## Use cases ### Agent-Driven Calibration Record Keeping An AI agent connected through Jentic registers an instrument, records its calibration result, and issues the certificate without a human stepping through each screen. Because Go-cal versions documents, certificates, and quotes, the agent leaves behind an auditable trail of every record it creates for the laboratory. Example prompt: Register an instrument, record a calibration result against it, and issue the calibration certificate ### Instrument Calibration Lifecycle A metrology lab tracks each instrument from registration through calibration and re-calibration. Go-cal records calibration results and best-measurement-capability entries per instrument and exposes instrument variables, so an agent keeps the calibration state of every instrument current. Example prompt: List instruments due for calibration, record a new calibration result, and update the instrument's traceability ### Certificate Traceability and Documents Accreditation requires certificates that trace back to reference standards and documents kept under version control. Go-cal issues calibration certificates with traceability and stores versioned documents and attachments, so an agent produces and files the evidence an audit expects. Example prompt: Retrieve a calibration certificate's traceability record and file the associated document in document management ### Calibration KPI Reporting Lab managers watch throughput and workload with indicators. Go-cal reports metrics such as calibrations per day and instrument interventions, so an agent pulls the indicator data to refresh a dashboard rather than aggregating calibration records itself. Example prompt: Fetch the calibrations-by-day indicator and the instrument-interventions indicator and load them into a dashboard ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/instrument/` | Register a calibration instrument | | GET | `/instrument/` | List instruments | | POST | `/calibration-result/` | Record a calibration result | | GET | `/bmc-calibration/` | List best-measurement-capability entries | | GET | `/certificate/traceability/calibration/{uuid}/` | Get a calibration certificate's traceability record | | GET | `/document-management/` | List versioned laboratory documents | | GET | `/indicators/calibrations-by-day/` | Read the calibrations-per-day indicator | | GET | `/billing/app/quotes/quote/` | List billing quotes | ## Key resources - **Instruments** — Register instruments, manage their measurement variables, and validate certificates - **Calibration results** — Record calibration results and best-measurement-capability (BMC) entries per instrument - **Certificates** — Issue calibration certificates with traceability back to reference standards - **Document management** — Store and version laboratory documents and their attachments - **Indicators** — Read calibration metrics such as calibrations per day and instrument interventions - **Billing** — Build quotes, price lists, and taxes for calibration services ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 23 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 36 / 100 - Developer Experience & Jentic Compatibility: 56 / 100 - AI-Readiness & Agent Experience: 17 / 100 - Agent Usability: 43 / 100 - Security: 50 / 100 - AI Discoverability: 7 / 100 - **View full report:** https://jentic.com/apis/go-cal.com.co/go-cal/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Go-cal by hand means supplying two API-key headers, the `Authorization` bearer token and the `x-Management` account id, and navigating 546 operations to find the ones you need. Through Jentic you install once, import Go-cal from the API Directory, store the credentials once, and your agent calls the operation it needs. - **Permission scoping:** Go-cal exposes 546 operations across instruments, calibrations, certificates, documents, and billing. You choose the operations your agent may call, so a rule can keep it to reading indicators and documents and leave instrument deletion or billing changes out unless you add them. - **Credential handling:** Your Go-cal `Authorization` token and `x-Management` account id are held by your own Jentic One instance, encrypted, and injected into the request headers at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'record a calibration result' or 'read the calibrations-by-day indicator', and Jentic returns the matching Go-cal operation with its input schema so the agent calls the right endpoint among the 546 without browsing the reference docs. ## Related APIs - **SafetyCulture API** — SafetyCulture runs inspections, assets, and quality checks, versus Go-cal's calibration and metrology focus. - **Fiix CMMS API** — Fiix manages equipment maintenance and work orders that pair with Go-cal's calibration lifecycle. - **Box Platform API** — Box stores and shares files, complementing Go-cal's calibration certificates and documents. ## FAQ ### What authentication does the Go-cal API use? The API uses API-key headers per its OpenAPI spec: a bearer token in the `Authorization` header and an account id in the `x-Management` header for management access. Through Jentic both are held by your own Jentic One instance and attached to each request at execution time, so they never appear in your agent's prompt or logs. ### Can I issue calibration certificates with the Go-cal API? Yes. Go-cal records calibration results against an instrument and issues certificates with traceability back to reference standards. Your agent retrieves a certificate's traceability record by id, so the evidence links to the calibration result and the instrument it covers. ### What are the rate limits for the Go-cal API? The OpenAPI spec does not specify rate limits. Check the Go-cal documentation at https://www.go-cal.com.co/ for current limits before running large synchronization jobs across the 546 operations. ### Is there a Go-cal MCP server? You do not need an MCP server to give your agent the Go-cal API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent calls the instrument, calibration, and document operations on demand without loading an extra server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the Go-cal API? Yes. With 546 operations spanning instruments, calibrations, documents, and billing, you write a rule that allows only the ones your agent needs, such as reading indicators and documents, so it cannot delete instruments or change billing unless you add those operations. You choose what the agent may call, and every call it makes is logged. ### How do I record a calibration result through Jentic? Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the Go-cal API from the Jentic directory and search by intent such as 'record a calibration result'. Jentic returns the matching operation with its input schema so your agent builds a valid request. To run it on your own infrastructure, install Jentic One from its GitHub repo.