Install Jentic One Beta

Connect the CloudXray FinOps Directory API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CloudXray FinOps Directory 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%2Fcloudxray.ai%2Fcloudxray" | 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%2Fcloudxray.ai%2Fcloudxray" | 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 CloudXray FinOps Directory API.

Search the directory of FinOps vendors with taxonomy filters

Read a vendor's full profile by slug

Find alternatives similar to a given vendor

Compare two to four vendors side by side

Read CloudXray's published analysis of a vendor

GET STARTED

Start building with CloudXray FinOps Directory API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use CloudXray FinOps Directory API for, with concrete tasks.

★ Agent-Driven Vendor Shortlisting

An AI agent connected to the CloudXray FinOps Directory API can build a shortlist of FinOps vendors from a plain description of a need. It reads the taxonomy to learn the valid filter values, searches the directory with those filters, and reads each candidate's profile, returning a ranked shortlist with the CloudXray profile URL for each so a buyer can click through. This replaces manually trawling vendor websites.

Read the taxonomy, search the directory for FinOps vendors matching the chosen filters, and return the top five profiles with their CloudXray profile URLs

Side-by-Side Vendor Comparison

When a team has narrowed its options, the CloudXray FinOps Directory API compares two to four vendors in one call and returns CloudXray's published analysis for each. An agent can assemble a comparison table and summarize where the vendors differ, drawing on the analysis endpoint rather than marketing copy, so the comparison reflects the directory's own research.

Compare the vendors with slugs vendor-a, vendor-b, and vendor-c and return a table of their differences with each vendor's analysis

Alternatives Discovery

A buyer who already knows one vendor often wants to see similar options. The CloudXray FinOps Directory API returns alternatives to a given vendor by slug, so an agent can start from a known name and surface comparable vendors the buyer may not have considered, each with its profile and CloudXray profile URL.

Find alternatives to the vendor with the given slug and return the three closest matches with their profiles

Directory Change Monitoring

The CloudXray FinOps Directory API publishes a change feed of directory updates, so an agent can watch for new vendors, profile changes, or newly published analysis. A team tracking the FinOps market can poll the feed and be notified when a vendor they follow is updated, without re-scanning the whole directory.

Read the change feed and return every directory update since the last check, flagging any that affect a vendor on the watch list

Key Endpoints

8 endpoints — the cloudxray finops directory api searches and reads a curated directory of finops vendors, returning each vendor's profile, similar alternatives, and cloudxray's published analysis.

METHOD

PATH

DESCRIPTION

GET

/api/v1/companies

Search vendors

GET

/api/v1/companies/{slug}

Get a vendor profile

GET

/api/v1/companies/{slug}/alternatives

Find similar vendors

GET

/api/v1/companies/{slug}/analysis

Published CloudXray analysis of a vendor

GET

/api/v1/compare

Compare two to four vendors

GET

/api/v1/taxonomy

Filter values and definitions

GET

/api/v1/changes

Directory change feed

GET

/api/v1/me

Your account's usage

GET

/api/v1/companies

Search vendors

GET

/api/v1/companies/{slug}

Get a vendor profile

GET

/api/v1/companies/{slug}/alternatives

Find similar vendors

GET

/api/v1/companies/{slug}/analysis

Published CloudXray analysis of a vendor

GET

/api/v1/compare

Compare two to four vendors

GET

/api/v1/taxonomy

Filter values and definitions

GET

/api/v1/changes

Directory change feed

GET

/api/v1/me

Your account's usage

Why Jentic?

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

Setup

Wiring the CloudXray FinOps Directory API by hand means creating a verified-email API key, handling the free-allowance-then-credits billing, and reading the taxonomy before you can filter a search correctly. Through Jentic you install once, import CloudXray from the API Directory, store the key once, and your agent calls it.

Permission scoping

Every CloudXray operation is a read: vendor search, profile, alternatives, analysis, compare, and the change feed. A rule bounds which of these your agent may call, so you can allow vendor search and profile reads without the compare or change-feed operations. Nothing in the directory can be modified through the API.

Credential isolation

Your CloudXray key 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 FinOps vendors' or 'compare FinOps tools', and Jentic returns the matching CloudXray operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using CloudXray FinOps Directory API through Jentic.

What authentication does the CloudXray FinOps Directory API use?

The CloudXray FinOps Directory API authenticates with a bearer token per its OpenAPI spec: an API key prefixed cai_live_ sent as an Authorization: Bearer header, created from your CloudXray profile with a verified email. Through Jentic the key is stored once by your own self-hosted instance and injected at call time, so it never sits in your agent's prompt or logs.

Is there a CloudXray MCP server?

You do not need an MCP server to give your agent the CloudXray FinOps Directory API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the search, profile, compare, and change-feed operations on demand. Operations are discovered when needed, so no extra server's tool definitions are loaded into the agent's context.

Can I limit what my agent is allowed to do with the CloudXray FinOps Directory API?

Yes. Give the agent a rule that permits the vendor search and single-profile reads and nothing else, so it can look up vendors and read their profiles but will not run comparisons or pull the change feed. Every CloudXray operation is a read, so the rule governs which lookups happen, and each call is logged.

Can I compare FinOps vendors with the CloudXray FinOps Directory API?

Yes. Call GET /api/v1/compare with two to four vendor slugs and the API returns a side-by-side comparison, and GET /api/v1/companies/{slug}/analysis returns CloudXray's published analysis for one vendor. To find candidates first, search with GET /api/v1/companies and list similar vendors with GET /api/v1/companies/{slug}/alternatives.

What are the rate limits for the CloudXray FinOps Directory API?

The OpenAPI spec does not state a fixed per-second rate limit. It notes each account gets a free monthly allowance of calls, after which calls draw on credits, and failed calls are not counted. Check the API terms at https://cloudxray.ai/api-terms for the current allowance before running an agent at volume.

How do I search FinOps vendors with the CloudXray FinOps Directory API through Jentic?

Search Jentic for 'search FinOps vendors' and it returns the GET /api/v1/companies operation with its input schema. Pass your filters and the agent gets back matching vendors, each with its CloudXray profile URL to display. To run it on your own infrastructure, install Jentic One from its GitHub repo.

CloudXray FinOps Directory API

AI ReadinessFoundational (C)54/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany Databearer8 EndpointsREST

For Agents

Search a directory of FinOps vendors, read vendor profiles and published analysis, find alternatives, and compare two to four vendors side by side. Read-only directory data with a taxonomy of filter values and a change feed.

Use for: Search for FinOps vendors that match a set of filters, Get the full profile of a specific FinOps vendor, Find alternatives to a vendor we are evaluating, Compare three FinOps tools side by side

Not supported: Does not manage cloud spend, process invoices, or store your own cost data. Use for searching and reading the CloudXray FinOps vendor directory only.

The CloudXray FinOps Directory API searches and reads a curated directory of FinOps vendors, returning each vendor's profile, similar alternatives, and CloudXray's published analysis. It compares two to four vendors side by side, exposes the taxonomy of filter values used to narrow a search, and streams a change feed of directory updates. Every vendor result carries its CloudXray profile URL to display alongside the data.

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: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

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: FSignals: 4

61%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

47%

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: A-Signals: 1

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the CloudXray FinOps Directory API to your agent

Capabilities

Start building with CloudXray FinOps Directory API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

CloudXray FinOps Directory API

Jentic AI Readiness Score

CloudXray FinOps Directory 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