canonical: https://jentic.com/apis/cloudxray.ai/cloudxray # CloudXray FinOps Directory API 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. ## For AI 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. ## Scope Does not manage cloud spend, process invoices, or store your own cost data. Use for searching and reading the CloudXray FinOps vendor directory only. ## Capabilities - 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 - Track directory updates through the change feed ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Companies** — Search vendors, read a vendor profile by slug, find alternatives, and read CloudXray's published analysis - **Compare** — Compare two to four vendors side by side in a single call - **Taxonomy** — The filter values and their definitions used to narrow a directory search - **Changes** — A change feed of directory updates to new and modified vendor entries ## 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:** 54 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 27 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 75 / 100 - **View full report:** https://jentic.com/apis/cloudxray.ai/cloudxray/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 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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **G2** — Broad software marketplace with reviews and comparisons across all categories, not FinOps specifically. - **Crunchbase** — Company and funding directory covering all industries rather than FinOps vendors with analysis. - **Clearbit** — Enriches a company record with firmographic and technographic data to add to a CloudXray profile. - **Diffbot** — Knowledge graph of organizations that can supplement a CloudXray vendor profile with web-sourced facts. ## FAQ ### 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.