Alphaus
Alphaus is a Tokyo-based cloud FinOps company (No. 1 in Japan) whose platform helps enterprises, managed service providers, and cloud resellers manage and optimize multi-cloud spend across AWS, Azure, and GCP. Its products include Octo (cost visibility and optimization), Ripple and WavePro (reseller billing automation and invoicing), and Cover (cost anomaly detection and recommendation intelligence). Developers integrate through the Blue API — a unified protobuf/gRPC surface with a grpc-gateway JSON/REST proxy and generated OpenAPI — spanning 15 services and nearly 600 operations, complemented by the bluectl CLI and Go, Python, and TypeScript SDKs.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Alphaus the way a machine reads it — 20 machine-readable artifacts across 15 APIs, 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 — Alphaus scores 45.1/100 (developing), with a separate agent-readiness read of 65/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
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.
How we profile Alphaus
Each block below is one kind of artifact we hold for Alphaus. 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 15
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.
Alphaus Admin API
Admin API. Base URL: https://api.alphaus.cloud/m/blue
Alphaus Billing API
(BETA) Billing API. Base URL: https://api.alphaus.cloud/m/blue/billing
Alphaus Cost API
Cost API. Base URL: https://api.alphaus.cloud/m/blue/cost
Alphaus Cover API
(BETA) Cover API. Base URL: https://api.alphaus.cloud/m/blue/cover
Alphaus Flags API
(ALPHA) Flag API. Base URL: https://api.alphaus.cloud/m/blue
Alphaus Flow API
(ALPHA) Flow API. Base URL: https://api.alphaus.cloud/m/blue/flow
Alphaus GuaranteedCommitments API
(Alpha) GuaranteedCommitments API. Base URL: https://api.alphaus.cloud/m/blue/gc
Alphaus Iam API
(BETA) IAM API. Base URL: https://api.alphaus.cloud/m/blue
Alphaus Luster API
(ALPHA) Luster API. Base URL: https://api.alphaus.cloud/m/blue/luster
Alphaus Operations API
(BETA) Long operations API. Base URL: https://api.alphaus.cloud/m/blue
Alphaus Organization API
(BETA) Organization API. Base URL: https://api.alphaus.cloud/m/blue
Alphaus Preferences API
(BETA) Preferences API. Base URL: https://api.alphaus.cloud/m/blue
Alphaus Pricing API
(BETA) Pricing API. Base URL: https://api.alphaus.cloud/m/blue/pricing
Alphaus Prism API
(Alpha) Prism API. Base URL: https://api.alphaus.cloud/m/blue/prism
Alphaus Vortex API
(Alpha) Vortex API. Base URL: https://api.alphaus.cloud/m/blue/vortex
Scroll within the panel for all 15 ·
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.
alphaus-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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Alphaus — 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.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/alphaus · machine-readable index on apis.io