Install Jentic One Beta

Connect the Odoo API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Odoo API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmetquay.co%2Fmetquay" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmetquay.co%2Fmetquay" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Odoo API.

Create a Metquay customer with companyName, companyCode, and workspaceCode, plus billing and shipping addresses

Register a customer instrument with serialNo, make, model, range, and a calibrationFrequency and calibrationFrequencySpan

Define an instrument category by name so new instruments can be grouped under it

Open a calibration work for a customerInstrumentId with inDate, deliveryDate, accreditation, and scope

GET STARTED

Start building with Odoo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Odoo API for, with concrete tasks.

★ Agent-driven intake of calibration jobs through Jentic

When instruments arrive at a calibration lab, an agent can register them and open the job without anyone retyping the paperwork. Through Jentic it finds the Metquay customer-instrument and work operations, creates the instrument with its serialNo and calibrationFrequency, then opens a work with the returned customerInstrumentId and today's inDate. The bearer token stays on your own Jentic One instance.

POST /customer-instrument-details with name 'Digital Caliper', companyId 'D1', serialNo 'DC-20931', calibrationFrequency '12', calibrationFrequencySpan 'MONTH', workspaceCode 'LAB1', then POST /works with the new customerInstrumentId and inDate '2026-11-09'

ERP-to-Metquay customer sync

Labs that run accounting and sales in an ERP such as Odoo can create matching Metquay customers when a new account is opened. The create-customer operation requires companyName, companyCode, and workspaceCode and accepts billing and shipping address fields, paymentMethod, isTaxable, and taxCode.

POST /customers with companyName 'Acme Instruments Ltd', companyCode 'ACME01', workspaceCode 'LAB1', email 'qa@acme.example', and billing address fields

Setting up instrument categories

Before importing a customer's instrument list, a lab can define the categories those instruments belong to. The instrument-categories operation needs only a name, with an optional description, and new instruments reference the category through instrumentCategoryName.

POST /instrument-categories with name 'Torque Wrenches' and description 'Click and dial torque tools'

Key Endpoints

4 endpoints — the metquay odoo api creates records in metquay, the calibration management system for instrument labs, from an outside system such as an erp.

METHOD

PATH

DESCRIPTION

POST

/customers

Create a customer

POST

/customer-instrument-details

Create a customer instrument

POST

/instrument-categories

Create an instrument category

POST

/works

Create a calibration work

POST

/customers

Create a customer

POST

/customer-instrument-details

Create a customer instrument

POST

/instrument-categories

Create an instrument category

POST

/works

Create a calibration work

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Metquay by hand means attaching its bearer token, picking the right workspace host, and assembling large create payloads with required fields such as companyCode and workspaceCode. Through Jentic you install once, import Metquay from the API Directory, store the token once, and your agent calls it.

Permission scoping

Metquay identifies customers and instruments in the request body, not the URL path, so rules bound which operations your agent may call, not which customer. Limit the agent to the operations it needs, such as opening works, so customer creation is not included unless you add it.

Credential isolation

Your Metquay bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'register a customer instrument' or 'open a calibration work', and Jentic returns the matching Metquay operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Odoo API through Jentic.

What authentication does the Metquay Odoo API use?

Per its OpenAPI spec, the Metquay Odoo API uses HTTP bearer authentication (the apiAuth scheme), sent as `Authorization: Bearer <token>` on each of its create operations. Through Jentic the token is stored encrypted by your own Jentic One instance and injected when the agent calls.

Can I read or update records with the Metquay Odoo API?

No. The spec contains four create operations: customers, customer instruments, instrument categories, and works. There are no list, get, update, or delete operations, so keep the IDs Metquay returns when you create a record if you need to reference it later, such as the customerInstrumentId a work requires.

How do I open a calibration work through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the Metquay API from the directory, and store your bearer token. Your agent searches 'create a calibration work in Metquay', gets POST /works with its schema, and sends the required customerInstrumentId plus fields such as inDate and deliveryDate. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Metquay Odoo API?

Yes. For example, write a rule that allows only POST /customer-instrument-details and POST /works, so an intake agent can register instruments and open jobs but cannot create customers or change your instrument categories. Every call it makes is logged.

Is there a Metquay MCP server?

You don't need an MCP server to give your agent Metquay. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it.

What are the rate limits for the Metquay Odoo API?

The OpenAPI spec does not specify numeric rate limits, though most operations list a 429 response. Check the Metquay documentation at https://metquay.co for current limits.

Which server does the Metquay Odoo API use?

The spec's live server is https://trial.metquay.co/api/v1/, and it also lists a SwaggerHub mock server for testing. Confirm the host for your own Metquay workspace before sending production data.

Metquay Odoo API

AI ReadinessAI-Aware (A-)71/100

See full scorecard

Community OpenAPI document · agent-readyCRMContact Managementbearer4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Push customers, customer instruments, instrument categories, and calibration works into Metquay from another system, using a bearer token.

Use for: Add a new calibration customer to Metquay from our ERP, Register a pressure gauge with serial number PG-4471 for an existing customer, Create an instrument category called Torque Wrenches, Open a calibration job for a customer instrument that arrived today

Not supported: Does not read, update, or delete records, issue calibration certificates, or handle invoicing. Use for creating Metquay customers, instruments, categories, and calibration works only.

The Metquay Odoo API creates records in Metquay, the calibration management system for instrument labs, from an outside system such as an ERP. It adds customers with company codes, billing and shipping addresses, and tax settings, registers the instruments each customer sends in with serial number, make, model, and calibration frequency, and defines instrument categories. It also opens calibration works against a customer instrument, carrying details such as inDate, deliveryDate, accreditation, and salesOrderNo. Every operation is a create, so the API pushes data into Metquay rather than reading it back.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: ASignals: 4

64%

Example Density

How richly the API is illustrated with examples.

86%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

67%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C+Signals: 1

59%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Odoo API to your agent

Capabilities

Start building with Odoo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Metquay Odoo API

Jentic AI Readiness Score

Odoo API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness