Armada
Armada is an edge computing company that deploys full-stack compute, connectivity, and AI infrastructure into remote and disconnected environments. Its platform spans Atlas (an enterprise console for monitoring and managing distributed IoT and edge assets), Galleon (ruggedized, rapidly deployable modular data centers), and Bridge (a GPU cloud management platform / PaaS that provisions and orchestrates bare-metal, virtual-machine, and Kubernetes GPU workloads across NVIDIA and AMD hardware). The Bridge Orchestrator API exposes tenants, clusters, VMs, storage, networking, catalogs, and quota operations for building sovereign and edge AI clouds, and an OpenAI-compatible Model-as-a-Service inference API is available through Bridge AI Studio.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Armada the way a machine reads it — 37 machine-readable artifacts across 33 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 — Armada scores 39.9/100 (thin), 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 Armada
Each block below is one kind of artifact we hold for Armada. 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 33
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.
Armada Admin Settings API
The Admin Settings API from Armada — 1 operation(s) for admin settings.
Armada App Catalog API
The App Catalog API from Armada — 2 operation(s) for app catalog.
Armada Catalog API
The Catalog API from Armada — 5 operation(s) for catalog.
Armada Clusters API
The Clusters API from Armada — 11 operation(s) for clusters.
Armada CMS API
The CMS API from Armada — 3 operation(s) for cms.
Armada Dashboard API
The Dashboard API from Armada — 1 operation(s) for dashboard.
Armada Data Volumes API
The Data Volumes API from Armada — 2 operation(s) for data volumes.
Armada Datasets API
The Datasets API from Armada — 2 operation(s) for datasets.
Armada Device Discovery API
The Device Discovery API from Armada — 3 operation(s) for device discovery.
Armada Endpoints API
The Endpoints API from Armada — 3 operation(s) for endpoints.
Armada Features API
The Features API from Armada — 1 operation(s) for features.
Armada Health & Debug API
The Health & Debug API from Armada — 2 operation(s) for health & debug.
Armada Infra Import API
The Infra Import API from Armada — 7 operation(s) for infra import.
Armada Load Balancers API
The Load Balancers API from Armada — 2 operation(s) for load balancers.
Armada Log Level API
The Log Level API from Armada — 3 operation(s) for log level.
Armada Metal API
The Metal API from Armada — 8 operation(s) for metal.
Armada Models API
The Models API from Armada — 3 operation(s) for models.
Armada Monetize API
The Monetize API from Armada — 3 operation(s) for monetize.
Armada NetQ API
The NetQ API from Armada — 6 operation(s) for netq.
Armada Network API
The Network API from Armada — 8 operation(s) for network.
Armada PaaS API
The PaaS API from Armada — 3 operation(s) for paas.
Armada Quotas API
The Quotas API from Armada — 9 operation(s) for quotas.
Armada S3 API
The S3 API from Armada — 5 operation(s) for s3.
Armada Security Groups API
The Security Groups API from Armada — 2 operation(s) for security groups.
Armada Servers API
The Servers API from Armada — 2 operation(s) for servers.
Armada Slurm API
The Slurm API from Armada — 2 operation(s) for slurm.
Armada Storage API
The Storage API from Armada — 6 operation(s) for storage.
Armada Storage Classes API
The Storage Classes API from Armada — 2 operation(s) for storage classes.
Armada Templates API
The Templates API from Armada — 2 operation(s) for templates.
Armada Tenant Common Storage API
The Tenant Common Storage API from Armada — 2 operation(s) for tenant common storage.
Armada Tenants API
The Tenants API from Armada — 2 operation(s) for tenants.
Armada VMs API
The VMs API from Armada — 11 operation(s) for vms.
Armada VPC API
The VPC API from Armada — 4 operation(s) for vpc.
Scroll within the panel for all 33 ·
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.
armada-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.
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 Armada — 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
Access & Security 2
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
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/armada · machine-readable index on apis.io