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.