Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ada Diamonds Agent 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%2Fadadiamonds.com%2Fadadiamonds" | shStep 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%2Fadadiamonds.com%2Fadadiamonds" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Ada Diamonds Agent API.
Search available loose lab-grown diamonds and read one by id
Search engagement ring settings and fine jewelry listings
Read published guides and showroom locations
Run several catalog reads in one batched request
Start and download a full catalog export job
GET STARTED
Create and complete an agent-commerce checkout session
Patterns agents use Ada Diamonds Agent API for, with concrete tasks.
★ Agent Shopping Assistant
A shopper asks an agent to find an engagement ring within a budget. The Ada Diamonds API searches loose diamonds, ring settings, and jewelry, and reads one item by id, so the agent can assemble a setting-plus-stone recommendation and answer questions from the published guides, all from anonymous catalog reads.
Search loose lab-grown diamonds and ring settings within a budget and return a setting-plus-stone recommendation
Guided Agent Checkout
Once a shopper picks an item, the agent needs to complete the purchase. The Ada Diamonds API creates an agent-commerce checkout session, updates it, and completes it to charge and place the order, so an authorized agent can take a selection all the way through to a placed order.
Create a checkout session for a selected ring, update it with shipping details, and complete it to place the order
Catalog Export and Sync
A partner wants Ada Diamonds' full inventory loaded into its own system. The API starts a full catalog export as an async job and lets the caller download the finished export, so an agent can run a scheduled export and keep an external catalog mirror in sync.
Start a full catalog export job, poll its status, and download the finished export
Consultation Booking
A high-consideration purchase often needs a human jeweler. The Ada Diamonds API requests a jeweler consultation and lists showroom locations and remote options, so an agent can hand a shopper off to a consultation and tell them where and how it can happen.
Request a jeweler consultation for a shopper and return the available showroom and remote options
41 endpoints — the ada diamonds agent api gives ai agents structured access to ada diamonds' live catalog of loose lab-grown diamonds, engagement ring settings, and fine jewelry, together with its published guides and showroom details.
METHOD
PATH
DESCRIPTION
/api/v1/diamonds
Search available loose lab-grown diamonds
/api/v1/engagement-rings
Search engagement ring settings
/api/v1/jewelry
Search fine jewelry
/api/v1/knowledge-base
List published guides and articles
/api/v1/batch
Run several read requests in one call
/api/v1/exports
Start a full catalog export job
/api/acp/checkout_sessions
Create an agent-commerce checkout session
/api/v1/diamonds
Search available loose lab-grown diamonds
/api/v1/engagement-rings
Search engagement ring settings
/api/v1/jewelry
Search fine jewelry
/api/v1/knowledge-base
List published guides and articles
/api/v1/batch
Run several read requests in one call
/api/v1/exports
Start a full catalog export job
/api/acp/checkout_sessions
Create an agent-commerce checkout session
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Ada Diamonds API by hand means choosing among API key, OAuth, and bearer auth and knowing which reads are anonymous. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.
Permission scoping
You choose which Ada Diamonds operations your agent may call, so it can search the catalog and read content while the checkout, consultation, and export operations stay out of the set unless you add them.
Credential isolation
Your Ada Diamonds credential 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 'search for lab-grown diamonds' or 'start a checkout session', and Jentic returns the matching Ada Diamonds operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Ada Diamonds Agent API through Jentic.
What authentication does the Ada Diamonds Agent API use?
The Ada Diamonds Agent API accepts an API key header, an OAuth 2.0 token with authorization-code or client-credentials flows, and a bearer token for its agent-commerce checkout, per its OpenAPI spec. Catalog and content reads are open and need no credential; credentials raise rate limits and reach customer-specific operations. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time.
Can I search the Ada Diamonds catalog without a credential?
Yes. The catalog and content reads for loose diamonds, ring settings, jewelry, guides, and showrooms are open, so an agent can search and read them anonymously. A credential is only needed for checkout, consultations, exports, and customer-specific data.
What are the rate limits for the Ada Diamonds Agent API?
The OpenAPI spec notes that credentials raise rate limits but does not state fixed numbers. Check the Ada Diamonds documentation at https://www.adadiamonds.com for the current limits on anonymous and keyed access.
How do I run a checkout through Jentic?
Import the Ada Diamonds Agent API from the Jentic directory and give your agent an intent such as 'start a checkout session for a ring'. Jentic returns the checkout operation with its input schema, your agent creates, updates, and completes the session, and your stored credential is injected at execution time. 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 Ada Diamonds Agent API?
Yes. Write a rule that allows only the catalog and content read operations, so your agent can search diamonds and read guides but cannot start a checkout, book a consultation, or run an export, and every call it makes is logged.
Is there an Ada Diamonds MCP server?
You don't need an MCP server to give your agent the Ada Diamonds Agent API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, so no extra server's tool definitions sit in the agent's context.
For Agents
Search Ada Diamonds' catalog of lab-grown diamonds, ring settings, and jewelry, read its guides, and run agent-commerce checkout sessions.
Use for: Search for loose lab-grown diamonds under a budget, Find an engagement ring setting by style, Read a knowledge-base guide about diamond cuts, Start a checkout session for a selected ring
Not supported: Does not handle diamond grading, shipping logistics, or post-sale support tickets. Use for browsing the Ada Diamonds catalog and completing checkout only.
The Ada Diamonds Agent API gives AI agents structured access to Ada Diamonds' live catalog of loose lab-grown diamonds, engagement ring settings, and fine jewelry, together with its published guides and showroom details. Catalog and content reads need no credential, while checkout, consultation booking, and customer-specific data require authorization. It supports batched reads, full catalog exports, and agent-commerce checkout sessions that charge and place an order.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>