ThetaRay
ThetaRay is an Israeli/US financial-crime-compliance software company that applies its patented "Cognitive AI" anomaly-detection technology to anti-money-laundering (AML) transaction monitoring, sanctions and customer screening, PEP screening, and customer risk assessment for banks, fintechs and payment service providers. Its cloud-native SaaS platform ingests SWIFT and domestic payment traffic, KYC/customer data and risk indicators to surface suspected money laundering, terrorist financing and sanctions-evasion typologies in cross-border and domestic payments, with an agentic AI investigation product ("RAY") that automates and explains alert triage inside a single case manager. ThetaRay markets an API-based architecture for integrating monitoring and screening into existing workflows, and publishes a developer portal at api.thetaray.com — but that portal, the documentation host docs.thetaray.com, and every specification behind them sit behind customer SSO, so no machine-readable contract is publicly retrievable. Offices in New York, London, Madrid, Tel Aviv and Dubai; also distributed through the Microsoft commercial marketplace.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles ThetaRay the way a machine reads it — 5 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — ThetaRay scores 21.3/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
ThetaRay's API developer portal at api.thetaray.com is a Redocly Cloud site whose every route — including /openapi and /_spec/* — 302s to an OIDC login at auth.cloud.redocly.com, and the separate docs.thetaray.com host 302s to a Microsoft Entra SAML sign-in, so the OpenAPI that portal exists to serve is readable only by existing ThetaRay customers.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is ThetaRay's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://api.thetaray.com/openapi→ HTTP 302https://api.thetaray.com/_spec/openapi.yaml→ HTTP 401http://docs.thetaray.com/→ HTTP 302https://api.thetaray.com/mcp→ HTTP 401https://api.thetaray.com/openapi.json→ HTTP 404https://api.thetaray.com/.well-known/oauth-authorization-server→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Put this on your own site. The badge is drawn live from ThetaRay's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/thetaray/"
title="ThetaRay on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/thetaray.svg"
alt="ThetaRay Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/thetaray/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/thetaray/"
title="ThetaRay on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/thetaray/card.svg"
alt="ThetaRay Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile ThetaRay
Each block below is one kind of artifact we hold for ThetaRay. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
ThetaRay Developer Portal API Surface
ThetaRay publishes an API developer portal at api.thetaray.com, hosted on Redocly Cloud. The portal root redirects to /openapi and then to an OIDC login at auth.cloud.redocly.co...
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
thetaray-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for ThetaRay — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/thetaray · machine-readable index on apis.io
This is an independent, third-party profile of ThetaRay, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.